Make API Call: 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
Method method	options	Required	Method. Options: GET, POST, PUT, PATCH, DELETE
Path path	string	Required	API path (appended to https://api.anthropic.com)
Request Body body	json	Optional	JSON body (for POST/PUT/PATCH)
Beta Header beta	string	Optional	Optional anthropic-beta header for beta features

Sample request

{
  "method": "{{trigger.method}}",
  "path": "e.g. /v1/messages",
  "body": "e.g. Hi there, thanks for reaching out.",
  "beta": "e.g. files-api-2025-04-14"
}

Returns

{
  "data": {},
  "type": "response"
}

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

FAQ

Questions about Make API Call.

What does the Make API Call action do in Anthropic?

Makes a custom API call to any Anthropic endpoint with method, path, headers, and body. The escape hatch for newly-released APIs or fields that the typed actions don't yet expose.

What inputs does Make API Call require?

Required: Method, Path. 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 Make API Call support batch operations?

Yes. Run Make API Call 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