Skip to content

Slack integration

Connect Threada to Slack for governed slash-command intake, escalation alerts, and optional governed channel posting.

Add to Slack View integration docs

Overview

The Slack Marketplace app enables governed `/threada` slash-command intake from mapped channels. Tenant admins can separately enable governed channel posting with a bot token stored in Secret Manager.

Capabilities

  • Create WorkItems from `/threada` slash commands in mapped channels
  • Optionally post WorkItem summaries and escalation alerts to channels after a governed posting credential is installed
  • Notify reviewers in Slack when an approval is pending (reviewers approve in Threada Work)
  • Route notifications by policy classification and priority
  • Audit trail for WorkItems created from Slack commands and governed Slack posting actions

A worked example

One end-to-end flow Threada runs with Slack:

  1. A team member runs `/threada` in a mapped Slack channel, and Threada creates a governed WorkItem with a typed schema.
  2. Threada drafts a grounded answer or proposes an action; if governed posting is configured, it can alert the right reviewer in Slack that an approval is pending.
  3. The reviewer opens Threada Work and approves or rejects at an explicit decision step; the approved action then runs as a governed action, with idempotency.
  4. If governed posting is configured, the outcome can be posted back to the channel; the WorkItem audit trail records the Slack command and governed posting action.

Setup

Configure the integration in Studio under pack governance. Install the Threada Slack app with the command scope and map channels to your workflow definitions. Add governed posting only when a tenant admin supplies a bot token through the directory credential route.

  1. In Studio, add the Slack integration under pack governance.
  2. Install the Threada Slack app with the least-privilege commands scope.
  3. Map the channels where `/threada` may create WorkItems; optionally add a governed Slack posting credential for outcome posts and reviewer alerts.
  4. Validate the connection; the integration activates only after the test succeeds.

Permissions & data access

Slack connects through least-privilege surfaces, each with a credential you control.

  • The Threada Slack Marketplace app requests a single OAuth scope — commands — so it only receives your /threada slash-command invocations and stores no Slack Web API token.
  • Governed channel posting uses a tenant-provided Slack bot token stored in Secret Manager and used only for the workspaces and channels you map.
  • Inbound slash-command requests are verified before Threada creates a WorkItem.
  • Uninstalling or disabling the integration stops intake and posting and preserves the audit history for WorkItems already created.

Frequently asked questions

Can people approve actions directly in Slack?
Not in Slack itself. Slack receives a notification that an approval is pending; the reviewer approves or rejects at an explicit decision step in Threada Work, and only then does the governed action run. The outcome can be posted back to the channel.
Does Threada capture intake from Slack?
Yes, through the `/threada` slash command in mapped channels. Threada does not read channel history or convert arbitrary channel messages into WorkItems.
What access does the integration need?
The public Slack app uses the commands scope for slash-command intake. Governed channel posting requires a separate tenant-provided bot token with `chat:write`. WorkItems and governed posting actions are logged on the audit trail.
View integration docs