Workflows

Conversation history becomes operating state.

Choose a Slack workflow contract or compare Slack commitments with one Asana project. Get validated JSON another tool can use, with source evidence preserved and no external write hidden inside the analysis.

Build my first workflow Compare plans

60-second walkthrough

See the whole continuity contract before connecting anything.

The silent walkthrough shows the break, the bounded Shadow Report, the Slack-to-Asana discrepancy, the read-only setup boundary, and the first paid offer. It uses sanitized product surfaces and makes no customer or traction claim.

  • One to five selected Slack channels
  • One selected Asana project
  • Source identifiers preserved
  • writes_performed: 0
Silent · exactly 60 seconds · sanitized product surfaces · no customer data
Live hosted tool · read-only · one AI credit

Contract proof

One call in. Contract-shaped JSON out.

continuity_shadow_report reads up to five channels and performs no external writes. Once the report proves useful, slack_workflow_brief can run the same contract on demand or by saved profile.

Read-only MCP call
{
  "tool": "continuity_shadow_report",
  "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"
  ]
}

Read-only boundary: the Shadow Report performs no Slack posts, webhook deliveries, or task changes. 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.

Cross-tool contract · one Asana project · zero external writes

Slack × Asana

Find the commitment that never became reliable work.

continuity_asana_discrepancy_report compares evidence from one to five selected Slack channels with incomplete tasks in one selected Asana project. It identifies missing tasks, owners, due dates, status conflicts, and stale task state without changing either system.

Read-only MCP call
{
  "tool": "continuity_asana_discrepancy_report",
  "slack_channel_ids": ["C_LAUNCH"],
  "asana_project_gid": "1200987654321000",
  "focus": "commitments due this week"
}
Representative output
{
  "summary": "One Slack commitment is not represented by a complete Asana task.",
  "matched_commitments": [],
  "gaps": [
    {
      "type": "missing_due_date",
      "slack_evidence": "C_LAUNCH / 1712345678.000100 · Ship the pricing update on Friday.",
      "asana_task_gid": "1200123456789012",
      "asana_evidence": "Pricing update · owner: Mina · due: none"
    }
  ],
  "task_drift": [],
  "next_reviews": [
    "Confirm Friday with Mina before adding a due date in Asana."
  ]
}

Evidence boundary: source identifiers remain in the report, only the selected project is compared, incomplete-task retrieval is capped at 100, and the response records writes_performed: 0. This synthetic example is representative product proof; it is not customer data.

Connect Slack and Asana Read the setup contract

Five contracts

Choose the operating question, not a generic summary.

support_inbox 5 validated keys

Individual fit for solo support operators. Small team fit when two to five 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

Small team fit for two-to-five-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?continuity_shadow_report is the read-only first run. It returns the same validated workflow shape without posting or delivering anything. Call slack_workflow_save once to persist a useful 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?Individual at $19/mo gives you unlimited requests, unlimited inference calls, saved profiles, and Slack OAuth. OAuth starts read-only; scheduled delivery at 8am daily or Monday is a separate permission. Small team at $49/mo flat adds shared workflow profiles for up to 5 operators and 24h support.
  • Does the Asana comparison change tasks or post to Slack?No. continuity_asana_discrepancy_report reads one selected Asana project and one to five selected Slack channels. It returns matched commitments, gaps, task drift, and next reviews with writes_performed: 0. Creating or updating a task would be a separate, explicit action and is not part of this contract.

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