Skip to content
For LLMsView as Markdown·

Pinecone ​

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

DetailValue
CategoryAI
Base URLhttps://api.pinecone.io
AuthenticationAPI Key
Endpoints4
Connector keypinecone

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 ​

EndpointSummary
GET /databasesList all indexes
POST /databasesCreate 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

DetailValue
Operation IDai.listIndexes
MethodGET
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

DetailValue
Operation IDai.createIndex
MethodPOST
Path/databases

Parameters ​

No parameters.

Request Body ​

FieldType
namestring
dimensioninteger
metricstring

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

DetailValue
Operation IDai.describeIndex
MethodGET
Path/databases/{indexName}

Parameters ​

NameLocationTypeRequired
indexNamepathstringYes

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

DetailValue
Operation IDai.deleteIndex
MethodDELETE
Path/databases/{indexName}

Parameters ​

NameLocationTypeRequired
indexNamepathstringYes

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.