Slack integration
Look up the Slack integration's availability, OAuth access, integration connection identity, and agent tools.
Slack connects a Slack workspace to Shipfox. Agent steps can use selected Slack tools through the integration connection.
Categories and related terms
Category: Messaging.
Related terms: ChatOps, notifications.
Availability: Available.
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, andreactions:read. - Write:
chat:write,reactions:write, andcanvases: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 connection in an agent integration selection.
integrations:
- connection: slack_acme
include: [read_channel]For the agent integration contract, see the workflow schema reference.
Capabilities
| Capability | Availability |
|---|---|
| Source control | Not available. |
| Events | Not available. |
| Agent tools | Available. View Slack agent tools. |
Connect Slack to create an integration connection.