Understand
Look inside the black box.
Every step, every tool, every decision is on the workflow, and the workflow is what runs. No second version hidden in a prompt somewhere.
Mermaid Flow
The visual builder for agentic workflows.
Triage every issue? Done. Recap the week? Scheduled.
Today that work lives in a chat window or a prompt file. What goes in, what comes out, and nothing in between. The same prompt drifts a little each run, nobody can say why, and every teammate keeps their own copy.
Mermaid Flow is for the work that happens more than once. Pick the work, connect your tools in one click, and build it once. Same steps, same order, every run, whoever presses run, and everyone can see how.
Start with work you already do by hand.
Open one, tell our agent what's different about yours, and run it. 39 templates in the gallery.
Engineering
Triage what comes in.
New issues labeled, deduped, and assigned before anyone has to look.
Research + News
A morning briefing that reads the internet for you.
The news and discussions that matter, in a two-minute read. No setup, no connectors.
Engineering
Docs and diagrams stay current.
Code changes, the docs get checked, and the PR to fix them opens itself.
Product
A summary every Friday.
Release notes and a weekly digest, built from what actually merged.
Engineering
Every PR, checked against your standards.
Your team's conventions on every pull request, with a summary you can act on.
How Mermaid Flow works.
Step 1. Pick.
Start from work you already do. Open a template, tell our agent what's different about yours, and you have a workflow. Or bring a doc, a flowchart, or a skill file you already have.
No blank page
Every step laid out where you can read it
Edit it like a diagram, not like code
What you see is what runs.
Step 2. Connect.
One click to the tools the work lives in. GitHub, Slack, Notion, Linear, Jira, Google Drive. Everything goes over MCP, so there's nothing to configure.
Sign in once, use it across every workflow
Any public MCP server you can sign in to
No API keys to paste, no glue code
Your workflow talks to the same tools your team does.
Step 3. Run.
Watch the first run. Schedule the rest. Hit run and watch your agent work, step by step. Put it on a schedule and it's automated.
Same steps, same order, every run
Runs whether you're watching or not
Every run kept
Come back tomorrow and see exactly what it did.
Step 1. Pick.
Start from work you already do. Open a template, tell our agent what's different about yours, and you have a workflow. Or bring a doc, a flowchart, or a skill file you already have.
No blank page
Every step laid out where you can read it
Edit it like a diagram, not like code
What you see is what runs.
Step 2. Connect.
One click to the tools the work lives in. GitHub, Slack, Notion, Linear, Jira, Google Drive. Everything goes over MCP, so there's nothing to configure.
Sign in once, use it across every workflow
Any public MCP server you can sign in to
No API keys to paste, no glue code
Your workflow talks to the same tools your team does.
Step 3. Run.
Watch the first run. Schedule the rest. Hit run and watch your agent work, step by step. Put it on a schedule and it's automated.
Same steps, same order, every run
Runs whether you're watching or not
Every run kept
Come back tomorrow and see exactly what it did.
For the workflows where the thinking is the work.
Rely
Steps, not a prompt.
Same path every time. The AI thinks inside a step; the workflow decides what happens next. Run it a hundred times, get a hundred of the same thing.
Build
No terminal required.
The tools that build these today assume you live in a terminal and a wall of markdown. Here, building one feels like working with a diagram, not writing code. Same power, none of the intimidation.
Maintain
Every run logged.
Open any run and see what went into each step and what came out. When something breaks, you know which step.
Share
One workflow, not ten versions.
Send the link and your teammate runs what you run: same steps, same tools, same instructions. Change it once and everyone's on the new version.
Plugs into the tools the work already lives in.
One click to any public MCP server you can sign in to. GitHub, Slack, Notion, Linear, Jira, Google Drive, Gmail, Sentry, Postgres, and more as services open up.
Runs where you need it to.
Scheduled
Daily, weekly, or the first Monday of the month. It runs without you remembering to.
From your tools
Your workflows are reachable over MCP. Run them, edit them, open them from the agent or editor you already work in.
Triggered
Coming soonA new issue, a merged PR, a webhook. Something happens, the workflow starts.
Start free. Pay when it's running your work.
Already have a Mermaid account? Runs come bundled with every plan. A run is one workflow, start to finish. Failed runs are free.
Basic
Free
For seeing one of your own workflows run
-
15 workflow runs per month
Plus
$10 per user / month
Billed annually
For individuals running their own workflows
-
15 workflow runs per user, per month
-
Full run history
Premium
$20 per user / month
Billed annually
For advanced users and teams running AI workflows
-
500 shared workflow runs per month
-
Your choice of model
Enterprise
Custom
Billed annually
For organizations that need scale and control
-
Custom run allowance
-
Custom contract & invoicing
-
Dedicated Customer Success Manager
Pick a workflow. Connect your tools. Hit run.
Start with one of ours, or bring your own.
FAQ
Have questions about Mermaid Flow? These should help.
A place to build agentic workflows and run them. Start from a template or describe what you want, and every step is laid out where you can see it. What you see is what executes. A chat window is great for a quick one-off; Mermaid Flow is for the work you do every week or every time something happens.
A diagram describes how something works. A workflow does the work. You've used Mermaid to understand your processes. This is where you run them.
No. Describe what you want in plain language, or bring a doc, a flowchart, or a skill file you already have. The syntax is there when you want it.
No. If you can read a flowchart, you can build and edit a workflow. Connecting your tools is one click, and there's no terminal and no code unless you want them.
Any public MCP server that lets you sign in, including GitHub, Slack, Notion, Linear, Jira, and Google Drive. Some services only accept approved clients or don't have a public MCP server yet. That list gets shorter as more of them open up.
Yes. Put a workflow on a schedule and it runs without you. Starting a workflow from a webhook or an event in a connected tool is coming soon.
Keep building there. Bring the skill file over when you want it to run without you, on a schedule, the same way every time, where your team can see it.
For a two-step integration with no AI in it, those are the better choice. Mermaid Flow is for the workflows where the thinking is the work and where you need to read them in a PR later. It's also simpler to pick up: people who've used both tell us Mermaid Flow is the easier one to build in. Yours is a Mermaid diagram, text underneath, so it renders anywhere Mermaid does and travels with the rest of your team's docs.
Keep the framework for production systems. Mermaid Flow is the version the rest of your team can read.
A run is one execution of a workflow in Mermaid Flow, start to finish, however it's triggered. Every plan includes runs: 15 per user each month on Basic and Plus, 500 shared across your organization on Premium, and custom on Enterprise. Runs reset monthly and are separate from AI credits. Workflows don't count toward your diagram limit.
Yes. Your Mermaid account signs you into Mermaid Flow, so a teammate you send the link to can open the workflow, see what it does, and run the same version you do.
The run stops, and you can see where it stopped and what each step before it produced. Failed runs don't count against your allowance.
There's a free allowance so you can build a workflow and watch it run. Runs are bundled into every Mermaid plan; paid plans raise the number of runs and how much history you keep.
