Upsert Vectors
pinecone.upsert
ActionDatabases & warehousesconnection required
Calls the Pinecone data API POST /vectors/upsert.
Upsert vectors (with metadata) into a Pinecone index.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Pinecone
- Secret shape
- the Pinecone API key
- Config it needs
- index_host, namespace
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
vectors Vectors: [{id, values:[...], metadata?}]. JSON. | array | Yes | — | array of object | — |
namespace Namespace (overrides connection). | string | No | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok | boolean | — |
upserted_count | number | — |
{
"ok": false,
"upserted_count": 0
}Related Pinecone nodes
See Upsert Vectors run in a workflow.
In a technical demo we add the Pinecone connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.