Workflows

Slack history becomes operating state.

Choose a workflow contract, point it at one to five channels, and get validated JSON that another tool can use. No transcript archaeology. No prompt-shape roulette.

Build my first workflow Compare plans
Live hosted tool · read-only · one AI credit

Contract proof

One call in. Contract-shaped JSON out.

slack_workflow_brief reads up to five channels, applies one named workflow contract, and rejects output that is missing a required key.

MCP call
{
  "workflow_kind": "support_inbox",
  "channel_ids": ["C_SUPPORT"],
  "focus": "unowned renewals"
}
Representative output
{
  "open_threads": [
    {
      "thread": "ACME renewal question",
      "state": "waiting_on_owner"
    }
  ],
  "ack_lag": [
    {
      "channel": "C_SUPPORT",
      "minutes": 18
    }
  ],
  "owner_gaps": [
    "Renewal follow-up is unassigned"
  ],
  "escalations": [],
  "next_actions": [
    "Assign the renewal follow-up before 10:00"
  ]
}

Proof boundary: this is a representative product demo built from synthetic support data, not customer evidence. Customer-approved proof is published only after explicit consent and operator review.

Five contracts

Choose the operating question, not a generic summary.

support_inbox 5 validated keys

Pro fit for solo support operators. Team fit when 2-10 people share the inbox and need synced profiles.

Callslack_workflow_brief({ workflow_kind: "support_inbox", channel_ids: ["C…"] })
open_threadsack_lagowner_gapsescalationsnext_actions
incident_room 5 validated keys

Team fit for 2-10 person on-call rotations. Ops fit when SLA, custom retention, or SOC2 evidence become hard requirements.

Callslack_workflow_brief({ workflow_kind: "incident_room", channel_ids: ["C…"] })
incident_summarytimelineopen_risksowner_gapsnext_actions
exec_brief 5 validated keys

Pro fit for solo founders / executives. Save the exec brief once, then deliver it daily at 8am in the profile timezone.

Callslack_workflow_brief({ workflow_kind: "exec_brief", channel_ids: ["C…"] })
summarydecisionsrisksasksaction_items
product_launch_watch 5 validated keys

Team fit for product ops squads. Free tier validates the pattern. Pro fit for solo PM operators running daily.

Callslack_workflow_brief({ workflow_kind: "product_launch_watch", channel_ids: ["C…"] })
launch_signalsfeedback_themesblockersmetricsnext_actions
custom 4 validated keys

Any plan. Use when the four named profiles don't match your workflow shape — define your own channels + priority people + cadence.

Callslack_workflow_brief({ workflow_kind: "custom", channel_ids: ["C…"] })
summaryhighlightsopen_questionsnext_actions

Profile continuity

Save once. Run by name. Deliver on schedule.

Saved profiles are live. The OSS package keeps profiles local; hosted slack_workflow_save stores the same tenant-scoped contract in D1. Call slack_workflow_brief with profile_name, or let Pro and Team deliver daily at 8am or Monday at 8am with persistent credentials.

npx -y @jtalk22/slack-mcp --apply-template oncall-handoff

Buyer FAQ

  • Are these separate MCP tools?The hosted inference layer includes slack_workflow_brief alongside slack_catch_me_up, slack_triage, and slack_smart_search. Call slack_workflow_save once to persist a tenant-scoped profile, list it with slack_workflows, then call slack_workflow_brief by profile_name. Direct workflow_kind plus channel_ids calls remain supported.
  • Why structured JSON outputs instead of free-text summaries?Operators chain workflow outputs into other tools — Notion, Linear, project trackers, status dashboards. Free-text summaries don't compose. Structured JSON does. slack_workflow_brief enforces the exec_brief shape {summary, decisions, risks, asks, action_items} today so downstream automation can rely on the keys.
  • When do I need Pro vs Team?Pro at $19/mo gives you unlimited requests, unlimited inference calls, saved profiles, opt-in encrypted credential storage, and scheduled delivery daily at 8am or Monday at 8am. Team at $49/mo flat adds shared workflow profiles across 5 workspaces and 24h support. Pro is solo. Team is squad.

Run it on your Slack

25 AI calls. No card.

Start free, prove one real workflow, then move to Pro when the brief becomes a habit.

Start free Start Pro $19/mo Customer proof Review a team rollout