From 181bf7e036f7fa211f06448453d1d57d1896f594 Mon Sep 17 00:00:00 2001 From: pwseg Date: Sat, 28 Jun 2025 19:14:56 -0500 Subject: [PATCH 01/14] init --- .../destinations/catalog/actions-twilio-messaging/index.md | 6 ++++++ 1 file changed, 6 insertions(+) create mode 100644 src/connections/destinations/catalog/actions-twilio-messaging/index.md diff --git a/src/connections/destinations/catalog/actions-twilio-messaging/index.md b/src/connections/destinations/catalog/actions-twilio-messaging/index.md new file mode 100644 index 0000000000..77db13e2ec --- /dev/null +++ b/src/connections/destinations/catalog/actions-twilio-messaging/index.md @@ -0,0 +1,6 @@ +--- +title: Twilio Messaging Destination +id: 674f23ece330374dc1ecc874 +hidden: true +beta: true +--- \ No newline at end of file From 94494ed162578fad4c131dc1253e314076bbb369 Mon Sep 17 00:00:00 2001 From: pwseg Date: Sun, 29 Jun 2025 19:29:06 -0500 Subject: [PATCH 02/14] overview section --- .../catalog/actions-twilio-messaging/index.md | 20 ++++++++++++++++++- 1 file changed, 19 insertions(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/actions-twilio-messaging/index.md b/src/connections/destinations/catalog/actions-twilio-messaging/index.md index 77db13e2ec..09589b5490 100644 --- a/src/connections/destinations/catalog/actions-twilio-messaging/index.md +++ b/src/connections/destinations/catalog/actions-twilio-messaging/index.md @@ -3,4 +3,22 @@ title: Twilio Messaging Destination id: 674f23ece330374dc1ecc874 hidden: true beta: true ---- \ No newline at end of file +--- + +Twilio Messaging gives businesses a way to reach customers on SMS, MMS, and WhatsApp for transactional notifications and personalized campaigns. + +The Twilio Messaging destination connects Segment to Twilio, so teams can send messages automatically based on real-time events, audience segments, or journeys without managing complex integrations. + +With the Twilio Messaging destination, you can: + +- Confirm orders or appointments +- Send shipping updates or reminders +- Deliver personalized marketing messages +- Support onboarding and reactivation campaigns + +This destination supports two ways to send messages: + +- **Content templates**: Messages pre-built and managed in Twilio. +- **Inline messages**: Messages created directly in Segment, with dynamic fields and variables. + +Twilio Messaging integrates tightly with Segment's data and audience tools, so you can deliver timely, personalized messages without building custom integrations. From c59fcfd33db16693e6bd098dc66884881ee06ebf Mon Sep 17 00:00:00 2001 From: pwseg Date: Sun, 29 Jun 2025 19:31:38 -0500 Subject: [PATCH 03/14] getting started --- .../catalog/actions-twilio-messaging/index.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/connections/destinations/catalog/actions-twilio-messaging/index.md b/src/connections/destinations/catalog/actions-twilio-messaging/index.md index 09589b5490..42c03a4420 100644 --- a/src/connections/destinations/catalog/actions-twilio-messaging/index.md +++ b/src/connections/destinations/catalog/actions-twilio-messaging/index.md @@ -22,3 +22,15 @@ This destination supports two ways to send messages: - **Inline messages**: Messages created directly in Segment, with dynamic fields and variables. Twilio Messaging integrates tightly with Segment's data and audience tools, so you can deliver timely, personalized messages without building custom integrations. + +## Getting started + +To start sending messages through Twilio Messaging, you'll set up your Twilio account credentials and connect the destination in Segment. + +At a high level, you will: + +1. Create a Twilio API Key and Secret. +2. Add the Twilio Messaging destination in Segment. +3. Configure message mappings to define what messages to send and when. + +The following sections walk through each step in detail. From 99cffe2933a51cbe03845b3c1a3436b655f4e477 Mon Sep 17 00:00:00 2001 From: pwseg Date: Sun, 29 Jun 2025 20:14:48 -0500 Subject: [PATCH 04/14] some fine tuning --- .../catalog/actions-twilio-messaging/index.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/src/connections/destinations/catalog/actions-twilio-messaging/index.md b/src/connections/destinations/catalog/actions-twilio-messaging/index.md index 42c03a4420..2136dc23a4 100644 --- a/src/connections/destinations/catalog/actions-twilio-messaging/index.md +++ b/src/connections/destinations/catalog/actions-twilio-messaging/index.md @@ -34,3 +34,19 @@ At a high level, you will: 3. Configure message mappings to define what messages to send and when. The following sections walk through each step in detail. + +## Authentication and setup + +Before adding the Twilio Messaging to Segment, create an API Key and Secret in your Twilio account. + +To create your API Key and Secret: + +1. Sign in to your [Twilio Console](https://console.twilio.com/){:target="_blank"}. +2. From your Account Dashboard, copy and save your **Account SID**. You'll this in Segment later. +3. In the **Account Info** tab, click **Go to API keys**. +4. On the **API keys & tokens** page, click **Create API Key**. +5. Enter a name for your API key, select the **Standard** key type, then click **Create**. +6. On the **Copy secret key** page, copy the **SID** and **Secret** values. Store them securely. You'll enter both in Segment later. +7. Click **Done** to finish creating the API Key. + +You now have your **Account SID**, **API Key SID**, and **API Key Secret**, which are required to connect Twilio Messaging in Segment. From bbdd88ca652e09d4a5185e52dbc3ccf940360baa Mon Sep 17 00:00:00 2001 From: pwseg Date: Sun, 29 Jun 2025 20:15:20 -0500 Subject: [PATCH 05/14] add private beta callout --- .../destinations/catalog/actions-twilio-messaging/index.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/connections/destinations/catalog/actions-twilio-messaging/index.md b/src/connections/destinations/catalog/actions-twilio-messaging/index.md index 2136dc23a4..90d193cfe6 100644 --- a/src/connections/destinations/catalog/actions-twilio-messaging/index.md +++ b/src/connections/destinations/catalog/actions-twilio-messaging/index.md @@ -23,6 +23,10 @@ This destination supports two ways to send messages: Twilio Messaging integrates tightly with Segment's data and audience tools, so you can deliver timely, personalized messages without building custom integrations. +> info "Twilio Messaging Destination Private Beta" +> Bidirectional sync is in Private Beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. + + ## Getting started To start sending messages through Twilio Messaging, you'll set up your Twilio account credentials and connect the destination in Segment. From 17c7d3d64f8b5a117fb2c05debdfd2d5954b1c2b Mon Sep 17 00:00:00 2001 From: pwseg Date: Sun, 29 Jun 2025 21:21:48 -0500 Subject: [PATCH 06/14] more fine tuning --- .../catalog/actions-twilio-messaging/index.md | 22 +++++++++++++++++-- 1 file changed, 20 insertions(+), 2 deletions(-) diff --git a/src/connections/destinations/catalog/actions-twilio-messaging/index.md b/src/connections/destinations/catalog/actions-twilio-messaging/index.md index 90d193cfe6..7c50ae6575 100644 --- a/src/connections/destinations/catalog/actions-twilio-messaging/index.md +++ b/src/connections/destinations/catalog/actions-twilio-messaging/index.md @@ -26,12 +26,11 @@ Twilio Messaging integrates tightly with Segment's data and audience tools, so y > info "Twilio Messaging Destination Private Beta" > Bidirectional sync is in Private Beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. - ## Getting started To start sending messages through Twilio Messaging, you'll set up your Twilio account credentials and connect the destination in Segment. -At a high level, you will: +You'll set up the Twilio Messaing destination in three stages: 1. Create a Twilio API Key and Secret. 2. Add the Twilio Messaging destination in Segment. @@ -54,3 +53,22 @@ To create your API Key and Secret: 7. Click **Done** to finish creating the API Key. You now have your **Account SID**, **API Key SID**, and **API Key Secret**, which are required to connect Twilio Messaging in Segment. + +## Add the Twilio Messaging destination + +After setting up your Twilio credentials, add the Twilio Messaging destination to your Segment workspace. + +To add the destination: + +1. From the Twilio Messaging destination page, click **Add destination**. +2. On the Setup screen, give the destination a name and select **Fill in settings manually.** +3. On your new destination page, click the **Settings** tab. +4. On the Settings tab, enter your **Twilio Account SID**, **Twilio API Key SID**, and **Twilio API Key Secret**. +6. To finish setting up the destination, click **Save Changes**. + +The destination is now connected and ready to configure message mappings. + + + From 04bba0393119c2f711a8f682ec6bcf038b47ddd1 Mon Sep 17 00:00:00 2001 From: pwseg Date: Sun, 29 Jun 2025 21:23:34 -0500 Subject: [PATCH 07/14] fix typo --- .../destinations/catalog/actions-twilio-messaging/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/connections/destinations/catalog/actions-twilio-messaging/index.md b/src/connections/destinations/catalog/actions-twilio-messaging/index.md index 7c50ae6575..bcfdd6646e 100644 --- a/src/connections/destinations/catalog/actions-twilio-messaging/index.md +++ b/src/connections/destinations/catalog/actions-twilio-messaging/index.md @@ -7,7 +7,7 @@ beta: true Twilio Messaging gives businesses a way to reach customers on SMS, MMS, and WhatsApp for transactional notifications and personalized campaigns. -The Twilio Messaging destination connects Segment to Twilio, so teams can send messages automatically based on real-time events, audience segments, or journeys without managing complex integrations. +The Twilio Messaging destination connects Segment to Twilio, letting you send messages automatically based on real-time events, audience segments, or journeys without managing complex integrations. With the Twilio Messaging destination, you can: @@ -30,7 +30,7 @@ Twilio Messaging integrates tightly with Segment's data and audience tools, so y To start sending messages through Twilio Messaging, you'll set up your Twilio account credentials and connect the destination in Segment. -You'll set up the Twilio Messaing destination in three stages: +You'll set up the Twilio Messaging destination in three stages: 1. Create a Twilio API Key and Secret. 2. Add the Twilio Messaging destination in Segment. From bcd611fa57d4f0a3882d22eb2e9cdd54e19a2489 Mon Sep 17 00:00:00 2001 From: pwseg Date: Sun, 29 Jun 2025 21:25:08 -0500 Subject: [PATCH 08/14] more random stuff --- .../catalog/actions-twilio-messaging/index.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/connections/destinations/catalog/actions-twilio-messaging/index.md b/src/connections/destinations/catalog/actions-twilio-messaging/index.md index bcfdd6646e..763b25717a 100644 --- a/src/connections/destinations/catalog/actions-twilio-messaging/index.md +++ b/src/connections/destinations/catalog/actions-twilio-messaging/index.md @@ -40,19 +40,19 @@ The following sections walk through each step in detail. ## Authentication and setup -Before adding the Twilio Messaging to Segment, create an API Key and Secret in your Twilio account. +Before you add the Twilio Messaging destination to Segment, you'll first need to create an API Key and Secret in your Twilio account. To create your API Key and Secret: 1. Sign in to your [Twilio Console](https://console.twilio.com/){:target="_blank"}. -2. From your Account Dashboard, copy and save your **Account SID**. You'll this in Segment later. +2. From your Account Dashboard, copy and save your **Account SID**. You'll enter it in Segment later. 3. In the **Account Info** tab, click **Go to API keys**. 4. On the **API keys & tokens** page, click **Create API Key**. 5. Enter a name for your API key, select the **Standard** key type, then click **Create**. 6. On the **Copy secret key** page, copy the **SID** and **Secret** values. Store them securely. You'll enter both in Segment later. 7. Click **Done** to finish creating the API Key. -You now have your **Account SID**, **API Key SID**, and **API Key Secret**, which are required to connect Twilio Messaging in Segment. +You now have your Account SID, API Key SID, and API Key Secret, which are required to connect Twilio Messaging in Segment. ## Add the Twilio Messaging destination @@ -61,7 +61,7 @@ After setting up your Twilio credentials, add the Twilio Messaging destination t To add the destination: 1. From the Twilio Messaging destination page, click **Add destination**. -2. On the Setup screen, give the destination a name and select **Fill in settings manually.** +2. On the Setup screen, give the destination a name and select **Fill in settings manually**. 3. On your new destination page, click the **Settings** tab. 4. On the Settings tab, enter your **Twilio Account SID**, **Twilio API Key SID**, and **Twilio API Key Secret**. 6. To finish setting up the destination, click **Save Changes**. From 2bd278c8e704d804db25cb53cca898cfbae829db Mon Sep 17 00:00:00 2001 From: pwseg Date: Sun, 29 Jun 2025 21:57:22 -0500 Subject: [PATCH 09/14] mappings table [netlify-build] --- .../catalog/actions-twilio-messaging/index.md | 46 +++++++++++++++++++ 1 file changed, 46 insertions(+) diff --git a/src/connections/destinations/catalog/actions-twilio-messaging/index.md b/src/connections/destinations/catalog/actions-twilio-messaging/index.md index 763b25717a..e87a58d114 100644 --- a/src/connections/destinations/catalog/actions-twilio-messaging/index.md +++ b/src/connections/destinations/catalog/actions-twilio-messaging/index.md @@ -72,3 +72,49 @@ The destination is now connected and ready to configure message mappings. Users can only access the destination through the specific URL. I'll update these instructions once it's publicly available and searchable in the workspace catalog. --> +## Configuring message mappings + +The Twilio Messaging destination supports one mapping: **Send message**. Use this mapping to define when messages get sent and what content they include. + +To configure the Send message mapping: + +1. From the destination page, go to **Mappings**. +2. Click **New Mapping**. +3. Select the **Send message** action. +4. Choose the trigger event and map the required fields. For example, specify the recipient's phone number and message content. +5. Configure any additional fields, such as variables or media URLs. +6. Click **Save** to create the mapping. +7. Enable the mapping to start sending messages. + +## Configuring message mappings + +The Twilio Messaging destination supports one mapping action: **Send message**. Use this mapping to define when messages are sent and what content they include. + +### Set up the Send message mapping + +To configure the mapping: + +1. In the Twilio Messaging destination settings, go to **Mappings**. +2. Click **New Mapping**. +3. Select the **Send message** action. +4. Choose the trigger event for when the message should send. +5. Fill out the required fields. +6. Click **Save** to create the mapping. +7. Enable the mapping to start sending messages. + +### Mapping fields reference + +| Field | Description | Notes | +| --------------------- | ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| Channel | The channel to send the message on. | Options: SMS, MMS, WhatsApp. | +| Sender Type | The sender to use for the message. | Options: Phone number or Messaging Service. Phone numbers must be approved in Twilio. | +| Content Template Type | The type of content template to use. | Options include Inline or pre-built templates in Twilio. Only compatible templates show based on your selected Channel and Content Template Type. | +| To Phone Number | The recipient's phone number. | Must be in [E.164 format](https://www.twilio.com/docs/glossary/what-e164){:target="_blank"}. | +| From Phone Number | The sending phone number. | Must be approved in Twilio and support the selected Channel. | +| Messaging Service SID | The messaging service SID to use. | Required if Sender Type is Messaging Service. | +| Content Template SID | The SID of the content template to use. | Required unless Content Template Type is Inline. | +| Content Variables | Variables used in the content template. | Variables must be pre-defined in Twilio. | +| Inline Template | The message body for inline messages. | Supports variables (for example, `Hello {{first_name}}`). Shown only if Content Template Type is Inline. | +| Inline Media URLs | URLs of any media you want to include with inline messages. | URLs must be publicly accessible. Shown only if Content Template Type is Inline. | +| Validity Period | How long Twilio keeps trying to deliver the message (in seconds). | Optional. Default is 14400 seconds (4 hours). Range: 1–14400. | +| Send At | Time to send the message. | Optional. Must be in [ISO 8601 format]{:target="_blank"}. Messages won't send before this time and will expire after it passes. | From e88f2031e4eeb837db02a21a51c4f0f94d44e41b Mon Sep 17 00:00:00 2001 From: pwseg Date: Sun, 29 Jun 2025 22:12:59 -0500 Subject: [PATCH 10/14] add message type info --- .../catalog/actions-twilio-messaging/index.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/src/connections/destinations/catalog/actions-twilio-messaging/index.md b/src/connections/destinations/catalog/actions-twilio-messaging/index.md index e87a58d114..27890bcb08 100644 --- a/src/connections/destinations/catalog/actions-twilio-messaging/index.md +++ b/src/connections/destinations/catalog/actions-twilio-messaging/index.md @@ -118,3 +118,13 @@ To configure the mapping: | Inline Media URLs | URLs of any media you want to include with inline messages. | URLs must be publicly accessible. Shown only if Content Template Type is Inline. | | Validity Period | How long Twilio keeps trying to deliver the message (in seconds). | Optional. Default is 14400 seconds (4 hours). Range: 1–14400. | | Send At | Time to send the message. | Optional. Must be in [ISO 8601 format]{:target="_blank"}. Messages won't send before this time and will expire after it passes. | + +## Message composition options + +The Twilio Messaging destination gives you two ways to create and send messages. + +**Content templates** are templates you’ve already set up in Twilio. They can include text, media, buttons, and other elements, depending on what you’ve built. When you choose a Channel and Content Template Type in Segment, you’ll only see templates that are compatible with those choices. If you’re sending messages to WhatsApp, you’ll need to use Content Templates, since WhatsApp requires pre-approved templates. For most use cases, templates are the way to go because they support richer formatting and keep you compliant. + +**Inline messages** let you write your message directly in Segment mappings. You can include dynamic variables like `Hello {{first_name}}` to personalize messages. Inline messages also support adding media URLs if you’re sending MMS or WhatsApp messages. They’re useful for quick tests or simple notifications, but they don’t support all the advanced features that Content Templates do. + +Choose the option that fits what you’re trying to send. For most customer-facing messages, Content Templates will give you the most reliable and feature-rich experience. From 472a8b2e4233d227bd674424a02c07ed98e56d79 Mon Sep 17 00:00:00 2001 From: pwseg Date: Sun, 29 Jun 2025 23:41:23 -0500 Subject: [PATCH 11/14] message setup options --- .../catalog/actions-twilio-messaging/index.md | 69 +++++++++++++++---- 1 file changed, 55 insertions(+), 14 deletions(-) diff --git a/src/connections/destinations/catalog/actions-twilio-messaging/index.md b/src/connections/destinations/catalog/actions-twilio-messaging/index.md index 27890bcb08..2477fd0136 100644 --- a/src/connections/destinations/catalog/actions-twilio-messaging/index.md +++ b/src/connections/destinations/catalog/actions-twilio-messaging/index.md @@ -104,20 +104,21 @@ To configure the mapping: ### Mapping fields reference -| Field | Description | Notes | -| --------------------- | ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | -| Channel | The channel to send the message on. | Options: SMS, MMS, WhatsApp. | -| Sender Type | The sender to use for the message. | Options: Phone number or Messaging Service. Phone numbers must be approved in Twilio. | -| Content Template Type | The type of content template to use. | Options include Inline or pre-built templates in Twilio. Only compatible templates show based on your selected Channel and Content Template Type. | -| To Phone Number | The recipient's phone number. | Must be in [E.164 format](https://www.twilio.com/docs/glossary/what-e164){:target="_blank"}. | -| From Phone Number | The sending phone number. | Must be approved in Twilio and support the selected Channel. | -| Messaging Service SID | The messaging service SID to use. | Required if Sender Type is Messaging Service. | -| Content Template SID | The SID of the content template to use. | Required unless Content Template Type is Inline. | -| Content Variables | Variables used in the content template. | Variables must be pre-defined in Twilio. | -| Inline Template | The message body for inline messages. | Supports variables (for example, `Hello {{first_name}}`). Shown only if Content Template Type is Inline. | -| Inline Media URLs | URLs of any media you want to include with inline messages. | URLs must be publicly accessible. Shown only if Content Template Type is Inline. | -| Validity Period | How long Twilio keeps trying to deliver the message (in seconds). | Optional. Default is 14400 seconds (4 hours). Range: 1–14400. | -| Send At | Time to send the message. | Optional. Must be in [ISO 8601 format]{:target="_blank"}. Messages won't send before this time and will expire after it passes. | +| Field | Description | Notes | +| ------------------------- | --------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| **Channel** | Choose which channel to send the message on. | Options: SMS, MMS, and WhatsApp. | +| **Sender Type** | Pick how you want to send the message. | Options: Phone number or Messaging Service. Phone numbers must be approved in Twilio. | +| **Content Template Type** | Select the type of content template. | Options include Inline or templates you’ve built in Twilio. Segment only shows templates that match your selected Channel and Template Type. | +| **To Phone Number** | Enter the recipient’s phone number. | Must be in [E.164 format](https://www.twilio.com/docs/glossary/what-e164){:target="_blank"}. | +| **From Phone Number** | Choose the phone number to send from. | Must be approved in Twilio and support the channel you’re using. | +| **Messaging Service SID** | Enter the messaging service SID if you’re using a messaging service. | Required if Sender Type is Messaging Service. | +| **Content Template SID** | Choose which content template to use. | Required unless you’re using Inline. | +| **Content Variables** | Map variables used in your content template. | These variables need to be defined in Twilio first. | +| **Inline Template** | Write your message body if you’re using Inline. | Supports variables (for example, `Hello {{first_name}}`). Shown only if Content Template Type is Inline. | +| **Inline Media URLs** | Add any media URLs for your inline message. | URLs must be publicly accessible. Shown only if Content Template Type is Inline. | +| **Validity Period** | Set how long Twilio should keep trying to deliver the message (in seconds). | Optional. Default is 14400 seconds (4 hours). Can be between 1 and 14400. | +| **Send At** | Schedule when Twilio should send the message. | Optional. Must be in [ISO 8601 format](https://en.wikipedia.org/wiki/ISO_8601){:target="_blank"}. Messages won’t send before this time and will expire after it passes. | + ## Message composition options @@ -128,3 +129,43 @@ The Twilio Messaging destination gives you two ways to create and send messages. **Inline messages** let you write your message directly in Segment mappings. You can include dynamic variables like `Hello {{first_name}}` to personalize messages. Inline messages also support adding media URLs if you’re sending MMS or WhatsApp messages. They’re useful for quick tests or simple notifications, but they don’t support all the advanced features that Content Templates do. Choose the option that fits what you’re trying to send. For most customer-facing messages, Content Templates will give you the most reliable and feature-rich experience. + +## Message setup options + +When you’re configuring your message mapping, there are a few key settings to choose from. + +### Content template types + +The template types you can use depend on the channel you select. Segment only shows templates that are compatible with your chosen channel. + +| Template type | Available channels | Description | +| ------------- | ------------------ | ------------------------------------------------------ | +| Text | SMS, WhatsApp | Standard text-only templates. | +| Media | MMS, WhatsApp | Templates that include images, videos, or other media. | +| Quick reply | WhatsApp | Messages with quick reply buttons for users to tap. | + +If you’re sending messages on WhatsApp, all messages must use approved Content Templates. + +### Sender types + +For the **Sender Type** field, you can choose either a phone number or a messaging service. + +If you select **phone number**, Twilio sends the message from a specific number you own. The number must be approved in your Twilio account and support the channel you’re using. + +If you select **messaging service**, Twilio uses a Messaging Service SID to send the message. Messaging Services group multiple senders under one ID, and Twilio decides which sender to use based on your setup. This option is helpful if you’re sending high volumes or managing multiple numbers. + +### Using variables + +Variables let you personalize messages with details from your event data or user traits. + +If you’re using a **Content Template**: +- Variables must be defined in Twilio when you create the template. +- In Segment, map each variable to the event property it should pull from. For example, if your template says `Hello {{first_name}}`, map `first_name` to the user’s first name property. + +If you’re writing an **inline message**: +- Add variables directly in your message body using handlebars, like `Hello {{first_name}}`. +- Define each variable in your mapping so Segment knows what value to insert. + +You can also use variables in Inline Media URLs to dynamically include different media based on event data. + +Make sure all variables you reference in your message are included in your mapping configuration. From 98aea2b4d7ed41deadfd1e54a8a12a85bcd35ad5 Mon Sep 17 00:00:00 2001 From: pwseg Date: Sun, 29 Jun 2025 23:46:47 -0500 Subject: [PATCH 12/14] more cleanup [netlify-build] --- .../catalog/actions-twilio-messaging/index.md | 47 ++++++++++++------- 1 file changed, 29 insertions(+), 18 deletions(-) diff --git a/src/connections/destinations/catalog/actions-twilio-messaging/index.md b/src/connections/destinations/catalog/actions-twilio-messaging/index.md index 2477fd0136..1cb9a5b408 100644 --- a/src/connections/destinations/catalog/actions-twilio-messaging/index.md +++ b/src/connections/destinations/catalog/actions-twilio-messaging/index.md @@ -21,10 +21,10 @@ This destination supports two ways to send messages: - **Content templates**: Messages pre-built and managed in Twilio. - **Inline messages**: Messages created directly in Segment, with dynamic fields and variables. -Twilio Messaging integrates tightly with Segment's data and audience tools, so you can deliver timely, personalized messages without building custom integrations. +Twilio Messaging works with Segment's data and audience tools to send timely, personalized messages without extra integration work. > info "Twilio Messaging Destination Private Beta" -> Bidirectional sync is in Private Beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. +> The Twilio Messaging Destination is in Private Beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. ## Getting started @@ -74,21 +74,7 @@ it's publicly available and searchable in the workspace catalog. --> ## Configuring message mappings -The Twilio Messaging destination supports one mapping: **Send message**. Use this mapping to define when messages get sent and what content they include. - -To configure the Send message mapping: - -1. From the destination page, go to **Mappings**. -2. Click **New Mapping**. -3. Select the **Send message** action. -4. Choose the trigger event and map the required fields. For example, specify the recipient's phone number and message content. -5. Configure any additional fields, such as variables or media URLs. -6. Click **Save** to create the mapping. -7. Enable the mapping to start sending messages. - -## Configuring message mappings - -The Twilio Messaging destination supports one mapping action: **Send message**. Use this mapping to define when messages are sent and what content they include. +The Twilio Messaging destination supports one mapping action: **Send message**. Use this mapping to define when messages get sent and what content they include. ### Set up the Send message mapping @@ -163,9 +149,34 @@ If you’re using a **Content Template**: - In Segment, map each variable to the event property it should pull from. For example, if your template says `Hello {{first_name}}`, map `first_name` to the user’s first name property. If you’re writing an **inline message**: -- Add variables directly in your message body using handlebars, like `Hello {{first_name}}`. +- Add variables directly in your message body using Handlebars, like `Hello {{first_name}}`. - Define each variable in your mapping so Segment knows what value to insert. You can also use variables in Inline Media URLs to dynamically include different media based on event data. Make sure all variables you reference in your message are included in your mapping configuration. + +## Additional features + +Twilio Messaging also supports a few optional settings you can use in your mappings. + +### Validity period + +The **Validity Period** controls how long Twilio keeps trying to deliver your message. It’s set in seconds, with a minimum of 1 and a maximum of 14400 (4 hours). If the message isn’t delivered within this time, it won’t be sent. The default is 14400 seconds. + +### Send At + +The **Send At** field lets you schedule a message to be sent at a specific time. Enter the time in ISO 8601 format. Messages won’t send before this time, and if the scheduled time passes, new messages triggered after that time won’t send either. Also, keep in mind that Twilio processes scheduled messages as they come in, so delivery might not be exactly at the time you set. + +Use these settings if you need to control delivery timing for things like appointment reminders or time-sensitive notifications. + +## Important considerations + +Here are a few things to keep in mind when using the Twilio Messaging destination: + +- **Content Templates must be created in Twilio**. You can’t create or edit Content Templates directly in Segment. Make sure your templates are built and approved in your Twilio account before selecting them in your mappings. +- **WhatsApp messages require approved templates**. WhatsApp doesn’t allow freeform messages unless it’s part of an active conversation window. For outbound messages, you’ll need to use approved Content Templates. +- **Phone numbers must be approved**. Any phone number you use to send messages must be approved in your Twilio account and support the channel you’re sending on. +- **Message logs and errors**. If a message fails to send, you can view details in your Twilio Console message logs. Common issues include invalid phone number formats or missing required template fields. + +Understanding these details will help you set up your messaging flows smoothly and avoid unexpected errors. From 778d71adec5ebcb2ef0cd34aadee8a2f8b743153 Mon Sep 17 00:00:00 2001 From: pwseg Date: Tue, 1 Jul 2025 12:19:55 -0500 Subject: [PATCH 13/14] fix liquid issue [netlify-build] --- .../destinations/catalog/actions-twilio-messaging/index.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/actions-twilio-messaging/index.md b/src/connections/destinations/catalog/actions-twilio-messaging/index.md index 1cb9a5b408..a85f71da84 100644 --- a/src/connections/destinations/catalog/actions-twilio-messaging/index.md +++ b/src/connections/destinations/catalog/actions-twilio-messaging/index.md @@ -100,7 +100,7 @@ To configure the mapping: | **Messaging Service SID** | Enter the messaging service SID if you’re using a messaging service. | Required if Sender Type is Messaging Service. | | **Content Template SID** | Choose which content template to use. | Required unless you’re using Inline. | | **Content Variables** | Map variables used in your content template. | These variables need to be defined in Twilio first. | -| **Inline Template** | Write your message body if you’re using Inline. | Supports variables (for example, `Hello {{first_name}}`). Shown only if Content Template Type is Inline. | +| **Inline Template** | Write your message body if you’re using Inline. | Supports variables. Shown only if Content Template Type is Inline. | | **Inline Media URLs** | Add any media URLs for your inline message. | URLs must be publicly accessible. Shown only if Content Template Type is Inline. | | **Validity Period** | Set how long Twilio should keep trying to deliver the message (in seconds). | Optional. Default is 14400 seconds (4 hours). Can be between 1 and 14400. | | **Send At** | Schedule when Twilio should send the message. | Optional. Must be in [ISO 8601 format](https://en.wikipedia.org/wiki/ISO_8601){:target="_blank"}. Messages won’t send before this time and will expire after it passes. | @@ -114,6 +114,8 @@ The Twilio Messaging destination gives you two ways to create and send messages. **Inline messages** let you write your message directly in Segment mappings. You can include dynamic variables like `Hello {{first_name}}` to personalize messages. Inline messages also support adding media URLs if you’re sending MMS or WhatsApp messages. They’re useful for quick tests or simple notifications, but they don’t support all the advanced features that Content Templates do. +In Segment, map each variable to the event property it should pull from. For example, if your template says {% raw %}`Hello {{first_name}}`{% endraw %}, map `first_name` to the user’s first name property. + Choose the option that fits what you’re trying to send. For most customer-facing messages, Content Templates will give you the most reliable and feature-rich experience. ## Message setup options From d177ac374f91329feec9e41e236963f5739c37e9 Mon Sep 17 00:00:00 2001 From: pwseg Date: Tue, 1 Jul 2025 12:40:55 -0500 Subject: [PATCH 14/14] final cleanup [netlify-build] --- .../catalog/actions-twilio-messaging/index.md | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/src/connections/destinations/catalog/actions-twilio-messaging/index.md b/src/connections/destinations/catalog/actions-twilio-messaging/index.md index a85f71da84..53f111b07a 100644 --- a/src/connections/destinations/catalog/actions-twilio-messaging/index.md +++ b/src/connections/destinations/catalog/actions-twilio-messaging/index.md @@ -2,10 +2,11 @@ title: Twilio Messaging Destination id: 674f23ece330374dc1ecc874 hidden: true +hide-dossier: true beta: true --- -Twilio Messaging gives businesses a way to reach customers on SMS, MMS, and WhatsApp for transactional notifications and personalized campaigns. +[Twilio Messaging](https://www.twilio.com/en-us/messaging/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} gives businesses a way to reach customers on SMS, MMS, and WhatsApp for transactional notifications and personalized campaigns. The Twilio Messaging destination connects Segment to Twilio, letting you send messages automatically based on real-time events, audience segments, or journeys without managing complex integrations. @@ -32,9 +33,9 @@ To start sending messages through Twilio Messaging, you'll set up your Twilio ac You'll set up the Twilio Messaging destination in three stages: -1. Create a Twilio API Key and Secret. -2. Add the Twilio Messaging destination in Segment. -3. Configure message mappings to define what messages to send and when. +1. [Create a Twilio API Key and Secret](#authentication-and-setup). +2. [Add the Twilio Messaging destination in Segment](#add-the-twilio-messaging-destination). +3. [Configure message mappings](#configuring-message-mappings) to define what messages to send and when. The following sections walk through each step in detail. @@ -110,9 +111,9 @@ To configure the mapping: The Twilio Messaging destination gives you two ways to create and send messages. -**Content templates** are templates you’ve already set up in Twilio. They can include text, media, buttons, and other elements, depending on what you’ve built. When you choose a Channel and Content Template Type in Segment, you’ll only see templates that are compatible with those choices. If you’re sending messages to WhatsApp, you’ll need to use Content Templates, since WhatsApp requires pre-approved templates. For most use cases, templates are the way to go because they support richer formatting and keep you compliant. +**Content templates** are [templates you’ve already set up in Twilio](https://www.twilio.com/docs/content/create-templates-with-the-content-template-builder){:target="_blank”}. They can include text, media, buttons, and other elements, depending on what you’ve built. When you choose a Channel and Content Template Type in Segment, you’ll only see templates that are compatible with those choices. If you’re sending messages to WhatsApp, you’ll need to use Content Templates, since WhatsApp requires pre-approved templates. For most use cases, templates are the way to go because they support richer formatting and keep you compliant. -**Inline messages** let you write your message directly in Segment mappings. You can include dynamic variables like `Hello {{first_name}}` to personalize messages. Inline messages also support adding media URLs if you’re sending MMS or WhatsApp messages. They’re useful for quick tests or simple notifications, but they don’t support all the advanced features that Content Templates do. +**Inline messages** let you write your message directly in Segment mappings. You can include [dynamic variables](#using-variables) to personalize messages. Inline messages also support adding media URLs if you’re sending MMS or WhatsApp messages. They’re useful for quick tests or simple notifications, but they don’t support all the advanced features that Content Templates do. In Segment, map each variable to the event property it should pull from. For example, if your template says {% raw %}`Hello {{first_name}}`{% endraw %}, map `first_name` to the user’s first name property. @@ -148,10 +149,10 @@ Variables let you personalize messages with details from your event data or user If you’re using a **Content Template**: - Variables must be defined in Twilio when you create the template. -- In Segment, map each variable to the event property it should pull from. For example, if your template says `Hello {{first_name}}`, map `first_name` to the user’s first name property. +- In Segment, map each variable to the event property it should pull from. For example, if your template says {% raw %}`Hello {{first_name}}`{% endraw %}, map `first_name` to the user’s first name property. If you’re writing an **inline message**: -- Add variables directly in your message body using Handlebars, like `Hello {{first_name}}`. +- Add variables directly in your message body using Handlebars. - Define each variable in your mapping so Segment knows what value to insert. You can also use variables in Inline Media URLs to dynamically include different media based on event data. @@ -181,4 +182,4 @@ Here are a few things to keep in mind when using the Twilio Messaging destinatio - **Phone numbers must be approved**. Any phone number you use to send messages must be approved in your Twilio account and support the channel you’re sending on. - **Message logs and errors**. If a message fails to send, you can view details in your Twilio Console message logs. Common issues include invalid phone number formats or missing required template fields. -Understanding these details will help you set up your messaging flows smoothly and avoid unexpected errors. +Understanding these details will help you set up your messaging flows smoothly and avoid unexpected errors. \ No newline at end of file