Short answer: Drop the "Twilio → Make Call" 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 Number To | string | Required | The phone number to call in E.164 format |
From Phone Number From | string | Required | Your Twilio phone number in E.164 format |
TwiML URL Url | string | Optional | URL that returns TwiML instructions for the call. Required unless Twiml is provided. |
TwiML Body Twiml | string | Optional | Inline TwiML instructions (e.g. <Response><Say>Hello</Say></Response>). Used instead of URL. |
Timeout (seconds) Timeout | string | Optional | How long to let the phone ring before hanging up (default 60) |
Record Record | options | Optional | Whether to record the call |
{"To": "+15551234567","From": "+15559876543","Url": "https://example.com/twiml","Twiml": "<Response><Say voice=\"alice\">Hello, this is a test call.</Say></Response>","Timeout": "30"}
{"to": "+15551234567","sid": "CA1234567890abcdef","from": "+15559876543","status": "queued","direction": "outbound-api","date_created": "2025-01-15T12:00:00Z"}
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.