Start free
ActionPineconeUpdated September 2026

How do I get Pinecone vector counts?

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

Describe Pinecone Index Stats in Pinecone — start free All 6 Pinecone actions
Describe Pinecone Index Stats in Pinecone — start free
Sample request
{}
Returns
{
  "dimension": 1536,
  "namespaces": {
    "default": {
      "vectorCount": 10000
    }
  },
  "indexFullness": 0.1,
  "totalVectorCount": 10000
}

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 Stats.

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 Stats.

What does the Describe Pinecone Index Stats action do in Pinecone?
Returns vector count by namespace. Useful for capacity planning and for "did the bulk insert succeed?" post-operation verification.
What inputs does Describe Pinecone Index Stats require?
Describe Pinecone Index Stats has no required inputs. Sensible defaults are applied if you leave fields blank.
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 Describe Pinecone Index Stats support batch operations?
Run Describe Pinecone Index Stats 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

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
Returns the index's dimension, metric, host, status. Useful for "is the index ready?" pre-flight checks before query workflows.
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 Stats in Pinecone — start free