Resources · Zapier integration

Pinecone Zapier integrationAutomate Pinecone with Zapier.

The Pinecone Zapier integration offers 1 trigger, 8 actions and 7 searches to feed a vector database from your everyday tools: add text records, keep them up to date, search them by meaning and look after your indexes, without writing a line of code.

See the 16 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Pinecone Zapier integration is for

Pinecone is a vector database: it stores text as records inside an index, split into namespaces, so an AI assistant can later find passages by meaning rather than by exact words. Zapier lets your other tools write into it and read from it, so the knowledge your AI relies on stays current without a developer in the loop.

Three results justify the setup. A knowledge base that fills itself: Add Record turns a piece of text into a vector and stores it in one step, so every new help article or meeting note lands in the index. Answers pulled from your own content: Search Records takes a question in plain words and returns the closest records, ready for the next step of the Zap. Records that follow reality: Update Record and Delete Record fix or remove a record when its source changes.

Now the limits. There is a single trigger, and it only watches the status of indexes, not new records. It is a polling trigger, checked on a timer. Several useful steps want the index host URL on top of its name, which most people do not have at hand. And the integration manages Pinecone; it does not write the prompt or call the AI model that will use the results.

Comparing tools first? The n8n vs Zapier and Make vs Zapier pages are there.

Vocabulary

Zapier vocabulary, quickly

The page leans on seven Zapier words. One line each, then they are used without reminder.

Zap
An automation built in Zapier: one trigger, then one or more actions that run every time that trigger event happens.
Trigger
The event that starts the Zap. With Pinecone, it is an index changing status. Once the Zap is on, Zapier waits for it.
Action
The work the Zap does once started: adding a record, deleting a namespace, creating an index, in Pinecone or another app.
Task
What Zapier bills: one action completed successfully. The monthly allowance of your plan is a count of those.
Polling vs instant
Polling means Zapier asks the app for news at a fixed interval; instant means the app reports the event itself. Pinecone's trigger polls.
Filter
A step that only lets the Zap go on when the incoming data meets the condition you set; otherwise the run stops there.
Search step
A step that looks up something already in Pinecone, an index, a namespace or records, and hands it to the steps after it.
Cost

What it really costs

Pinecone is not reserved to paid plans: the integration runs on Zapier's free plan. You pay in tasks.

  • Tasks on the free plan100 a month
  • Steps on the free plan2: one trigger, one action
  • Pinecone on freeYes, not a paid-only app
  • Instant triggers0 of 1

Checking the trigger never costs anything, however often Zapier looks. Each action that succeeds counts as one task, and a failed one is not counted. The free plan gives 100 tasks a month, unlimited Zaps, a check every 15 minutes and two-step Zaps only: one trigger, one action. A search before the action, a filter or a second action makes the Zap multi-step, and that needs a paid plan. Most Pinecone scenarios with Search Records fall in that case.

Connect

Connect Pinecone to Zapier in three steps

  1. 01

    Start from your apps

    Open the Apps page of your Zapier account and click + Add connection. The connection links your Pinecone account once; every Pinecone step of every Zap then reuses it.

  2. 02

    Find Pinecone

    Search for Pinecone in the dialog, pick it, then confirm with Add connection. A Pinecone account is required beforehand: Zapier does not open one for you.

  3. 03

    Sign in and grant access

    Log in to Pinecone in the tab that opens and allow Zapier into the account. For indexes a colleague created, check that your access lets you read them, or write to them if the Zap adds records.

First Zap

Your first Zap: seed an index once it is ready

GoalWhen an index changes status and is ready, a first reference text is stored in it.

  1. 01

    Pick the trigger

    Create a Zap, choose Pinecone and the Index Status Change event, then select the Pinecone connection you set up a moment ago.

  2. 02

    Test it on real data

    Run the trigger test. Zapier brings back the three most recent items from your account, so you map the next steps on a real index rather than a guess.

  3. 03

    Add the filter

    Add a Filter step and set it so the Zap goes on only when the status returned means the index is ready. This step makes the Zap multi-step: paid plan.

  4. 04

    Add the record

    Add Add Record. Map the index name from the trigger, type the namespace, and put the reference text you want stored first in Record Text.

  5. 05

    Test, then publish

    Test the action and check the record in Pinecone. Then publish to switch the Zap on; only status changes after that moment will run it.

Triggers

The Pinecone trigger

1 event starts a Zap when something happens in Pinecone. Zapier checks for them at the interval your plan allows.

1

Index Status Change

Polling trigger

In Zapier“Triggers when the status of any Pinecone index changes.”

Starts a Zap whenever the status of any index in your Pinecone project changes, for example while a new index is being prepared. It is the only trigger of the app, and it watches indexes, never the records inside them.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
your team wants a message, or a first record loaded, once a freshly created index is up.
Watch out
it covers every index of the project, so add a filter if only one of them matters, and never point Configure Index at the index this Zap watches.
Actions

