Pinecone

Vector database API for similarity search. Manage indexes, upsert vectors, and query embeddings.

Detail	Value
Category	AI
Base URL	https://api.pinecone.io
Authentication	API Key
Endpoints	4
Connector key	pinecone

Using Pinecone in a workflow

1. Go to Connections and click New Connection.
2. Pick Pinecone from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
GET /databases	List all indexes
POST /databases	Create an index
GET /databases/{indexName}	Describe an index
DELETE /databases/{indexName}	Delete an index

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /databases

List all indexes

Detail	Value
Operation ID	ai.listIndexes
Method	GET
Path	/databases

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Pinecone connection from the Connection dropdown.
3. In the Operation dropdown, select ai.listIndexes.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Pinecone API reference.

POST /databases

Create an index

Detail	Value
Operation ID	ai.createIndex
Method	POST
Path	/databases

Parameters

No parameters.

Request Body

Field	Type
name	string
dimension	integer
metric	string

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Pinecone connection from the Connection dropdown.
3. In the Operation dropdown, select ai.createIndex.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Pinecone API reference.

GET /databases/{indexName}

Describe an index

Detail	Value
Operation ID	ai.describeIndex
Method	GET
Path	/databases/{indexName}

Parameters

Name	Location	Type	Required
indexName	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Pinecone connection from the Connection dropdown.
3. In the Operation dropdown, select ai.describeIndex.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Pinecone API reference.

DELETE /databases/{indexName}

Delete an index

Detail	Value
Operation ID	ai.deleteIndex
Method	DELETE
Path	/databases/{indexName}

Parameters

Name	Location	Type	Required
indexName	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Pinecone connection from the Connection dropdown.
3. In the Operation dropdown, select ai.deleteIndex.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Pinecone API reference.