
Pinecone
Upsert, update, fetch, list and query vectors and namespaces in a Pinecone index for semantic search and RAG.
Keep a vector index in step with business records so search and AI assistants use current data.
Source actions
7
Destination actions
4
Data types
5
Validation status
Implemented · fixture tested.
Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.
What you can map
index stats
- Get index statisticsSource
Vector counts per namespace, dimension, metric and fullness, optionally for vectors matching a filter.
namespaces
- Create namespaceDestinationDuplicate protected
Creates a namespace, optionally declaring which metadata fields are indexed for filtering.
- Get namespaceSource
Record count, size and metadata schema for one namespace.
- List namespacesSource
Namespaces in a serverless index with record counts.
vector batches
- Upsert vectors in batchDestinationDuplicate protected
Creates or replaces up to 500 vectors by ID in one request.
vector ids
- List vector IDsSource
Vector IDs in a namespace, optionally by ID prefix (serverless indexes).
vectors
- Fetch vectorSource
Fetches one vector with its values and metadata by ID.
- Fetch vectors by metadataSource
Pages through vectors whose metadata matches a filter.
- Query vectorsSource
Finds the most similar vectors to a query vector or an existing vector ID, with an optional metadata filter.
- Update vectorDestinationDuplicate protected
Updates one vector's values or merges metadata fields by ID; unspecified metadata is kept.
- Upsert vectorDestinationDuplicate protected
Creates or replaces one vector by ID with values and metadata.
Authentication
Pinecone API key
Plans and access
Starter (free), Standard and Enterprise projects. Vector ID listing and namespace operations are supported only on serverless indexes.
Test environment
The Starter plan can be used for testing.
Rate limits
Per-index read and write unit limits and request size limits (upsert up to 1,000 records or 2 MB); HTTP 429 when exceeded.
Provider events
Pinecone does not deliver data webhooks. Nexra event triggers are not yet available; flows run on demand or on a schedule.
Before you build a flow
- Each connection targets one index host. Control-plane operations on api.pinecone.io (list, describe and create indexes) are not available because a recipe has a single API origin.
- Integrated inference, the records and documents APIs, bulk import, backups and deletes are not exposed.
- Fetch reads one vector ID per call because the engine sends single-valued query parameters.
- API version 2026-07 is pinned.