You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/actions-twilio-messaging/index.md
+46Lines changed: 46 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -72,3 +72,49 @@ The destination is now connected and ready to configure message mappings.
72
72
Users can only access the destination through the specific URL. I'll update these instructions once
73
73
it's publicly available and searchable in the workspace catalog. -->
74
74
75
+
## Configuring message mappings
76
+
77
+
The Twilio Messaging destination supports one mapping: **Send message**. Use this mapping to define when messages get sent and what content they include.
78
+
79
+
To configure the Send message mapping:
80
+
81
+
1. From the destination page, go to **Mappings**.
82
+
2. Click **New Mapping**.
83
+
3. Select the **Send message** action.
84
+
4. Choose the trigger event and map the required fields. For example, specify the recipient's phone number and message content.
85
+
5. Configure any additional fields, such as variables or media URLs.
86
+
6. Click **Save** to create the mapping.
87
+
7. Enable the mapping to start sending messages.
88
+
89
+
## Configuring message mappings
90
+
91
+
The Twilio Messaging destination supports one mapping action: **Send message**. Use this mapping to define when messages are sent and what content they include.
92
+
93
+
### Set up the Send message mapping
94
+
95
+
To configure the mapping:
96
+
97
+
1. In the Twilio Messaging destination settings, go to **Mappings**.
98
+
2. Click **New Mapping**.
99
+
3. Select the **Send message** action.
100
+
4. Choose the trigger event for when the message should send.
| Channel | The channel to send the message on. | Options: SMS, MMS, WhatsApp. |
110
+
| Sender Type | The sender to use for the message. | Options: Phone number or Messaging Service. Phone numbers must be approved in Twilio. |
111
+
| 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. |
112
+
| To Phone Number | The recipient's phone number. | Must be in [E.164 format](https://www.twilio.com/docs/glossary/what-e164){:target="_blank"}. |
113
+
| From Phone Number | The sending phone number. | Must be approved in Twilio and support the selected Channel. |
114
+
| Messaging Service SID | The messaging service SID to use. | Required if Sender Type is Messaging Service. |
115
+
| Content Template SID | The SID of the content template to use. | Required unless Content Template Type is Inline. |
116
+
| Content Variables | Variables used in the content template. | Variables must be pre-defined in Twilio. |
117
+
| Inline Template | The message body for inline messages. | Supports variables (for example, `Hello {{first_name}}`). Shown only if Content Template Type is Inline. |
118
+
| 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. |
119
+
| Validity Period | How long Twilio keeps trying to deliver the message (in seconds). | Optional. Default is 14400 seconds (4 hours). Range: 1–14400. |
120
+
| 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. |
0 commit comments