Slack integration
Connect Slack to trigger workflows from messages, reactions, mentions, or slash commands, and call Slack tools from workflows.
Authentication
Shipfox uses Slack OAuth with a bot token. Install the Shipfox app in the target Slack workspace and approve its requested bot scopes.
The app requests read access for channel history and metadata, direct-message
history, user profiles, reactions, canvases, and mentions. It requests write access for
messages, reactions, and canvases, and for agents to reply with their own name and
avatar and show their status in Slack's agent view. It also requests the commands
scope for slash commands.
The required bot scopes are:
- Read:
app_mentions:read,im:history,im:read,mpim:history,mpim:read,channels:history,groups:history,channels:read,groups:read,users:read,reactions:read, andcanvases:read. - Write:
chat:write,chat:write.customize,assistant:write,reactions:write, andcanvases:write. - Commands:
commands.
A connection missing either chat:write.customize or assistant:write must
reconnect.
A self-hosted deployment creates its own app from the
Slack app manifest.
Integration connection identity
The slug of a Slack integration connection defaults to slack_<workspace>,
where <workspace> is the normalized Slack team name. For example,
slack_acme. Shipfox uses the team ID when the team name is unavailable, falls
back to slack when neither is available, and makes the slug unique within the
workspace. Use it as a trigger source or as connection in an agent
integration selection.
triggers:
on_mention:
source: slack_acme
event: app_mentionFor trigger, tool step, and agent integration fields, see the workflow schema reference.
Capabilities
| Capability | Details |
|---|---|
| Events | View Slack events. |
| Tools | View Slack tools. |
Connect Slack to create an integration connection.