Slack
Call the Slack Web API from a dock with a bot token.
Connect with a bot token (PUT /v1/workspaces/:workspaceId/connectors/slack with
{ "token": "xoxb-..." }) or with OAuth when SLACK_CLIENT_ID and
SLACK_CLIENT_SECRET are set. See Connectors for the routes.
The account label is the Slack team name.
| OAuth bot scopes requested | channels:read, channels:history, chat:write, users:read, app_mentions:read |
| Web API in a dock | $DOCK_SLACK_API_URL/<method>, for example chat.postMessage |
| MCP in a dock | not available |
A mention of the app (app_mention) by a full member of the workspace starts a run
and is answered in its thread; guests and Slack Connect users are refused. See
Triggers and replies. The bot must be in the channel.
Only Web API method names are accepted as the path (letters, digits and dots).
curl -H "Authorization: Bearer $DOCK_CONNECTOR_TOKEN" -H "content-type: application/json" \
-d '{"channel":"C123","text":"build finished"}' $DOCK_SLACK_API_URL/chat.postMessagePull requests
An admin can link a Slack channel id (or *) to a GitHub repository so runs started from Slack open draft pull requests there, with the link posted in the reply. Links are managed with PUT /v1/workspaces/:workspaceId/connectors/slack/repo-links; see Open pull requests in a linked repository. Scope key: channel id.