CommunicationReal-timeUpdated May 2026

Twilio

SMS and voice as triggers and actions

Twilio is programmable comms, the layer that turns "we need to text the customer" or "we need to handle an inbound call" from a multi-week vendor evaluation into a single action node. Two triggers cover the inbound side: SMS Received fires when someone texts a Twilio number you own, and Call Received fires when someone calls. Both payloads include the sender's number, message body or call SID, and the receiving Twilio number, so a workflow can route inbound messages by destination. Seven actions cover the outbound and lookup side: Send SMS, Make Call (with TwiML or recorded voice), Lookup Phone Number (carrier, type, country, caller name where available), Get Message, Get Call, List Messages, List Calls. Authorize with your Twilio account SID and Auth Token. The integration handles message segmentation for long SMS automatically, and lookup costs hit your Twilio dashboard directly. Common pattern: a Stripe Charge Failed event triggers an SMS to the cardholder via Send SMS, with a Klaviyo email fallback if the lookup says the number is a landline.

Connect Twilio See 2 triggers

2triggers

7actions

≈ 2 minto set up

Freetier · no card

Triggers

Workflows start when Twilio does.

2 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.

Real-time · webhook-driven

Trigger live

When call received

Fires when a phone call is received on your Twilio number. Use it to log calls into your CRM, route via IVR, or kick off a callback workflow.

See what it returns →

Trigger live

When sms received

Fires when an SMS message is received on your Twilio number. The starting hook for SMS bots, opt-in/opt-out handling, and 2-way conversation flows.

See what it returns →

Actions

Do anything Twilio can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs
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.	1 fields	View →
Get 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.	1 fields	View →
List Calls	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.	4 fields	View →
List 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.	4 fields	View →
Lookup 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.	2 fields	View →
Make 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.	6 fields	View →
Send 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.	4 fields	View →

Recipes

Pre-built Twilio workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Twilio → Slack alerts

AI-triage every Twilio event, ping the right channel only when it matters.

Twilio → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Twilio → Notion database

Turn Twilio into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Twilio once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Twilio field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Twilio integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Twilio to Tiny Command?

Open the Tiny Command workflow builder, drop in a Twilio node, and click Connect. Authorize Twilio once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Twilio triggers does Tiny Command support?

Tiny Command supports 2 real-time Twilio triggers, including "Call Received", "SMS Received". Each trigger fires within seconds of the event happening in Twilio.

What Twilio actions can I run from a workflow?

7 Twilio actions are available out of the box, covering communication operations like "Get Call". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Twilio integration real-time?

Yes. Call Received and every other Twilio trigger uses webhooks or push subscriptions, so workflows fire within seconds of the event in Twilio rather than on a polling schedule.

Do I need to write code to use Twilio with Tiny Command?

No. Every Twilio trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Twilio API endpoint directly.

How much does the Twilio integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Twilio integration itself has no per-app surcharge.