Twilio
Twilio·AE_HSc_TwilioConnectorGuide
Overview
The Twilio connector integrates AlertEnterprise's Guardian platform with Twilio for SMS-based messaging — visitor check-in / check-out notifications, OTP delivery, mass alert dispatch, and general SMS communication driven by Guardian workflows.
Topology: Alert Connector Framework (ACF) → Alert Twilio Connector → Twilio's hosted messaging API over HTTPS. No intermediate agent — direct vendor-cloud REST integration.
Architecture
Composed from this connector's actors + edges. Trust zones are color-coded; trust crossings render as thicker lines.
Authentication
1 method supported
Twilio's REST API uses HTTP basic-auth with the Account SID as the username and the Auth Token as the password. Auth Tokens are rotatable from the Twilio console.
Prerequisites
Everything that must be in place for this connector to work, with the owner who's responsible.
Twilio account with verified messaging-capable phone number or Messaging Service
customerCustomer needs an active Twilio account with at least one messaging-capable phone number or a configured Messaging Service. SMS deliverability depends on Twilio's regional carrier registrations (10DLC in US, sender-ID registration elsewhere).
Account SID + Auth Token in AE config
aeTwilio Account SID + Auth Token configured in AE connector config.
Known limitations
Documented constraints to set customer expectations before deployment.
SMS regulatory compliance is customer responsibility
importantUS (10DLC), India (DLT), and similar regional registrations for SMS sending are customer-owned. The connector does not register sender IDs on the customer's behalf.
Data fields
2 fields mapped between AE Guardian and the vendor system.
| AE field | Vendor field | Description | Direction | Required |
|---|---|---|---|---|
| SMS Message | Twilio Message | Outbound SMS messages — body, recipient phone, sender number / messaging service SID. | outbound | yes |
| Delivery Status | Twilio Message Status Callback | Delivery status updates (sent / delivered / failed) returned via Twilio status callbacks. | inbound | no |
- src/connectors/twilio/source.pdf — p7 — Chapter 2, Connector Architecture