The 8 Pinecone actions

Pinecone gives you 8 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add Record

Action

In Zapier“Embeds a record and upserts it to Pinecone in one step.”

Converts a piece of text into a vector and stores it in the index in one go. Record Text, Index Name and Namespace are required.

When to use it
each new help-centre article should become searchable by your support chatbot.
Watch out
keep the ID it returns somewhere, since Update Record and Delete Record need it later.
2

Configure Index

Action

In Zapier“Configures a Pinecone index (e.g., pod type, replicas, deletion protection, tags).”

Adjusts the settings of an index you name, such as replicas, deletion protection or tags.

When to use it
once an index goes into production use, switch deletion protection on so a later Zap cannot wipe it.
Watch out
changing an index can change its status, which wakes Index Status Change if a Zap listens to it.
3

Create Index

Action

In Zapier“Creates a new Pinecone index with specified configuration.”

Builds a new index from a name and a model. The name must be unique in your project, and an optional box makes the step wait until the index is ready.

When to use it
every new client project gets its own index the day it is opened in your project tool.
Watch out
a name already taken fails the step.
4

Delete Index

Action

In Zapier“Deletes a Pinecone index.”

Deletes an entire Pinecone index, identified by its name alone.

When to use it
a closed project in your management tool should free its index without a manual cleanup.
Watch out
this is the heaviest step of the app; deletion protection, set with Configure Index, is your safety net.
5

Delete Namespace

Action

In Zapier“Deletes all vectors in a Pinecone namespace.”

Empties a whole namespace: every vector it holds is deleted. It asks for Index Name, Index Host and Namespace.

When to use it
a client leaves and all of their documents must go in one move.
Watch out
one wrong mapping clears the wrong namespace, and nothing comes back.
6

Delete Record

Action

In Zapier“Deletes a record (vector) from Pinecone by ID.”

Removes one record, found by its Record ID, from a given index and namespace. The Index Host is required too.

When to use it
a page unpublished from your site must stop feeding answers to your assistant.
Watch out
the deletion is final, so test with a throwaway record first.
7

Update Record

Action

In Zapier“Updates the text and/or metadata for a record in Pinecone.”

Changes the text, the metadata or both on an existing record, located by Record ID, Index Name and Namespace.

When to use it
a document edited in your wiki should replace its old version in Pinecone instead of piling up next to it.
Watch out
without the Record ID from Add Record or your own, there is nothing to update.
8

API Request (Beta)

Action

In Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”

An advanced step for what the other actions do not cover: it sends a raw request to Pinecone with your existing connection. You set the method and the address, limited to domains tied to Pinecone.

When to use it
a technical teammate needs one Pinecone feature that has no ready-made action.
Watch out
with Stop on error set to No, the Zap carries on even when Pinecone refuses.
Searches

The 7 Pinecone searches

7 search steps look for data that already exists in Pinecone, so a later step can use it.

A search step reads what already exists in Pinecone and passes it to the next steps. In the editor, searches sit at the bottom of the Action event list, under SEARCH. Four of them carry the Advanced label: Pinecone itself flags them as rarely needed. Three settings decide what happens when the result is not the expected one.

1

Advanced: Describe Index

Search

In Zapier“For power users: Returns detailed configuration and status for a Pinecone index. Not needed for most Zapier workflows.”

Returns the full configuration and current status of one index, from its name.

When to use it
before adding records, a Zap checks how the index is set up.
Watch out
Pinecone presents it as a power-user search; most Zaps do fine without it.
2

Advanced: Describe Index Stats

Search

In Zapier“For power users: Returns detailed statistics for a Pinecone index. Not needed for most Zapier workflows.”

Brings back detailed statistics on an index, with its name and Index Host.

When to use it
a periodic report to your data lead should show how the index is growing.
Watch out
without the host URL, the step cannot run.
3

Advanced: Describe Namespace

Search

In Zapier“For power users: Returns detailed information about a Pinecone namespace. Not needed for most Zapier workflows.”

Gives detailed information about one namespace inside an index. Index Name, Index Host and Namespace are required.

When to use it
before emptying a client's namespace, a Zap first reads what it holds.
Watch out
it reads, it never changes anything, so it is a safe check before Delete Namespace.
4

List Indexes

Search

In Zapier“Lists all Pinecone indexes in your project.”

Lists every index of your Pinecone project, with no box to fill.

When to use it
an inventory Zap writes the indexes into a sheet so nobody loses track of them.
Watch out
it returns several items, so set the multiple-results option to pass them all if the list is the point.
5

List Namespaces

Search

In Zapier“Lists all namespaces in a Pinecone index.”

Lists the namespaces of one index, given its name and host URL.

When to use it
you split clients by namespace and want to check which ones exist before adding a record.
Watch out
by default only the first namespace goes on.
6

Advanced: List Records

Search

In Zapier“For power users: Lists all records in a Pinecone index. Not needed for most Zapier workflows.”

