# Twilio Engage Messaging Destination

## About this integration

Twilio Engage brings Segment, Twilio, SendGrid, and WhatsApp together to help you create and send email, SMS, and WhatsApp campaigns to your customers. As a destination, you can identify profiles in Twilio and send events that trigger messages, helping you maintain timely, personal relationships with your customers.

[Mode How we forward source data to the destination: through Customer.io's servers or directly from our JavaScript client.](/cdp/destinations/getting-started/#connection-mode)

[Web sources Indicates whether or not this integration supports our the JavaScript client.](/cdp/sources/getting-started/#types-of-sources)

[API sources Indicates whether or not this integration supports our server libraries (Go, NodeJS, Python), API, Mobile SDK, and other data sources.](/cdp/sources/getting-started/#types-of-sources)

[Supported calls The API methods this integration supports.](/cdp/sources/source-spec/source-events/)

[Integration name The name of this integration if you want to enable or disable it in the `integrations` object.](/cdp/sources/source-spec/common-fields/#the-integrations-object)

Standard

[track](/api/cdp/#operation/track)

Engage Messaging Twilio

## Getting started[](#getting-started)

1.  Go to **[Data & Integrations > Integrations](https://fly.customer.io/workspaces/last/journeys/integrations/all/directory)** and select the **Twilio Engage Messaging** entry in the *Directory* tab.
    
2.  (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration.
    
3.  Configure your integration.
    
    1.  **Twilio Account SID**: Twilio Account SID
        
    2.  **Twilio Api Key SID**: Twilio API Key SID
        
    3.  **Twilio Api Key Secret**: Twilio API Key Secret
        
    4.  **Profile Api Environment**: Profile API Environment
        
    5.  **Profile Api Access Token**: Profile API Access Token
        
    6.  **Space Id**: Space ID
        
    7.  **Source Id**: Source ID
        
    8.  **Webhook Url**: Webhook URL that will receive all events for the sent message
        
    9.  **Twilio Hostname**: Overrides the default Twilio host name used mainly for testing without having to send real messages.
        
    10.  **Connection Overrides**: Connection overrides are configuration supported by twilio webhook services. Must be passed as fragments on the callback url
        
    11.  **Region**: The region where the message is originating from
        
4.  Click **Enable Destination**.
    

## Actions[](#actions)

When you’re done setting things up, you can go to the *Actions* tab to see how we map incoming data to your integration.

You may need to add actions for this integration

While we often have default triggers for actions, we don't always add those actions as defaults. You may need to add actions to make sure that you're sending all the data that you want to send to your integration. See our [actions](/integrations/data-out/actions/) page for help setting up actions.

Action

Default Trigger

Description

Send SMS

`type = “track”` and  
`event = “Audience Entered”`

Send SMS using Twilio

Send WhatsApp

`type = “track”` and  
`event = “Audience Entered”`

Send WhatsApp using Twilio