Canopy with Slack
Define how work should happen once, then run it from where your team already is. Slack is one of Canopy's surfaces: the brief arrives there, the approval happens there, and the engine keeps the record.
What Canopy does in Slack
- Delivers the morning brief, the exception queue, and the decisions that need a person
- Takes approvals and overrides in the thread, and remembers the reasons
- Triggers workflows from a message, with rules checked before anything runs
- Reports what changed while you were away — nothing starts from zero
Same workflow, every surface
A workflow defined in Canopy runs the same way from Slack, web, CLI, or API. Slack is a surface, not a separate bot with separate behaviour — the harness, memory, and audit trail are identical.
Is Canopy a Slack bot?
Slack is one surface Canopy runs on. The workflows, rules, and memory live in the control center; Slack is where briefs arrive and approvals happen, alongside web, CLI, and API.
Can approvals happen in Slack?
Yes. Draft-and-approve workflows present the draft where your team works, a person approves or overrides, and the decision — with its reason — is remembered by the engine.
What does Canopy surface in Slack?
Only what needs a decision: a break in a pattern, a chance you missed, a shift worth noticing. Not a dashboard you have to watch — a control center that watches for you.