Skip to contentSkip to navigationSkip to topbar
On this page
Looking for more inspiration?Visit the
(information)
You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

Slack (Actions) Destination


Destination Info
  • Accepts Page, Alias, Group, Identify and Track calls.
  • Refer to it as Actions Slack, or Slack (Actions) in the Integrations object
(information)

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(link takes you to an external page) 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

benefits-of-slack-actions-vs-slack-classic page anchor

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.

  1. From the Segment web app, click Catalog, then click Destinations.
  2. Find the Destinations Actions item in the left navigation, and click it.
  3. Click Configure Actions Slack.
  4. Select an existing Source to connect to Slack (Actions).
  5. Click Customized Setup to start from a blank mapping.
  6. In your Slack workspace, create a new Incoming Webhook URL(link takes you to an external page) 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

important-differences-from-the-classic-slack-destination page anchor

Build your own Mappings. Combine supported triggers with the following Slack-supported actions:

(information)

Mapping limits per destination

Individual destination instances have support a maximum of 50 mappings.

Post Message

post-message page anchor

Post a message to a Slack channel.

Post Message is a Cloud action.

Property nameTypeRequiredDescription
Webhook URLSTRING
required

Slack webhook URL.


MessageTEXT
required

The text message to post to Slack. You can use Slack's formatting syntax.(link takes you to an external page)


ChannelSTRING

Optional

Slack channel to post message to.


UserSTRING

Optional

User name to post messages as.


Icon URLSTRING

Optional

URL for user icon image.


Migration from the classic Slack destination

migration-from-the-classic-slack-destination page anchor

Follow the table below to map your existing Slack destination configuration to Slack (Actions).

(warning)

Warning

Slack (Actions) uses Slack's formatting syntax(link takes you to an external page). 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 SettingHow 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.