Get Call: Twilio action · Tiny Command

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
Call SID call_sid	string	Required	Call SID. Example: CA1234567890abcdef

Sample request

{
  "call_sid": "e.g. CA1234567890abcdef"
}

Returns

{
  "to": "+15551234567",
  "sid": "CA123",
  "from": "+15559876543",
  "status": "completed",
  "duration": "42",
  "start_time": "2025-01-15T12:00:00Z"
}

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

FAQ

Questions about Get Call.

What does the Get Call action do in Twilio?

Retrieves details about a specific Twilio call by SID: from, to, duration, status, price, and recording info. Used to read back details after a webhook fires.

What inputs does Get Call require?

Required: Call SID. 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 Twilio 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 Call support batch operations?

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

More actions