Jump go di content

Integration with Slack

Connect Threada to Slack for notification wey get governance, escalation alert and request intake.

Add am to Slack See integration docs

Overview

Di Slack integration dey make Threada fit deliver notification, collect intake from channel and route escalation alert — everything under workspace policy.

Capabilities dem

  • Post WorkItem summary and escalation alert go channel dem
  • Collect request intake from channel dem wey you choose
  • Notify reviewer dem for Slack when approval dey pending (reviewer dem dey approve for Threada Work)
  • Route notification by policy classification and priority
  • Audit trail for every message and interaction wey happen

One worked example

One end-to-end flow wey Threada dey run with Slack:

  1. One team member dey post request for one Slack channel wey dem designate, and Threada dey capture am as WorkItem wey get governance with typed schema.
  2. Threada dey draft grounded answer or propose action, and e dey post notification to Slack to alert di right reviewer say approval dey pending.
  3. Di reviewer dey open Threada Work and approve or reject for one explicit decision step; di approved action come dey run as action wey get governance, with idempotency.
  4. We dey post di outcome back to di channel, and we dey record every message and interaction for di audit trail.

Setup

Set di integration for Studio under pack governance. Install di Threada Slack app with scoped permission and map channel dem to your workflow definition dem.

  1. For Studio, add di Slack integration under pack governance.
  2. Install di Threada Slack app with scoped, least-privilege permission.
  3. Map di channel dem wey Threada fit read intake from and post outcome to.
  4. Validate di connection; di integration go only activate after di test don pass.

Permissions plus data access

Slack dey connect through least-privilege surface dem, and each one get im own credential wey you dey control.

  • Di Threada Slack Marketplace app dey request only one OAuth scope — commands — so e dey only receive your /threada slash-command invocation dem, and e no dey store any Slack Web API token.
  • Channel message intake and channel posting dey use one tenant Slack app wey im bot token and signing secret na you dey provide; dem dey store dem inside Secret Manager and dem dey use dem only for di channel dem wey you map — di same credential model wey Threada other integration dem dey use.
  • Dem dey verify inbound Slack request dem against your Slack signing secret before Threada go create WorkItem; outbound alert dem fit also use one Slack incoming webhook URL wey no get token.
  • If you uninstall or disable di integration, e dey stop intake and posting, and e dey keep di audit history for WorkItems wey dem don create already.

Question dem wey people dey always ask

People fit approve action dem straight for inside Slack?
No be inside Slack itself. Slack dey receive notification say approval dey pending; di reviewer dey approve or reject for one explicit decision step inside Threada Work, and na only afta dat one di action wey get governance go run. Dem fit post di outcome back to di channel.
Threada dey capture intake from Slack?
Yes. Message dem for di channel dem wey dem designate dey become WorkItems wey get governance with typed schema, so informal Slack request dey turn structured, trackable record instead of thread wey go lost.
Wetin access di integration need?
Di Threada Slack app wey dem install with scoped, least-privilege permission for di particular channel dem wey dem dey use. We dey log every message and interaction for di audit trail.
See integration docs