Start free
ActionAnthropicUpdated June 2026

How do I check the status of an Anthropic message batch?

Short answer: You can get message batch in Anthropic by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Anthropic Get Message Batch action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Use this actionAll 21 Anthropic actions
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Batch ID
batch_id
stringRequiredBatch ID. Example: batch_abc123
Sample request
{
  "batch_id": "e.g. batch_abc123"
}
Returns
{
  "id": "batch_abc123",
  "type": "message_batch",
  "ended_at": "2026-04-17T12:00:00Z",
  "request_counts": {
    "errored": 0,
    "expired": 0,
    "canceled": 0,
    "succeeded": 10,
    "processing": 0
  },
  "processing_status": "ended"
}

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

Triggered by

Apps that pair well as the trigger for Get Message Batch.

Any of these apps can fire this action as part of a workflow.

Gmail → Anthropic
1 Gmail triggers
Slack → Anthropic
13 Slack triggers
Google Sheets → Anthropic
2 Google Sheets triggers
HubSpot → Anthropic
18 HubSpot triggers
FAQ

Questions about Get Message Batch.

What does the Get Message Batch action do in Anthropic?
Gets the status of a message batch: processing_status, request_counts, and (when complete) the results_url to download. Poll until status is "ended".
What inputs does Get Message Batch require?
Required: Batch ID. 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 Anthropic 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 Get Message Batch support batch operations?
Yes. Run Get Message Batch inside a Loop node to process arrays. TinyCommand handles Anthropic's rate limits automatically so you don't have to throttle manually.
More actions

Other Anthropic actions.

Action
Analyze Image
Sends an image to Claude for analysis (vision), via URL or base64 bytes alongside a text prompt. Use for OCR, chart extraction, accessibility alt-text, or visual QA flows.
Action
Cancel Message Batch
Cancels a message batch that is still processing. Already-completed entries in the batch keep their results; in-flight ones get cancelled with no charge.
Action
Computer Use
Sends a message with the computer-use tool, letting Claude take screenshots and click/type on a virtual desktop. Requires Opus 4.x or Sonnet 4.x; you provide the sandboxed desktop environment.
Action
Count Tokens
Counts the number of tokens a Messages API call would consume without actually sending the message. Useful for cost estimation and to stay under context-window limits.
Action
Create Message
Sends a message to a Claude model and gets a response. The core Anthropic action; supports system prompts, multi-turn conversation, temperature, and stop sequences.
Action
Create Message Batch
Creates a batch of messages for async processing on the Messages API, with a 50% cost reduction and up to 24-hour turnaround. Perfect for bulk classification, summarization, or labeling jobs.