Lists all records stored in one namespace of an index. Index Name, Index Host and Namespace are needed.

When to use it
an audit compares what Pinecone holds with your source documents.
Watch out
flagged for power users; for finding content by meaning, Search Records is the right tool.
7

Search Records

Search

In Zapier“Searches for records in a Pinecone index using a text query.”

Finds the records closest in meaning to a text query. You set the index, the namespace, the Query Text and Top K, the number of best results to return.

When to use it
a question arriving by email pulls the matching passages from your documentation.
Watch out
with Top K above one, set the multiple-results option or only the first result goes on.

The three settings every search exposes

  1. Successful if no search results are found?
    By default, a search that comes back empty stops the Zap and skips the steps that rely on it. Switched on, the Zap continues with nothing in hand.
  2. Create X if it doesn't exist yet?
    This box would turn a search into a find-or-create. Pinecone has no such variant, so it does not appear on these searches.
  3. If multiple search results are found?
    When several items match: keep the first, which is the default, stop the Zap, or pass them all on. Search Records is where this matters most.
When it breaks

When it breaks

Zapier attaches a single help article to this app, How to get started with Pinecone on Zapier. The rest of what breaks comes from how Zapier works and from Pinecone's required fields.

  • Past changes are never picked up

    A Zap reacts only to what happens after you publish it. Indexes and records that already existed are not replayed; loading old documents is a separate job.

  • The configure loop

    Index Status Change plus Configure Index on the same index: the change of settings can change the status, which starts the Zap again, and the tasks go fast.

  • Missing Index Host

    Delete Record, Delete Namespace, List Namespaces and three searches need the index host URL. Leave it out and the step cannot be completed.

  • Duplicate index name

    Create Index requires a name unique within your project. A Zap that reuses a fixed name fails from its second run onwards.

  • A namespace wiped by mistake

    Delete Namespace removes every vector of the namespace. A wrong mapping clears the wrong client, so test it on a dummy namespace first.

  • Bulk changes held back

    After a migration or a burst of index changes, the trigger can return a large batch at once, and Zapier's flood protection may hold it back.
Need help

Need help automating Pinecone with Zapier?

A person reads every message.

FAQ

Pinecone and Zapier, the questions people ask

01Is the Pinecone Zapier integration free?
Yes, within the free plan's limits. Pinecone is not reserved to paid plans, so you get 100 tasks a month, unlimited Zaps and a check every 15 minutes. The limit is the shape of the Zap: one trigger and one action. A typical Pinecone use, where a question is searched with Search Records and the answer sent somewhere, needs a search plus an action, which makes the Zap multi-step and requires a paid plan. A plain feed with Add Record stays free.
02How many tasks does a Pinecone Zap use?
One task per action that succeeds, none for the trigger. Zapier can check the status of your indexes as often as your plan allows without counting anything. A Zap that adds one record per new document costs one task per document. An action that fails is not counted. Some apps and some actions use more than one task when they complete, so look at the number of actions in your Zap before choosing a plan.
03Is the Pinecone integration real time?
No. The only Pinecone trigger, Index Status Change, is a polling trigger: Zapier checks your indexes at a fixed interval. That interval depends on the plan, 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. On paid plans you can change how often it checks and launch a check by hand from the editor. Actions run when the Zap reaches them, so adding or searching records is not delayed by the plan.
04What do you need to connect Pinecone to Zapier?
A Pinecone account, and access to the indexes you did not create yourself. In Zapier, open the Apps page, click + Add connection, search for Pinecone and confirm with Add connection, then sign in to Pinecone in the new tab and grant access. Keep the host URL of each index close by: several actions and searches ask for that Index Host on top of the index name. The connection itself is made once, then every Pinecone step of every Zap reuses it.
05Does Add Record need vectors prepared beforehand?
No. Add Record takes plain text in Record Text, turns it into a vector and stores it in the chosen index and namespace in a single step. That is what makes the integration usable without a developer. On the index side, Create Index is where a Model is chosen. Note the Record ID that comes back, or set your own: Update Record and Delete Record both need it to target that record later.
06What if the Pinecone operation you need does not exist?
Zapier offers 16 Pinecone operations: 1 trigger, 8 actions and 7 searches. If yours is missing, try a combination first, for instance a search that fetches an index or a namespace and passes it to an action. For a feature with no ready-made step, API Request (Beta) sends a request to Pinecone through your existing connection, but it is meant for technical profiles. Beyond that, the Hack'celeration team can study the case with you.
07Zapier, Make or n8n for Pinecone?
Choose by criteria, not by reputation. Zapier gives you 16 ready-made Pinecone operations, one polling trigger on index status, and a free plan limited to one trigger plus one action. So check three things. Does your flow need a search and an answer in the same Zap, which means a paid plan here? Does it need to react to new records rather than index status? Does the other tool cover the Pinecone operations you will use? Verify that before deciding.
Same platform

Other docs you might need on this stack.

Browse all integrations