Elastic and Pinecone Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Align data between Elastic and Pinecone to automate database workflows. Actions made in Elastic integration can trigger sequences of multiple actions inside Pinecone app - automatically, without any line of code.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about Elastic and Pinecone

Detailed info you need to know about Elastic and Pinecone integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Elastic

    • Database
    • 58 searches
    • 65 actions

    Distributed search and analytics engine for documents, logs, and metrics.[5]

  • Pinecone

    • Database
    • 37 searches
    • 40 actions

    Vector database and assistant platform for AI search.[6]

How to connect Elastic to Pinecone

Set up your Elastic and Pinecone integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between Elastic and Pinecone work in WEXTL?

WEXTL exposes actions and triggers for Elastic and Pinecone that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.

Elastic actionsPinecone actions

Elastic modules

  • Analyze Index Text Splits Text into search tokens using the analyzers and field mappings of one index. Use Field to analyze it the way that field would, or Analyzer, Tokenizer, Token Filters and Character Filters to try another chain.
  • Analyze Text Breaks Text into search tokens, either with an Analyzer or with a Tokenizer plus Token Filters and Character Filters. Add a Normalizer to turn the whole text into a single token for keyword fields.
  • Bulk Index Documents Runs many index, create, update and delete actions in one request, each action line followed by its document line. Add an Ingest Pipeline as default, or Require Alias to fail operations whose index is not an alias. Output includes Took (ms), Errors and Items.
  • Cancel a Task Cancels a running task. Turn on Wait for Completion to wait until the task has actually stopped.
  • Clean a Snapshot Repository Removes files from a snapshot repository that no remaining snapshot needs.
  • Clone an Index Copies a read-only Source Index to a New Index Name that does not exist yet. Pass Settings or Aliases as JSON objects for the new index, and Wait for Active Shards to wait for shard copies. Output includes Acknowledged and Index.
  • Close an Index Closes an index, or a comma-separated list or pattern of indices. Use Wait for Active Shards to wait for shard copies before the step finishes.
  • Count Documents Counts the documents that match a Query DSL object or a Lucene Query String, across all indices. Use Minimum Score, Routing or Stop After to narrow or shorten the count.
  • Count Index Documents Counts documents in a single index, with the same Query, Query String, Minimum Score and Routing options. Output has the Count and Shards.
  • Create a Component Template Saves a reusable component template under a Template Name. Fill in at least one of Settings, Mappings or Aliases to say what it contributes, and turn on Create Only to fail instead of replacing a template of the same name.
  • Create a Data Stream Makes a new data stream. An index template with data stream enabled must already match its name.
  • Create a Document Stores a new Document in a data stream or index under a Document ID, failing with a conflict if that ID already exists. Use Ingest Pipeline to transform it first and Routing to pick the shard.
  • Create a Snapshot Takes a snapshot in a Repository under a Snapshot Name. Narrow it with Indices, Feature States or Ignore Missing Indices, and turn on Wait for Completion to get its details.
  • Create a Snapshot Repository Registers a repository under a Repository Name, of a Type such as Amazon S3 or Shared file system, with its Settings. Turn Verify off to register it first and check later.
  • Create an ILM Policy Saves an index lifecycle policy from its Phases (hot, warm, cold, frozen or delete). An existing policy with the same Policy Name is replaced.
  • Create an Index Creates an index named Index Name, with optional Settings, Mappings and Aliases as JSON objects. Leave Settings empty for the cluster defaults.
  • Create an Index Alias Points an Alias Name at an index or data stream. Add a Filter to limit which documents the alias shows, or turn on Write Index to make this index the one that receives writes sent to the alias.
  • Create an Index Template Saves an index template for matching Index Patterns, with optional Component Templates, Priority, Settings, Mappings and Aliases. Turn on Data Stream to create data streams instead of plain indices.
  • Create an Ingest Pipeline Saves an ingest pipeline from its Processors, which run in order. Use On Failure for processors that run when one fails, and If Version to replace it only at a stored version.
  • Delete a Component Template Removes a component template. Elasticsearch refuses while an index template still uses it.
  • Delete a Data Stream Deletes a data stream. Its data is removed and this cannot be undone.
  • Delete a Data Stream Lifecycle Removes the lifecycle attached to a data stream in Elasticsearch.
  • Delete a Document Deletes a document held in an index. Use If Sequence Number and If Primary Term so the delete only runs when the document has not changed since.
  • Delete a Snapshot Deletes a snapshot stored in a Repository. Turn off Wait for Completion to return as soon as the deletion is scheduled.
  • Delete a Snapshot Repository Unregisters a snapshot repository from the cluster.
  • Delete an ILM Policy Removes a lifecycle policy. Elasticsearch refuses while an index still uses it.
  • Delete an Index Removes an index. This cannot be undone. Turn on Ignore Missing Index so the step succeeds when the index does not exist.
  • Delete an Index Alias Deletes the alias pointing at a data stream or index.
  • Delete an Index Template Deletes an index template used for new indices.
  • Delete an Ingest Pipeline Removes an ingest pipeline. An index that names it as its default pipeline then fails to index.
  • Delete Documents by Query Deletes all documents of an index that match a Query, stopping at Maximum Documents when that is used. Use Requests per Second to throttle the run, and On Version Conflict to Abort or Proceed.
  • Explain Allocation Explains why a shard is or is not allocated. With nothing filled in, it explains the first unassigned shard Elasticsearch finds. Turn on Include Disk Info or Include Yes Decisions for more detail.
  • Explain Document Tests a document against a Query DSL object or a Lucene Query String. Output includes Matched and Explanation.
  • Explain Index Lifecycle Reports the lifecycle state of an index, with its Policy, Phase and Age. Turn on Only Errors to see only stuck indices, or Only Managed to leave out those with no policy.
  • Flush All Indices Triggers a flush on all indices. Turn on Force to flush even when there are no changes to commit.
  • Flush Index Flushes one index, or a list or pattern of them. Turn off Wait If Ongoing to fail instead of waiting for a flush already running.
  • Force Merge Index Merges an index down to Maximum Segments per shard, where 1 gives the fastest searches. Run it only on indices that no longer receive writes.
  • Get a Component Template Reads a component template, or one per match when a wildcard is used. Output includes the Name, Version, Template and Created Date.
  • Get a Data Stream Reads a data stream, or one result per match for a pattern such as logs-*. Output includes Health, Generation, Index Template, ILM Policy and Backing Indices.
  • Get a Data Stream Lifecycle Reads the lifecycle of a data stream, giving a Data Stream and its Lifecycle for each match. Turn on Include Defaults to also show settings that keep their default value.
  • Get a Document Fetches a document by Document ID from an index. Output includes Found, Version, Source and Stored Fields. Add Source Fields to Include to return only fields like user.id, or Source Fields to Exclude to leave out a large body field.
  • Get a Document Source Fetches the stored Source of a document without its metadata, with optional Source Fields to Include and Source Fields to Exclude. Turn off Real Time to read only refreshed data.
  • Get a Mapping Returns the mapping for an index, with one result per index when a list or pattern is used.
  • Get a Node Describes a node. Output includes Node ID, Name, Host, IP, Version and Build Flavor. A filter such as master:true returns one result per match.
  • Get a Snapshot Reads snapshots from a Repository. Sort them with Sort By and Order, filter with States, and turn off Verbose for a shorter answer.
  • Get a Snapshot Repository Reads a snapshot repository, or one per match for a list or wildcard. Output includes Repository, Type, UUID and Settings.
  • Get a Task Checks the progress of a task, such as one started by Reindex Documents or Delete Documents by Query. Turn on Wait for Completion to wait, up to Timeout, until it finishes.
  • Get All Mappings Reads the field mappings of all indices as one result per Index. Use Include to pick which kinds of indices are read, and Limit to cut the number returned.
  • Get All Settings Reads the settings of all indices, with Settings and Defaults for each Index. Use Flat Settings for dotted keys instead of nested objects.
  • Get an ILM Policy Reads a lifecycle policy, or one per name when several are mapped. Output includes Policy Name, Version, Policy and In Use By.

