Delete Pinecone Vectors: Pinecone action

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
Vector IDs (JSON array) ids	string	Optional	Array of vector IDs to delete
Namespace namespace	string	Optional	Namespace. Example: default
Delete All deleteAll	options	Optional	Delete all vectors in the namespace

Sample request

{
  "ids": "[\"doc1\", \"doc2\"]",
  "namespace": "e.g. default",
  "deleteAll": "{{trigger.deleteAll}}"
}

Returns

{
  "success": true
}

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

FAQ

Questions about Delete Pinecone Vectors.

What does the Delete Pinecone Vectors action do in Pinecone?

Removes vectors by ID list, by metadata filter, or by namespace. For "user churned → delete all their vectors" tenant-isolation workflows.

What inputs does Delete Pinecone Vectors require?

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

Yes. Run Delete 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