Twilio
Send the right update through Twilio at the right moment, with a person approving what reaches customers.
25 ways to read, 2 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Twilio, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Add conversation messageApproval by rule
- Send messageApproval by rule
- List debugger alertsRead
Example flow
- HubSpot · Read contactsDone
- Twilio · Send messageNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Twilio.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Twilio
- Twilio's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.
For developers
Technical detail
Send SMS and WhatsApp messages; read messages, calls, usage, alerts, Conversations, Verify, Studio and TaskRouter; and look up phone numbers.
Twilio API docs- Source actions
- 25
- Destination actions
- 2
- Data types
- 16
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Alerts2
- Get alertSource
One debugger alert.
- List debugger alertsSourceIncremental
Monitor API alerts (webhook failures, delivery errors), filtered by log level and date.
Calls2
- Get callSource
One call with status, duration and price.
- List callsSourceIncremental
Call log, newest first, optionally filtered by number, status or start date.
Conversation messages2
- Add conversation messageDestinationNot retried automaticallyApproval before production
Posts one message to one conversation; Twilio delivers it to the conversation's participants.
- List conversation messagesSource
Messages in a conversation, oldest first unless the order is descending.
Conversation participants1
- List conversation participantsSource
Participants in a conversation with their identity or channel binding.
Conversations2
- Get conversationSource
One conversation by SID or unique name.
- List conversationsSourceIncremental
Conversations, optionally filtered by state and creation date range.
Messages4
- Get messageSource
Current status, segments, price and error details for one message.
- List MessagesSource
List operation for Messages.
- Search messagesSourceIncremental
Message log filtered by sender, recipient or sent date, newest first. Use the sent-on-or-after date for incremental sync.
- Send messageDestinationNot retried automaticallyApproval before production
Sends an SMS, MMS or WhatsApp message from a Messaging Service or sender, with text, media or an approved content template.
Messaging services2
- Get Messaging ServiceSource
One Messaging Service.
- List Messaging ServicesSource
Messaging Services with use case, webhook and A2P registration settings.
Phone numbers2
- Get phone numberSource
One phone number on the account with capabilities and webhook configuration.
- List phone numbersSource
Phone numbers on the account with capabilities and webhook configuration.
Recordings1
- List recordingsSourceIncremental
Recording metadata, optionally for one call or created on or after a date.
Studio executions1
- List Studio executionsSourceIncremental
Executions of a flow, optionally filtered by creation date range.
Studio flows2
- Get Studio flowSource
One Studio flow (definition is not returned).
- List Studio flowsSource
Studio flows with status and revision.
Taskrouter tasks1
- List TaskRouter tasksSource
Tasks in a workspace, filtered by assignment status, queue or workflow.
Taskrouter workers1
- List TaskRouter workersSource
Workers in a workspace with current activity and availability.
Taskrouter workspaces1
- List TaskRouter workspacesSource
TaskRouter workspaces with default activities and queue ordering.
Usage records1
- List usage recordsSource
Usage and cost by category (SMS, calls, Lookup, Verify and others) for a period, optionally split by day, month or year.
Verify services2
- Get Verify serviceSource
One Verify service.
- List Verify servicesSource
Verify services and their code and channel settings. Read only.
Access and limits
- Authentication
- API key SID and secret with account SID
- Plans and access
- Any Twilio account; trial accounts can only message verified numbers. Senders must be registered for the destination (A2P 10DLC, toll-free verification, WhatsApp sender approval).
- Test environment
- Trial accounts and the WhatsApp Sandbox can be used; test credentials do not support listing resources.
- Rate limits
- Account-level concurrency limit; HTTP 429 with error 20429. Message queues send at sender throughput (MPS).
- Pagination
- PageSize up to 1000 with next_page_uri page tokens.
- Provider events
- StatusCallback for message and call status; incoming message webhooks per number. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- Sending SMS or WhatsApp messages must be explicitly enabled on the connection and runs only in an approved flow. Twilio has no idempotency key, so a send with an uncertain outcome is never repeated automatically; check the Twilio message log before retrying.
- Sending is high risk and billable: Twilio has no idempotency key for message creation, so an uncertain send is never repeated automatically.
- A queued or sent status is not delivery; read the message later for delivered, undelivered or failed.
- Product APIs are on their own hosts (messaging, monitor, conversations, verify, studio, taskrouter .twilio.com); the same API key authenticates all of them.
- Verify is read only: Nexra never starts or checks verifications.
- Lookup is deliberately excluded: Twilio requires the phone number in the URL path, and Nexra never puts personal data in URLs.
- No deletes, bulk or broadcast sends (Notify, Messaging Service bulk), conversation updates, Studio executions or TaskRouter writes.
- Message search filters by sent date at day precision; Twilio removes message records after 400 days.
- Recording media and message media files are not downloaded; only metadata is read.
Developer reference
- Create the Twilio credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Twilio, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/twilio and the Connections API.