By default, Dispatch ships with support for Slack. Below, is how to configure the slack plugin to work with Dispatch.
Note: The Slack plugin relies on the Events API to receive events for the event types the bot is subscribed to. Dispatch receives these events at the /events/slack/event API endpoint. This endpoint must be publicly available in order for the Dispatch Slack app to work correctly.
Specifies the Slack app id so Dispatch can filter events from the app.
Specifies the name of the workspace the Slack app is installed in.
Bot Token used to communicate with the Slack API.
Secret used to verify signatures included on each HTTP request that Slack sends.
Used during development to funnel all messages to a particular user.
Active command as displayed in Slack.
Stable command as displayed in Slack.
Close command as displayed in Slack.
Status report command as displayed in Slack.
List tasks command as displayed in Slack.
List participants command as displayed in Slack.
Assign role command as displayed in Slack.
Edit incident command as displayed in Slack.
Engage oncall command as displayed in Slack.
List resources command as displayed in Slack.
To enable Dispatch's slash commands you must create them an point them to the appropriate endpoint:
Ensure that the Command matches the configuration variables above and that Request URL points to the events endpoint of the dispatch server (/api/v1/events/slack/command).
To enable Dispatch to process slack events ensure you configuration looks similar to the following:
To enable Dispatch Dialogs ensure your configuration looks similar to the following:
The following are the scopes required for the Dispatch Slack App to function correctly.
channels:read
chat:write
commands
files:read
groups:history
groups:read
groups:write
im:history
im:read
im:write
mpim:history
mpim:read
mpim:write
pins:write
reactions:read
reactions:write
reminders:write
remote_files:read
team:read
users:read
users:read.email
users:write
channels:read
groups:history
groups:read



