ActionPineconeUpdated May 2026

How do I run k-NN search in Pinecone?

Short answer: Drop the "Pinecone → Query Pinecone Vectors" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 6 Pinecone actions

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
Query Vector (JSON array) vector	string	Required	The embedding vector to search with
Top K topK	string	Required	Number of nearest results to return
Namespace namespace	string	Optional	Namespace. Example: default
Include Metadata includeMetadata	options	Optional	Include Metadata. Options: Yes, No

Sample request

{
  "vector": "[0.1, 0.2, 0.3, ...]",
  "topK": "10",
  "namespace": "e.g. default",
  "includeMetadata": "{{trigger.includeMetadata}}"
}

Returns

{
  "matches": [
    {
      "id": "doc1",
      "score": 0.95,
      "metadata": {
        "text": "Relevant document text..."
      }
    }
  ],
  "namespace": "default"
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Query Pinecone Vectors.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Pinecone

2 Google Sheets triggers

HubSpot → Pinecone

18 HubSpot triggers

FAQ

Questions about Query Pinecone Vectors.

What does the Query Pinecone Vectors action do in Pinecone?

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.

What inputs does Query Pinecone Vectors require?

Required: Query Vector (JSON array), Top K. 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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Query Pinecone Vectors support batch operations?

Yes. Run Query Pinecone Vectors inside a Loop node to process arrays. Tiny Command handles Pinecone's rate limits automatically so you don't have to throttle manually.

More actions