Overview
Twilio is a cloud communications platform (CPaaS) that enables programmatic sending and receiving of SMS, voice, video, and WhatsApp messages.
The Flows360 integration for Twilio provides a unified interface to manage communication workflows. Sync Message, Channel, and User objects to maintain a consistent state with other applications. Utilize actions to send messages or list channels, and configure triggers to initiate workflows upon receiving new messages, all without direct API implementation.
Capability summary
Authentication
Auth method: Basic Authentication (Account SID & Auth Token)
Required scopes
]
Supported objects
| Object | Read | Write | Notes |
|---|---|---|---|
| Message | Yes | Yes | Represents an individual SMS, MMS, or WhatsApp message. Both inbound and outbound. |
| Channel | Yes | No | Represents a communication channel, such as for Twilio Conversations. |
| User | Yes | No | Represents a user within a Twilio Conversations or similar service. |
Supported actions
| Action | Description |
|---|---|
| send_message | Send an outbound SMS or WhatsApp message to a specified recipient number. |
| list_channels | Retrieves a list of available communication channels. |
| message_received | Triggers a workflow when an inbound message is received on a connected Twilio number. |
Setup steps
Prerequisites
- An active Twilio account with administrative privileges.
- At least one provisioned Twilio phone number.
Connection Steps
- Log in to your Twilio Console.
- On the main dashboard, locate the Account Info panel.
- You will find your Account SID and Auth Token. Click the lock icon to reveal the Auth Token.
- In Flows360, navigate to the connector setup page for Twilio.
- Enter the Account SID into the
Account SIDfield. - Enter the Auth Token into the
Auth Tokenfield. - Click Connect. The system will validate the credentials.
Limitations
- API Rate Limits: Twilio imposes rate limits on API requests, which vary by account type and the specific endpoint being called. High-volume workflows may need to incorporate throttling logic.
- Carrier Filtering: Message deliverability can be affected by carrier-side filtering. Flows360 reports the status provided by Twilio, but debugging delivery issues may require access to the Twilio console logs.
- Regulatory Compliance: Users are responsible for complying with all relevant telecommunications regulations for the regions in which they operate, such as A2P 10DLC registration in the United States.
Troubleshooting
Connection fails with an authentication error.
Verify that the Account SID and Auth Token are copied correctly from the Twilio Console dashboard. Ensure you are using your Live credentials, not your Test credentials, as they are different. Also confirm that the account is active and has a valid payment method on file if it is a paid account.
An action to send a message is successful, but the message is not delivered.
This is typically caused by one of the following:n1. Invalid 'To' Number: Ensure the recipient phone number is in E.164 format (e.g., +14155552671).n2. Carrier Filtering: The destination carrier may have blocked the message. Check the message logs in the Twilio Console for specific error codes (e.g., 30007).n3. Unsubscribed Recipient: The user may have replied with a stop word (e.g., 'STOP').n4. Geo-Permissions: Your account may not have permission to send messages to the destination country. Check your Messaging Geographic Permissions in the Twilio console.