# A BPMN process diagram from your meeting notes

> Give Claude Code, Codex, Cursor or Copilot your workshop notes or a meeting transcript, and with CoPage it draws the process in BPMN notation (lanes, start and end events, tasks, gateways and labelled flows), checks that every flow is connected and exports an editable SVG, PNG or draw.io file. CoPage draws BPMN as a diagram; it doesn't read or write BPMN 2.0 XML files.

Process workshops produce pages of notes: who does what, what happens when a claim is rejected, which step a system
takes over. Turning them into a process diagram is slow by hand, and a picture from a chat assistant can't be fixed
when the client corrects a step. With CoPage, your agent draws the process as a real diagram that you, your team and
the agent keep editing.

## What the agent draws

CoPage has no separate BPMN palette. The agent builds BPMN notation from CoPage's shapes and connectors, the way our
own sample process is drawn:

| BPMN element | In CoPage |
| --- | --- |
| Pool or lane | A box across the diagram with the role's name in a header on the left |
| Start event | A circle with a thin border, labelled ("Disputes a charge") |
| End event | A circle with a thick border |
| Task | A rounded box with the step's name |
| Exclusive gateway | A diamond with the question ("Credit ≤ €50?") |
| Sequence flow | A connector attached to both shapes, with a label such as "yes" or "no" |

Connectors take elbow, straight or curved routes and can leave from a chosen side, so flows stay readable when they
cross lanes.

## How it works

1. **Set up.** With the free CLI: `copage init` and `copage skill install` in your project (or `copage connect` for
   MCP). In the CoPage app, connect your agent to your workspace instead.

2. **Hand over the notes.** Any text your agent can read: meeting notes, a Teams, Zoom or Google Meet transcript, a
   list of steps from a workshop. Say what you need, for example: "Draw the as-is claims process from
   notes/claims-workshop.md in BPMN: one lane per role, gateways for every decision, and list anything the notes
   leave open."

3. **The agent draws, looks and fixes.** It creates the diagram (`copage diagram new "Claims process" --ops
   ops.json`), renders it to see the layout (`copage diagram render <id>`) and runs the checks
   (`copage diagram check <id>`): every connector attached at both ends, nothing stacked, nothing left unconnected,
   no placeholder text. It fixes what they find and renders again.

4. **Correct it with the people who were there.** `copage open` opens the editor in the browser. Move a task, rename
   a lane, add a missing branch, or tell the agent what's wrong. When the agent works on it again, it gets the list of
   changes people made and builds on them.

5. **Export or put it on a slide.** `copage diagram export <id> docs/claims-process.svg` (or `.png`, `.drawio`). In
   the CoPage app, the same diagram goes on a proposal slide as a linked diagram.

## What you get

- An **SVG** or **PNG** that carries the diagram inside it, so it opens for editing again.
- A **.drawio** file for colleagues in draw.io, and **.json**, CoPage's own format.
- The process on a slide, comments for people and for your agent, and native PowerPoint export, where the diagram
  goes in as one vector picture. (CoPage app, early access)

## What it is not

- **Not BPMN 2.0 XML.** CoPage doesn't import or export `.bpmn` files, so a process engine such as Camunda can't run
  what it draws. Use it for diagrams people read: workshops, proposals, documentation.
- **Not every BPMN symbol.** Message, timer and other event markers, data objects and subprocess markers have no
  built-in shape; the agent can approximate them with shapes, icons and text.
- **Not a recorder.** CoPage doesn't record or transcribe meetings; your meeting tool writes the transcript.

## Who it's for

Business analysts, solution architects and consultants who run process workshops and need the result as a clear
diagram the same day, and pre-sales teams who put the to-be process into a proposal.

## Read more

- [Diagrams](/docs/diagrams): shapes, connectors, routes and exports.
- [Connecting your agent](/docs/agents) and [Checks](/docs/checks).
- [CoPage CLI documentation](/docs/cli). [Install the free CLI](/#cli), or see
  [proposal decks from call transcripts](/use-cases/proposal-decks-from-call-transcripts) for the next step.

## Questions

### Can CoPage export a .bpmn file?

No. CoPage draws BPMN notation as a diagram and exports SVG, PNG, draw.io and its own JSON. It doesn't read or write
BPMN 2.0 XML, so the result is for people to read, not for a process engine to run.

### Which BPMN elements can the agent draw?

Lanes, start and end events, tasks, exclusive gateways and labelled sequence flows, built from CoPage's boxes,
circles, diamonds and connectors. Other symbols can be approximated with shapes and text.

### Can the agent work from a meeting recording?

From its transcript. Teams, Zoom and Google Meet can save one; give the file to your agent. CoPage doesn't record or
transcribe calls.

### Can I fix the process by hand after the agent draws it?

Yes. Open it in the editor with `copage open`, or open the exported SVG or PNG with `copage diagram open`. The agent
sees your changes the next time it works on the diagram and keeps them.

### Do I need the CoPage app for this?

No. The free CLI draws, checks and exports process diagrams on your computer, with no account. The app adds decks,
comments and a team workspace.