Create Batch: 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
Input File ID input_file_id	string	Required	JSONL file uploaded via /files with purpose=batch
Endpoint endpoint	options	Required	Which API the batch lines target
Completion Window completion_window	options	Optional	How long the batch may run

Sample request

{
  "input_file_id": "file-abc123",
  "endpoint": "{{trigger.endpoint}}",
  "completion_window": "{{trigger.completion_window}}"
}

Returns

{
  "id": "batch_abc",
  "status": "validating",
  "endpoint": "/v1/chat/completions",
  "input_file_id": "file-abc"
}

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

FAQ

Questions about Create Batch.

What does the Create Batch action do in OpenAI?

Submits a batch of OpenAI requests at a 50% cost discount with a 24-hour SLA. Requires an uploaded JSONL file id with one request per line. Perfect for bulk classification or embedding jobs.

What inputs does Create Batch require?

Required: Input File ID, Endpoint. 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 Batch support batch operations?

Yes. Run Create Batch 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