Slack

Connect your Slack workspace to ProxifAI to receive notifications, create issues from Slack, and take quick actions without leaving your messaging app.

Connecting Slack

The Slack integration is a Provider that ships with the OSS build (internal/integrations/slack/). Connect via OAuth — ProxifAI stores the workspace’s bot token, then verifies the connection on every save by calling Slack’s auth.test API.

Install the Slack app

Settings → Integrations → Slack → Connect Slack Workspace redirects you to Slack’s OAuth authorization page. The OAuth callback hits /api/v1/webhooks/slack/oauth on the deployment.

Authorize the workspace

Slack lists the requested scopes — message posting, slash commands, event subscriptions, interactive components. After approval, the bot token is exchanged and stored encrypted in the integration’s credentials.

Verify the connection

ProxifAI runs client.TestAuth(ctx) immediately. The integration’s status flips to active (or surfaces the auth error if the token is invalid).

Configure routing and notifications

Pick a default channel for org-wide events; add per-project, per-team, or per-event-type routing rules under Channels.

pfai integration ls --provider slack            # status of connected workspaces
pfai integration verify <integration-id>        # re-run auth.test
pfai integration view <integration-id>          # see the credentials envelope (token redacted)

Notifications

Receive real-time updates in Slack when key events occur:

Event	Description
PR reviews	Notified when a pull request is submitted for review, approved, or has changes requested
Pipeline failures	Alerts when CI/CD pipelines fail, with links to logs
Workflow approvals	Human-in-the-loop approval requests with inline approve/reject buttons
Issue assignments	Notified when an issue is assigned to you or your team
Release published	Alerts when a new release is created
Agent completion	Notified when an AI agent execution finishes (success or failure)

Notifications include contextual information — PR diffs, pipeline error messages, issue details — so you can triage without switching to the ProxifAI UI.

Slash commands and event subscriptions

Slack’s Events API and slash commands both deliver to the same inbound URL — /api/v1/webhooks/inbound/<slug> — registered when the workspace connects. The Slack provider verifies Slack’s X-Slack-Signature header (signing secret) before doing anything else, then dispatches:

/proxifai slash commands → the slash-command handler turns the command + args into a PlatformEvent you can react to with trigger rules (the slack_trigger is the first-class consumer)
App mentions (@proxifai in a channel) → published as webhook.slack.app_mention events
Direct messages to the bot → published as webhook.slack.message

The exact slash-command surface is configured on Slack’s app dashboard, not in ProxifAI — register the commands you want, then write trigger rules that match on data.command. The handler treats commands as opaque strings rather than hardcoding /proxifai issue etc., so you compose your own Slack-driven UX without recompiling.

Interactive Actions

Slack messages from ProxifAI include action buttons for quick responses:

Approve / Reject — respond to workflow approval requests inline
Assign to me — take ownership of an unassigned issue
View in ProxifAI — open the resource in the ProxifAI web app
Snooze — mute notifications for a specific issue or PR for a configurable duration

Interactive actions respect your ProxifAI permissions. You can only approve, assign, or modify resources that your role allows.

Channel Configuration

Route notifications to the right channels:

Organization-wide channel — receives all notifications not routed elsewhere
Per-project channels — route specific project notifications to dedicated channels
Per-team channels — team mentions and assignments go to the team’s channel
DM notifications — personal assignments and mentions are sent as direct messages

Configure channel routing from Settings > Integrations > Slack > Channels.

Create a dedicated #proxifai-alerts channel for pipeline failures and agent errors to keep noise out of general channels.