Get Model: Anthropic 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
Model ID model_id	string	Required	Model ID. Example: claude-sonnet-4-6-20250514

Sample request

{
  "model_id": "e.g. claude-sonnet-4-6-20250514"
}

Returns

{
  "id": "claude-sonnet-4-6-20250514",
  "type": "model",
  "created_at": "2025-05-14T00:00:00Z",
  "display_name": "Claude Sonnet 4.6"
}

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

FAQ

Questions about Get Model.

What does the Get Model action do in Anthropic?

Returns metadata about a specific Claude model (display name, context window, deprecation status). Useful for surfacing model availability in your UI.

What inputs does Get Model require?

Required: Model 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 Model support batch operations?

Yes. Run Get Model inside a Loop node to process arrays. Tiny Command handles Anthropic's rate limits automatically so you don't have to throttle manually.

More actions