# Messaging Destinations

# Overview

Messaging destinations are pre-built connectors for destination platforms (email, SMS, push notifications) that activate data and deliver messages to the specified users.

# Twilio - SMS

With Intempt Platform you can send global SMS, MMS, and chat messages from any app, and ensure deliverability using Twilio's APIs.

# How to Set Up a Twilio Destination

Go to Destinations (opens new window) > Create Destination > Select Twilio

Add these credentials from your Twilio account:

  • Phone number - phone number used in your Twilio console
  • Auth token - acts as a password (you can find the Auth Token in the Project Info pane of the Console Dashboard page)
  • API Key SID - accessible from the settings page (API Keys) of the Twilio account.
  • Account SID - available on the general settings page of the Twilio console
  • Messaging Service SID - available on the Programmable Messaging page of the Twilio console.
  • Status Callback URL - Leave this field blank.

img

Next, add a descriptive name and set up attribute mapping for the selected destination.

Attribute mapping ensures that your database is properly synced with the destination schema.

For example, you have an attribute for your user emails named "e-mail" in your database. This attribute in the destination schema is named differently - "user-email." With attribute mapping, you can link these attributes to ensure that your customer data is properly used and sent to the destination.

img

Once the last step is done, the destination is configured and you can use it in a pipeline or a journey builder flow.

img

# Sendgrid - Email

SendGrid provides a cloud-based email delivery service that assists businesses with email delivery. The service manages various types of email including shipping notifications, friend requests, sign-up confirmations, and email newsletters.

# How to Set Up a Sendgrid Destination

Go to Destinations (opens new window) > Create Destination > Select Sendgrid

Enter your API Key from your Sendgrid account (under “Settings” -> “API keys”)

img

Next, add a descriptive name and set up attribute mapping for the selected destination.

Attribute mapping ensures that your database is properly synced with the destination schema.

For example, you have an attribute for your user emails named "e-mail" in your database. This attribute in the destination schema is named differently - "user-email." With attribute mapping, you can link these attributes to ensure that your customer data is properly used and sent to the destination.

img

Once the last step is done, the destination is configured and you can use it in a pipeline or a journey builder flow

img