Skip to content
Forgecroft Docs

Slack Integration

Connecting Slack

Section titled “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

Section titled “What Slack Provides”

Decision Packets

Section titled “Decision Packets”

When a pull request is evaluated by the CI gate, Forgecroft can post the decision to a Slack channel: the verdict (go / conditional_go / no_go / insufficient_context), the blast radius, and a link to the full review in the Console. On re-evaluation of the same change, the original message is updated in place and a threaded reply records what changed, so a channel keeps one running thread per change rather than a stream of duplicates.

Delivery is opt-in per evaluation: the caller supplies the target channel and the Console link, and the org must have a connected Slack workspace.

Managing Connections

Section titled “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

Section titled “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
Section titled “Related”