Pinecone modules

  • Cancel a Bulk Import Stops a bulk import that is still running into an index.
  • Cancel a Conversion Job Stops a running index conversion job.
  • Chat with an Assistant Asks an assistant a question and gets an answer built from its files, with Citations. Send one Message or a whole Messages conversation, and choose the Model and Temperature.
  • Convert an Index Starts a conversion of a pod index into a new index called New Index Name, with the schema from Fields. Use On Error to choose what happens to records that cannot convert.
  • Create a Backup Takes a backup of an index and labels it with an optional Name and Description.
  • Create a Backup Schedule Sets up automatic backups of an index under Name, repeating at a Frequency and keeping each backup for Keep For Days.
  • Create a Bulk Import Loads records from a Storage URI into an index in the background, billed per record. Use Integration ID for a private bucket and On Error for failed records.
  • Create a Namespace Makes a namespace inside an index under Name. A Schema can list which fields are filterable.
  • Create a Namespace Alias Adds an alias called Alias Name that points to a Target Namespace, so callers can use one stable name.
  • Create a Vector Index Builds an index of a chosen Vector Type in a Cloud and Region, with a Dimension and similarity Metric. Turn on Deletion Protection and add Tags if wanted.
  • Create an Assistant Sets up an assistant under a Name, with optional Instructions, Region and Metadata.
  • Create an Index Makes a serverless index in a Cloud and Region from the Fields of its schema. Turn on Deletion Protection to block removal and add Tags to label it.
  • Create an Index from a Backup Restores a backup into a fresh index named New Index Name. Follow the restore with the Restore Job ID that is returned.
  • Delete a Backup Removes a stored backup of an index.
  • Delete a Backup Schedule Deletes a recurring backup schedule of an index.
  • Delete a Namespace Deletes a namespace together with the data inside it.
  • Delete a Namespace Alias Removes an alias that pointed at a namespace.
  • Delete All Documents Clears out one namespace by deleting all of its documents once Confirm is turned on.
  • Delete All Vectors in a Namespace Empties one namespace of its vectors after you turn on Confirm.
  • Delete an Assistant Removes an assistant. This cannot be undone.
  • Delete an Assistant File Removes one uploaded file of an assistant.
  • Delete an Index Deletes an index. This cannot be undone, and it fails while deletion protection is on.
  • Delete Documents Removes documents from a namespace, either the Document IDs given or those matching a Filter.
  • Delete Vectors Removes a batch of vectors from an index by their Vector IDs.
  • Delete Vectors by Metadata Deletes the vectors whose metadata satisfies a Filter.
  • Fetch Documents Pulls documents from a namespace, optionally for given Document IDs or a Filter, returning only the Include Fields requested.
  • Fetch Vectors Retrieves vectors by Vector IDs, returning their Values and Metadata.
  • Fetch Vectors by Metadata Shows the vectors whose metadata matches a Filter, with their Values and Metadata.
  • Generate Embeddings Turns Texts into vectors with an embedding Model. Use Input Type and Truncate to tune the call and read Total Tokens for the usage.
  • Get a Backup Fetches a backup with its Name, Description and Source Index Name.
  • Get a Backup Schedule Checks a recurring backup schedule and shows its Name and Schedule Type.
  • Get a Bulk Import Checks one bulk import and reports its Status and Percent Complete.
  • Get a Conversion Job Checks an index conversion and shows its Source Index Name and Target Index Name.
  • Get a Model Retrieves one inference model with its Short Description, Type and Default Dimension.
  • Get a Namespace Looks up one namespace and reports its Record Count and Size Bytes.
  • Get a Namespace Alias Looks up an alias and shows the Target Namespace it points to.
  • Get a Restore Job Checks a restore job, showing its Status and Target Index Name.
  • Get an Assistant Shows one assistant with its Name, Instructions, Status and Host.
  • Get an Assistant File Looks up one assistant file, returning its Name and Size. Turn on Include Download URL to also get a download link.
  • Get an Assistant Operation Checks an assistant operation such as a file upload, reporting its Operation Type and Status.
  • Get an Index Pulls an index with its Host, Status, Deployment and Schema.
  • Get Index Stats Counts the vectors of an index, giving the Total Vector Count, Dimension and Index Fullness. A Filter counts only matching vectors.
  • List Assistant Files Shows the files uploaded to an assistant, with a Name and Size for each. Use Metadata Filter to keep matching files.
  • List Assistant Operations Gathers the operations run on an assistant, such as uploads, optionally for one Operation Type or Status.
  • List Assistants Shows your assistants with their Name, Status and Host.
  • List Backup Schedule History Gathers the backups that a schedule produced, each with its Backup ID and Name.
  • List Backup Schedules Reads the recurring backup plans of an index, each with a Name and Schedule Type.
  • List Backups Pulls the backups stored for an index, naming each by Name and Description. Turn on Include Deleted to see removed ones.
  • List Bulk Imports Collects the bulk imports run against an index, showing Status and Percent Complete.
  • List Conversion Jobs Returns index conversion jobs with their Source Index Name and Target Index Name.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with Elastic and Pinecone integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Elastic and Pinecone on WEXTL®

