Slack integration

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, and mentions. It requests write access for messages, reactions, and canvases. 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, and reactions:read.
• Write: chat:write, reactions:write, and canvases:write.
• Commands: commands.

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_mention

For trigger and agent integration fields, see the workflow schema reference.

Capabilities

Connect Slack to create an integration connection.