Slack

The Slack integration brings 4RGE into your team's chat — start tasks from a channel and get notified when runs finish. When fully connected, Slack acts as both a trigger source for automations and a notification channel for run status updates.

Planned capabilities

Current dashboard behavior

Slack appears on Dashboard → Integrations alongside GitHub, Linear, and Jira. Unlike GitHub, Slack has no connectUrl wired — clicking Connect shows a toast: Slack integration setup is not connected yet. No OAuth tokens or channel selections are persisted today. The automation trigger picker may list Slack, but those triggers are not active in production.

Alternatives on the same page

While Slack is incomplete, use capabilities that ship today on the Integrations page:

Paid plan tiers gate some integration UI in the product spec — Slack cards may appear before the connect flow is ready. Treat GitHub as the production trigger source until Slack OAuth ships.

Connecting (when available)

1. Add the Slack app

   From the Integrations page in the dashboard, authorize the 4RGE Slack app for your workspace. A workspace admin may need to approve the install.

2. Choose channels

   Pick the channels where 4RGE can post notifications and listen for commands. Prefer a dedicated #x4rge-agents channel over general channels to reduce noise.

3. Map to your organization

   Confirm the Slack workspace is linked to the correct 4RGE organization so permissions and budget policies apply.

4. Test a notification

   Start a manual cloud run and verify a completion message appears in the selected channel.

What it will enable

• Kick off agent tasks from a message or slash command.
• Receive run status and completion notifications with links to diffs and PRs.
• Trigger automations when messages match patterns (for example, a posted Sentry alert URL).
• Route notifications by team — members only see activity they're allowed to access.

Example automation trigger (planned)

{
  "kind": "slack",
  "channel": "C01234567",
  "event": "message",
  "pattern": "/agent triage"
}

Until Slack triggers are active, use schedule or GitHub triggers for production automations.

Notification format (planned)

Workaround today

Until Slack is connectable:

1. Use GitHub automations for event-driven cloud runs.
2. Subscribe to PR notifications through GitHub's native Slack integration for merge-ready output.
3. Monitor runs in Sentinel or the Agents workspace directly.

Security considerations