Connect Twilio SMS
Send SMS from AXO triggers.
All connectors · Checked against AXO’s implementation in October 2026.
Prepare access
Use an owner or admin account in AXO and confirm the selected site. Have permission to authorize the external account or create its server credentials. Keep secrets in the connector’s protected configuration.
| Setting | Value to prepare |
|---|---|
account_sid | Twilio Account SID. |
auth_token | Auth token for that account. |
from_number | An SMS-capable sender, including its country code. |
Connect
Open Integrations, find Twilio SMS, and open its setup. Enter the fields above and save with Connect (or Save changes for an existing connection).
- Select this integration in a trigger that requires a phone identifier. The rendered payload is the message body.
Verify the result
The connection check reads the account; it does not send SMS. A trigger test sends an actual message and may incur provider charges.
Record the AXO integration or trigger result and the receiving system’s result. A saved configuration, credential check, and completed delivery establish different things. Use a controlled destination for a test that writes data or sends a message.
Fix a failed connection
Check the account’s sender permissions, destination format, trial-account restrictions, and delivery status in Twilio.
For a saved catalog connector, open Health to read the latest error, then repair the settings through the setup method on this page. Pause delivery while correcting an unintended destination. Reconnect OAuth when its grant is revoked; for key-based connections, save the replacement key, verify it, then revoke the old key at the provider.
Next: create an event-triggered action, or implement a webhook receiver.