Document key decisions in Confluence automatically

An Orkeste agent watches meeting notes and decision-tagged Slack threads, drafts a structured Decision Record in Confluence, and waits for the decision owner to approve before publishing to the team space.

How the workflow runs

1. Watch decision sources: Listens to tagged Slack threads, meeting notes and design docs.
2. Extract decision structure: Identifies context, options considered, decision, owner and date.
3. Draft decision record: Composes a structured ADR-style page in Confluence.
4. Owner approves: Decision owner reviews and approves before the page is published.
5. Publish in Confluence: Page is published in the right space with tags and links to source threads.

Human-in-the-loop: Decision records are only published in Confluence after the decision owner explicitly approves the framing.

Works with your stack

• confluence
• slack
• notion

Related workflows

• Summarize meeting notes and extract actions in Notion
• Auto-create sprint tickets in Jira from planning docs
• Announce product updates internally on Slack

Questions about this workflow

What template does it use?

Your existing decision-record template. The agent fills sections, never invents new ones.

Can it back-fill historical decisions?

Yes. You can run a back-fill against archived Slack channels and meeting notes.

Who can be a decision owner?

Anyone you designate. The agent never auto-approves; the named owner must sign off.