Start free
ActionPineconeUpdated June 2026

How do I get Pinecone index info?

Short answer: You can describe pinecone index in Pinecone by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Pinecone Describe Pinecone Index action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Describe Pinecone Index in Pinecone — start free All 6 Pinecone actions
Describe Pinecone Index 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.

FieldTypeRequiredDescription
Index Name
indexName
stringRequiredIndex Name
Sample request
{
  "indexName": "{{trigger.indexName}}"
}
Returns
{
  "host": "my-index-abc123.svc.pinecone.io",
  "name": "my-index",
  "spec": {
    "pod": {
      "pod_type": "p1.x1",
      "environment": "us-east1-gcp"
    }
  },
  "metric": "cosine",
  "status": {
    "ready": true,
    "state": "Ready"
  },
  "dimension": 1536
}

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

Triggered by

Apps that pair well as the trigger for Describe Pinecone Index.

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

Gmail → Pinecone
1 Gmail triggers
Slack → Pinecone
13 Slack triggers
Google Sheets → Pinecone
2 Google Sheets triggers
HubSpot → Pinecone
18 HubSpot triggers
FAQ

Questions about Describe Pinecone Index.

What does the Describe Pinecone Index action do in Pinecone?
Returns the index's dimension, metric, host, status. Useful for "is the index ready?" pre-flight checks before query workflows.
What inputs does Describe Pinecone Index require?
Required: Index Name. 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 Describe Pinecone Index support batch operations?
Yes. Run Describe Pinecone Index inside a Loop node to process arrays. TinyCommand handles Pinecone's rate limits automatically so you don't have to throttle manually.
More actions

Other Pinecone actions.

Action
Delete Pinecone Vectors
Removes vectors by ID list, by metadata filter, or by namespace. For "user churned → delete all their vectors" tenant-isolation workflows.
Action
Describe Pinecone Index Stats
Returns vector count by namespace. Useful for capacity planning and for "did the bulk insert succeed?" post-operation verification.
Action
List Pinecone Indexes
Returns every index in the connected project. Useful for inventory and for resolving index names at workflow setup.
Action
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.
Action
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.
Describe Pinecone Index in Pinecone — start free