ActionPineconeUpdated September 2026

How do I run k-NN search in Pinecone?

Short answer: You can query pinecone vectors in Pinecone by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Pinecone Query Pinecone Vectors action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Query Pinecone Vectors in Pinecone — start free All 6 Pinecone actions

Query Pinecone Vectors in Pinecone — start free

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 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 Query Pinecone Vectors support batch operations?

Run Query 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