ActionPineconeUpdated September 2026
How do I add vectors to Pinecone?
Short answer: You can upsert pinecone vectors in Pinecone by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Pinecone Upsert Pinecone Vectors action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Namespace namespace | string | Optional | Partition within the index |
Vectors (JSON) vectors | string | Required | Array of vectors: [{"id": "doc1", "values": [0.1, 0.2, ...], "metadata": {"text": "..."}}] |
Sample request
{"namespace": "e.g. default","vectors": "[{\"id\": \"doc1\", \"values\": [0.1, 0.2, 0.3], \"metadata\": {\"source\": \"article\"}}]"}
Returns
{"upsertedCount": 1}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Upsert Pinecone Vectors.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Upsert Pinecone Vectors.
What does the Upsert Pinecone Vectors action do in Pinecone?
Batch-inserts up to 100 vectors with metadata and namespace. For bulk ingestion >100, pre-batch upstream. The standard "embed content → index in Pinecone" step.
What inputs does Upsert Pinecone Vectors require?
Required: Vectors (JSON). Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Pinecone returns an error?
The run history shows the failed step with its input and the error message Pinecone returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Upsert Pinecone Vectors support batch operations?
Run Upsert Pinecone Vectors inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Pinecone's rate limits.
More actions
Other Pinecone actions.
Action
Delete Pinecone Vectors
Removes vectors by ID list, by metadata filter, or by namespace. For "user churned → delete all their vectors" tenant-isolation workflows.
ActionDescribe Pinecone Index
Returns the index's dimension, metric, host, status. Useful for "is the index ready?" pre-flight checks before query workflows.
ActionDescribe Pinecone Index Stats
Returns vector count by namespace. Useful for capacity planning and for "did the bulk insert succeed?" post-operation verification.
ActionList Pinecone Indexes
Returns every index in the connected project. Useful for inventory and for resolving index names at workflow setup.
ActionQuery Pinecone Vectors
Returns top-k nearest vectors with scores and metadata, optionally filtered by metadata. The standard RAG retrieval call — fetch top vectors, pass metadata to LLM for grounded answers.