This step parses the HTTP POST request made by a slack slash command.
- SlackSlashCommandSteps.zip - Workflow zip file with the step and example flow
- Slack.png - Slack logo
Accepts a post request, then gives back the user_name, user_id, command, channel_name, channel_id, and text parameters.
Requires a custom slack app. Within a slash command in the app, set the Request URL as the initiation URL from xMatters.
- Download the SlackSlashCommandSteps.zip file onto your local computer
- Navigate to the Developer tab of your xMatters instance
- Click Import, and select the zip file you just downloaded
The Slack - Parse Slash Command HTTP Trigger is now available in your custom steps. So navigate to the appropriate canvas so you can add the step there. If you'd like to experiment with it, the Slack Slash Command workflow has a canvas that can be triggered via HTTP call.
| Name | Description |
|---|---|
| user_name | Username of slash command caller |
| user_id | user_id of slash command caller |
| command | Slash command that was called |
| channel_name | Name of channel where slash command was called |
| channel_id | ID of channel where slash command was called |
| text | Text that was put after the slash command |
| response_url | Temporary webhook URL that can be used to generate messages responses |
| trigger_id | Short-lived ID that will can be used to open a modal |
| team_id | Context for where the user was in slack when the command was triggered |
| team_domain | Slack domain command was called from |
| enterprise_name | Context for where user is when the command was triggered |
This is an example of using the Slack - Parse Slash Command to trigger an xMatters event.
