- Integrations
- /
- Twilio
- /
- Actions
- /
- List Calls
ActionTwilioUpdated May 2026
How do I list Twilio call records?
Short answer: Drop the "Twilio → List Calls" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 |
|---|---|---|---|
To Phone To | string | Optional | To Phone. e.g. "+15551234567" |
From Phone From | string | Optional | From Phone. e.g. "+15559876543" |
Status Status | options | Optional | Options: All, Queued, Ringing, In Progress, Completed, Failed, No Answer, Busy |
Page Size PageSize | string | Optional | Page Size. e.g. "50" |
Sample request
{"To": "+15551234567","From": "+15559876543","Status": "{{trigger.Status}}","PageSize": "50"}
Returns
{"calls": [{"to": "+15551234567","sid": "CA123","from": "+15559876543","status": "completed","duration": "42"}],"page_size": 50}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for List Calls.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about List Calls.
What does the List Calls action do in Twilio?
Lists call records from your Twilio account with filters for to, from, status, and date range. Used for usage reports, billing reconciliation, or quality monitoring.
What inputs does List Calls require?
List Calls has no required inputs. Sensible defaults are applied if you leave fields blank.
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 List Calls support batch operations?
Yes. Run List Calls 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
Other Twilio actions.
Action
Get Call
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.
ActionGet Message
Retrieves details of a sent Twilio message by SID with status (queued, sent, delivered, undelivered, failed), price, and error code. Used to reconcile sends with carrier-reported state.
ActionList Messages
Retrieves a list of sent and received messages on your Twilio account, with filters for to, from, status, and date sent. Used for audit and reporting.
ActionLookup Phone Number
Looks up information about a phone number via Twilio Lookup: country, carrier, line type (mobile/landline/voip), and validity. Use to filter signups, fraud-score, or pre-validate before sending SMS.
ActionMake Call
Initiates an outbound phone call via Twilio. The call flow is driven by either a TwiML URL or by passing inline TwiML; required to specify either url or twiml.
ActionSend SMS
Sends an SMS (or MMS, by adding MediaUrl) via Twilio to the destination number. US/Canada destinations require 10DLC or short-code registration to avoid carrier filtering.
Send list calls from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.