Short answer: Drop the "Twilio → List Calls" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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" |
{"To": "+15551234567","From": "+15559876543","Status": "{{trigger.Status}}","PageSize": "50"}
{"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.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.