OtherReal-timeUpdated May 2026

Pinecone

Pinecone vector database for RAG workflows

Pinecone is the managed vector database for similarity-search workloads — RAG (retrieval-augmented generation), semantic search, recommendation, anomaly detection. Tiny Command exposes six actions covering the read/write surface against an index: List Indexes (all indexes in the project), Describe Index (the dimension, metric, host, and status), Describe Index Stats (vector count by namespace, useful for capacity planning), Upsert Vectors (batch insert/update with optional metadata and namespace), Query Vectors (k-nearest-neighbours with optional metadata filter), and Delete Vectors (by ID list, by metadata filter, or by namespace). The connection uses a Pinecone API key plus the environment (legacy pod-based indexes carry an environment like us-east-1-aws; serverless indexes use a host URL). Upsert Vectors batches up to 100 vectors per call (Pinecone's recommended chunk); larger workflows should pre-batch in the upstream step. Query Vectors with namespace + filter is the standard RAG retrieval shape — fetch top-k vectors with score and metadata, pass the metadata into the LLM prompt.

Connect Pinecone

0triggers

6actions

≈ 2 minto set up

Freetier · no card

Actions

Do anything Pinecone can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs
Delete Pinecone Vectors	Removes vectors by ID list, by metadata filter, or by namespace. For "user churned → delete all their vectors" tenant-isolation workflows.	3 fields	View →
Describe Pinecone Index	Returns the index's dimension, metric, host, status. Useful for "is the index ready?" pre-flight checks before query workflows.	1 fields	View →
Describe Pinecone Index Stats	Returns vector count by namespace. Useful for capacity planning and for "did the bulk insert succeed?" post-operation verification.	0 fields	View →
List Pinecone Indexes	Returns every index in the connected project. Useful for inventory and for resolving index names at workflow setup.	0 fields	View →
Query Pinecone Vectors	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.	4 fields	View →
Upsert Pinecone Vectors	Batch-inserts up to 100 vectors with metadata and namespace. For bulk ingestion >100, pre-batch upstream. The standard "embed content → index in Pinecone" step.	2 fields	View →

Recipes

Pre-built Pinecone workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Pinecone → Slack alerts

AI-triage every Pinecone event, ping the right channel only when it matters.

Pinecone → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Pinecone → Notion database

Turn Pinecone into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Pinecone once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Pinecone field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Pinecone integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Pinecone to Tiny Command?

Open the Tiny Command workflow builder, drop in a Pinecone node, and click Connect. Authorize Pinecone once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Pinecone triggers does Tiny Command support?

Tiny Command focuses on outbound actions for Pinecone today. Use Tiny Command's universal Webhook or Schedule trigger to start Pinecone workflows, then run any Pinecone action you need.

What Pinecone actions can I run from a workflow?

6 Pinecone actions are available out of the box, covering other operations like "Delete Pinecone Vectors". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Pinecone integration real-time?

Pinecone actions execute synchronously inside your workflow. Tiny Command waits for Pinecone's API to confirm before continuing to the next step, so downstream nodes can rely on the result.

Do I need to write code to use Pinecone with Tiny Command?

No. Every Pinecone trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Pinecone API endpoint directly.

How much does the Pinecone integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Pinecone integration itself has no per-app surcharge.