Claim your 3-day trial to build Elastic with Pinecone integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting Elastic and Pinecone.

How do I connect Elastic and Pinecone?

Connect your Elastic and Pinecone accounts once, pick an action in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between Elastic and Pinecone?

Example: use the Elastic "Analyze Index Text" action to perform the Pinecone "Cancel a Bulk Import" action. Elastic has 123 actions (including Analyze Index Text, Analyze Text, and Bulk Index Documents). Pinecone has 77 actions (including Cancel a Bulk Import, Cancel a Conversion Job, and Chat with an Assistant). Add filters and transforms between steps when you need them.[1]

Can I use a Elastic action to perform a Pinecone action?

Yes. Pick an action in either app, then an action in the other, and map the fields between them.[2]

Do I need to write code to integrate Elastic and Pinecone?

No. Elastic-to-Pinecone automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does Elastic integrate with Pinecone in real time?

Yes. Trigger-based automations start the moment Elastic (or Pinecone) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a Elastic + Pinecone integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect Elastic with Pinecone?

You can build your Elastic + Pinecone automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the Elastic and Pinecone integration.

  1. Elastic and Pinecone integration source code, module specs and credentials implementation.
  2. Our Elastic and Pinecone integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Elastic and Pinecone, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. Elastic integration information
  6. Pinecone integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted Elastic and Pinecone integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Elastic and Pinecone, or get started