Short answer: Drop the "Anthropic → Create Message 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 |
|---|---|---|---|
Model model | options | Required | Model. Options: Claude Sonnet 4.6, Claude Opus 4.6, Claude Haiku 4.5 |
Prompt prompt | string | Required | The prompt to send to each item in the batch |
Max Tokens max_tokens | string | Optional | Max Tokens |
Custom ID custom_id | string | Required | Your unique ID for this batch request |
{"model": "{{trigger.model}}","prompt": "{{trigger.prompt}}","max_tokens": "{{trigger.max_tokens}}","custom_id": "e.g. request-001"}
{"id": "batch_abc123","type": "message_batch","request_counts": {"errored": 0,"expired": 0,"canceled": 0,"succeeded": 0,"processing": 1},"processing_status": "in_progress"}
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.