Create Vector Store: OpenAI 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
Name name	string	Required	Product Docs Q4
File IDs file_ids	array	Optional	Files (already uploaded with purpose=assistants) to attach
Expires After (days) expires_after_days	string	Optional	Auto-expire after N days of last activity. Leave empty for no expiry.

Sample request

{
  "name": "Product Docs Q4",
  "file_ids": "{{trigger.file_ids}}",
  "expires_after_days": "7"
}

Returns

{
  "id": "vs_abc",
  "name": "Product Docs Q4",
  "status": "in_progress",
  "file_counts": {
    "total": 5,
    "failed": 0,
    "completed": 0
  }
}

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

FAQ

Questions about Create Vector Store.

What does the Create Vector Store action do in OpenAI?

Creates a vector store (used by the File Search tool in Responses/Assistants). OpenAI handles chunking, embedding, and indexing of any files you attach.

What inputs does Create Vector Store require?

Required: 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 OpenAI 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 Create Vector Store support batch operations?

Yes. Run Create Vector Store inside a Loop node to process arrays. Tiny Command handles OpenAI's rate limits automatically so you don't have to throttle manually.

More actions