Slack Trigger

🕙  2 minute read

Starts a Workflow instance when a custom Slack command is used within Slack. Set up custom Slack commands anywhere in your Slack workspace—use /catalytic start pizzaparty to kick off a lunch order, or /catalytic start weeklyreport to get ready for the week.

This trigger requires a preconfigured Slack integration. For more information on integrating Catalytic with other systems, refer to the Slack integration setup guide.

How to configure this trigger

As with all triggers, a Workflow is a prerequisite for using the trigger.

You can add new triggers or configure any existing triggers on a Workflow’s edit screen. Triggers are configured for each Workflow.

  1. Select Workflows from the top navigation bar
  2. Choose a Workflow, this will open the Workflow detail page
  3. Select Open Builder in the upper-right corner to get to the Workflow Builder page.
  4. Add or edit a trigger under Triggers & Fields section.

Fields for this trigger

  • Trigger name

    • Enter the trigger name. This is used to reference or identify the trigger.
  • Integration

    • Select from a list of all previously authorized Slack integrations.
  • Trigger Command

    • This is the command you will use in Slack to start the process. It should be short, memorable, and related to the process. The command will be /catalytic start {{trigger command}}. Whitespace isn’t allowed.

What will this output?

Every time the Slack slash command is entered, an instance of a Workflow starts. Attributes each command, like the user who used the command, the channel they were in, or additional text added are available as fields within the Workflow.

Output fields for this trigger

  • channel_id

    • This will be the unique Channel ID where the Slack command was entered.
  • channel_name

    • The name of the channel where the command was entered. The field will be directmessage if the command was entered in any Slack direct message.
  • response_url

    • The URL used for the automated command response. See Slack’s article on the response URL.
  • sentToSlack

    • True or false whether the response was sent.
  • team_domain

    • The team name where the Slack command was entered.
  • team_id

    • The team ID where the Slack command was entered.
  • text

    • The part of the Slack command after /catalytic. This text can be used as a parameter to provide conditions for the command.
      • For example, if a user enters /catalytic start purchaserequest, this field will return start purchaserequest. If a user enters /catalytic start purchaserequest apples, this field will return start purchaserequest apples
  • trigger_id

    • Slack provides a trigger ID if the command response will include a dialog.
  • user_id

    • The ID of the user who triggered the command.
  • user_name

    • The plain text name of the user who triggered the command.
  • username

    • The plain text username of the user who triggered the command.

Sorry about that. What was the most unhelpful part?

Thanks for your feedback

We update the Help Center daily, so expect changes soon.

Link Copied

Paste this URL anywhere to link straight to the section.

Need more help?

If you're signed in to Catalytic Community, you can ask other users a question. You'll be redirected to Community where you can add more info.