Linking Pinecone as a source
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
Contents
The Pinecone connector syncs your vector database data – indexes, collections, backups, restore jobs, namespaces, assistants, and assistant files – into PostHog, so you can analyze your AI infrastructure alongside your product data.
Note: Individual vectors and records are not synced. Fetching records would consume Pinecone read units on every sync, so the connector syncs metadata tables only.
Prerequisites
You need a Pinecone account with access to the Pinecone API. You'll need an API key from your Pinecone project.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
When linking Pinecone, you'll need:
- API key – found in your Pinecone console under your project settings.
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
indexes | Configuration and status of indexes in the connected Pinecone project. | Full refresh | — | — |
collections | Collections containing snapshots of pod-based indexes in the connected Pinecone project. | Full refresh | — | — |
backups | Backup inventory for the connected Pinecone project. | Full refresh | — | — |
restore_jobs | Progress and results of backup restore jobs in the connected Pinecone project. | Full refresh | — | — |
namespaces | Namespaces in each ready serverless or BYOC index of the connected Pinecone project. | Full refresh | — | — |
assistants | Pinecone Assistants in the connected project. | Full refresh | — | — |
assistant_files | Files uploaded to each ready Pinecone Assistant in the connected project. | Full refresh | — | — |
Troubleshooting
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.