Slack (Actions) Destination
Additional versions of this destination are available
This page is about the Slack (Actions) Destination. See below for information about other versions of the Slack destination:
Slack is a team collaboration tool work flows. It’s where the people you need, the information you share, and the tools you use come together to get things done.
Benefits of Slack (Actions) vs Slack Classic
Slack (Actions) provides the following benefits over the classic Slack destination:
- Consolidated Message Sending. Send multiple messages from a single instance of the Slack (Actions) destinations. Use Event Triggers to send a message when your criteria is met.
- Streamlined Configuration. Configure connection details on a per-message basis, rather than for the destination as a whole. This enables sending messages to different workspaces or channels from one source.
- Easier access to data. The event variables picker shows you all the available data from the event you use to test the Trigger. Variables are clearly labeled to ensure they stand out from other text and markup.
Getting Started
- From the Segment web app, click Catalog, then click Destinations.
- Find the Destinations Actions item in the left navigation, and click it.
- Click Configure Actions Slack.
- Select an existing Source to connect to Slack (Actions).
- Click Customized Setup to start from a blank mapping.
- In your Slack workspace, create a new Incoming Webhook URL and select the Slack channel associated with your account that you’d like to send messages to. The Slack channel you select will be the default channel that receives message events. Paste the Incoming Webhook URL you created into each of your Slack Destination’s Actions under the field labeled
Webhook URL*.
Important differences from the classic Slack destination
- The classic Slack destination formats messages using the handlebars syntax. Slack (Actions) follows Slack’s formatting syntax.
Available Actions
Build your own Mappings. Combine supported triggers with the following Slack-supported actions:
Mapping limits per destination
Individual destination instances have support a maximum of 50 mappings.
Post Message
Post a message to a Slack channel.
Post Message is a Cloud action.
| Field | Description |
|---|---|
| Webhook URL* | Type: STRINGSlack webhook URL. |
| Message* | Type: TEXTThe text message to post to Slack. You can use Slack’s formatting syntax. |
| Channel | Type: STRINGSlack channel to post message to. |
| User | Type: STRINGUser name to post messages as. |
| Icon URL | Type: STRINGURL for user icon image. |
Migration from the classic Slack destination
Follow the table below to map your existing Slack destination configuration to Slack (Actions).
Slack (Actions) uses Slack’s formatting syntax. This requires that you manually re-enter any messages from Slack Classic, and pick event data from the event variable picker. The handlebars syntax from Slack Classic is not compatible.
Slack settings mapping
| slack Classic Destination Setting | How to enable in slack (Actions) | |
|---|---|---|
| Connection Settings | ||
| Event Channels |
In Slack (Actions), events and channels are set per subscription. |
|
| Identify Template |
In Slack (Actions), you do not need a specific template for Identifying users. Use the Messages field to write your message, and add data from the event. |
|
| Event Template |
In Slack (Actions), you do not need a specific template for specific Events. Use the Filter and Messages field to specify the incoming event, and write your message with data from the event. |
|
| Incoming Webhook URL |
Available as a subscription-level setting on the Post Message action. |
|
| Whitelisted Traits |
Use the Messages field in the Post Message action to create your message with any traits from an incoming Identify call. |
|
This page was last modified: 06 Feb 2024
Need support?
Questions? Problems? Need more info? Contact Segment Support for assistance!