Slack Integration

Connecting Slack

1. Start the OAuth flow: GET /oauth/slack/start
2. You are redirected to Slack to authorize the app
3. After authorization, Forgecroft exchanges the code for a bot token
4. The connection is stored with the token in the secrets vault

What Slack Provides

Notifications

Run events (completed, failed, requires approval) are sent to configured Slack channels.

Interactive Approvals

When a run requires approval and Slack is connected:

1. Approvers receive a Slack message with approve/reject buttons
2. Clicking a button sends an interactive action to Forgecroft
3. Forgecroft resolves the Slack user → email → Forgecroft user
4. RBAC is checked — the user must have approve or reject verb on the workspace
5. The run is approved or rejected
6. An ephemeral response is posted in Slack

Email Matching Requirement

The Slack user’s email must match a Forgecroft account in the same org. If no matching account is found, the approval fails.

Managing Connections

List connections:

GET /slack-connections

Disconnect:

DELETE /slack-connections/{id}

This removes the connection and deletes the bot token from the secrets vault.

Slack Events API

Forgecroft also receives Slack Events API payloads for:

• app_mention — acknowledged with :eyes: reaction
• message in DM — acknowledged with :eyes: reaction
• assistant_thread_started — sets “is thinking…” status

Related

• Notification Channels — Configuring Slack notification channels
• User Preferences — Setting Slack DM as your notification channel