Short answer: Drop the "OpenAI → Get Batch" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Batch ID batch_id | string | Required | batch_abc123 |
{"batch_id": "batch_abc123"}
{"id": "batch_abc","status": "completed","output_file_id": "file-out","request_counts": {"total": 100,"failed": 0,"completed": 100}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.