Skip to content

Commit 17c7d3d

Browse files
committed
more fine tuning
1 parent bbdd88c commit 17c7d3d

File tree

1 file changed

+20
-2
lines changed
  • src/connections/destinations/catalog/actions-twilio-messaging

1 file changed

+20
-2
lines changed

src/connections/destinations/catalog/actions-twilio-messaging/index.md

Lines changed: 20 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,12 +26,11 @@ Twilio Messaging integrates tightly with Segment's data and audience tools, so y
2626
> info "Twilio Messaging Destination Private Beta"
2727
> Bidirectional sync is in Private Beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available.
2828
29-
3029
## Getting started
3130

3231
To start sending messages through Twilio Messaging, you'll set up your Twilio account credentials and connect the destination in Segment.
3332

34-
At a high level, you will:
33+
You'll set up the Twilio Messaing destination in three stages:
3534

3635
1. Create a Twilio API Key and Secret.
3736
2. Add the Twilio Messaging destination in Segment.
@@ -54,3 +53,22 @@ To create your API Key and Secret:
5453
7. Click **Done** to finish creating the API Key.
5554

5655
You now have your **Account SID**, **API Key SID**, and **API Key Secret**, which are required to connect Twilio Messaging in Segment.
56+
57+
## Add the Twilio Messaging destination
58+
59+
After setting up your Twilio credentials, add the Twilio Messaging destination to your Segment workspace.
60+
61+
To add the destination:
62+
63+
1. From the Twilio Messaging destination page, click **Add destination**.
64+
2. On the Setup screen, give the destination a name and select **Fill in settings manually.**
65+
3. On your new destination page, click the **Settings** tab.
66+
4. On the Settings tab, enter your **Twilio Account SID**, **Twilio API Key SID**, and **Twilio API Key Secret**.
67+
6. To finish setting up the destination, click **Save Changes**.
68+
69+
The destination is now connected and ready to configure message mappings.
70+
71+
<!-- PW, 6/29/25; during private beta, there's no way to search for the destination in the catalog.
72+
Users can only access the destination through the specific URL. I'll update these instructions once
73+
it's publicly available and searchable in the workspace catalog. -->
74+

0 commit comments

Comments
 (0)