Tag: agentic workflows

  • Mermaid Launches Flow, a Visual Builder for Agentic Workflows (2026)

    Mermaid Launches Flow, a Visual Builder for Agentic Workflows (2026)

    Takeaway: On November 18, 2026, Mermaid launched Mermaid Flow, a visual builder that lets people design agentic workflows as diagrams and run those same steps each time. The company says the product is meant for AI work that happens more than once, so a team can build a workflow once and rely on it to follow the same path on later runs. Mermaid Flow is available now at mermaid.ai/flow.

    The launch post and Mermaid’s Flow product page and pricing page are the sources for the details below. In the launch post, Mermaid also said it is on Product Hunt today. We are not reporting a Product Hunt rank or vote count, because the official pages do not publish one.

    What Mermaid Flow is for

    Mermaid argues that a lot of repeated team work — triaging new issues, writing a weekly recap, or giving a pull request a first read — now runs through AI, but often lives in a chat window or a prompt file. In that setup, people can see the input and the output, but not the steps in between. Prompts get copied, tweaked, and rerun, and different teammates can end up with slightly different versions of the same process.

    Flow is meant to put those in-between steps on a diagram that actually runs. Mermaid, which maintains the open-source Mermaid project, says teams already use diagrams to explain how a process should work. In Flow, that picture becomes the thing that executes. The launch post sums this up in four design choices:

    • The steps are fixed. Flow runs the same steps in the same order each time. The model still does the thinking inside each step, but it does not decide what the steps are.
    • Every step between the input and the output is visible, so a surprising result is easier to inspect.
    • There is one shared copy. Anyone on the team can read the workflow, and anyone who runs it gets the same steps as the person who built it.
    • Setup is supposed to stay short: pick the work, connect tools in one click, and run it.

    Starting workflows and how a run works

    Mermaid says the best first workflow is something you already did this week and expect to do again next week. The launch post highlights four starting examples, each framed as small enough to build in minutes: triaging new issues with a team’s existing labels and routing rules; scheduling a weekly recap of what shipped, what is still open, and what is blocked; giving every pull request a first read against a team checklist before a human reviewer opens it; and drafting release notes from work merged since the last release. Those are suggested starting points from the post, not a complete catalog of named product templates.

    The product page says the gallery includes 39 templates, and that you can start from a template, describe what you want, or bring a document, a flowchart, or a skill file you already have. It breaks the work into three stages: pick the workflow, connect the tools the work already lives in, and run it — watching the first run, then scheduling later ones if you want. A run, Mermaid says, is one execution of a workflow from start to finish, however it is triggered. Failed runs do not count against the monthly allowance, and every run is logged so you can see what went into each step and what came out.

    Connections go over Model Context Protocol (MCP). The product page lists GitHub, Slack, Notion, Linear, Jira, Google Drive, Gmail, Sentry, and Postgres as examples, and says you can sign in once and use that connection across workflows, including any public MCP server you can sign in to. It also notes that some services only accept approved clients or do not yet have a public MCP server. Scheduled runs are available — daily, weekly, or the first Monday of the month, according to the product page. Starting a workflow from a webhook or an event in a connected tool is described there as coming soon, so we are not treating event-based triggering as generally available today. Workflows are also reachable over MCP from an agent or editor you already use.

    This is a different kind of agent product from desktop or computer-use agents. For a separate agent-tool story, we previously covered Vercel’s Agent Desktop accessibility and computer-use work. Mermaid Flow is a shared, diagram-based workflow runner, not a desktop computer-use agent.

    Plans and workflow-run limits

    The launch post says the free plan includes 15 workflow runs a month, and that Premium includes 500 shared runs a month across the organization. Mermaid’s pricing and product pages add more plan detail. A run is counted once per successful start-to-finish execution, resets monthly, and is separate from AI credits. Workflows do not count toward a plan’s diagram limit. Mermaid also says runs come bundled with every plan if you already have a Mermaid account.

    On the official pricing page, Basic is free and Plus is $10 per user per month, billed annually. Premium is $20 per user per month, billed annually. Enterprise is listed as custom, also billed annually. The product and pricing FAQs say Basic and Plus each include 15 workflow runs per user each month, while Premium includes 500 shared runs across the organization and Enterprise has a custom run allowance. The product page also says Plus includes full run history, and Premium includes a choice of model. Plus is listed with 300 AI credits per year, and Premium with 2,000 AI credits per year; the Basic plan card describes AI as limited and does not publish a clearer credit figure in the same way, so we are not inferring one.

    Key facts

    ItemWhat Mermaid says
    AnnouncementNovember 18, 2026 launch post, “Mermaid Flow: the visual builder for agentic workflows.”
    What it isA visual builder for agentic workflows: you lay steps out as a diagram and run those same steps each time.
    Where to use itAvailable now at mermaid.ai/flow. More product detail is on mermaid.ai/products/flow/.
    Workflow runs15 per user each month on Basic and Plus; 500 shared across the organization on Premium; custom on Enterprise. Failed runs do not count. Runs reset monthly and are separate from AI credits.
    PricingBasic is free. Plus is $10 per user per month, billed annually. Premium is $20 per user per month, billed annually. Enterprise is custom.
    ConnectionsOne-click sign-in over MCP, including GitHub, Slack, Notion, Linear, Jira, Google Drive, Gmail, Sentry, and Postgres, plus other public MCP servers that allow sign-in.
    AutomationScheduled runs are available. Starting a workflow from a webhook or a connected-tool event is listed as coming soon.
    Product HuntThe launch post says Mermaid Flow is also on Product Hunt today. Official pages do not publish a rank or vote count.

    FAQ

    What is Mermaid Flow?

    It is Mermaid’s visual builder for agentic workflows, launched on November 18, 2026. You design the workflow as a diagram, connect the tools it needs, and run those same steps each time, including for AI work that a team expects to repeat.

    Where can I try it?

    Mermaid says it is available now at mermaid.ai/flow. The company points to mermaid.ai/products/flow/ for a longer product overview, and to its pricing page for plan comparisons.

    How many workflow runs are included?

    Official pricing and product FAQs say Basic and Plus include 15 workflow runs per user each month, Premium includes 500 shared runs a month across the organization, and Enterprise has a custom allowance. A run is one start-to-finish execution. Failed runs do not count, and the allowance resets monthly.

    How much does Mermaid Flow cost?

    The free Basic plan includes Flow runs. Plus is $10 per user per month, billed annually, and Premium is $20 per user per month, billed annually. Enterprise pricing is custom. Mermaid’s official pages do not list a separate monthly-billed price in the material we reviewed, so we are not inferring one.

    Which starting workflows does Mermaid suggest?

    The launch post highlights four examples: triaging issues, writing a weekly recap, giving pull requests a first read, and drafting release notes. The product page also says the gallery has 39 templates. Those are Mermaid’s suggested starting points, not a claim that every team’s workflow is already built.

    Which tools can a workflow connect to?

    Mermaid says connections use MCP and lists GitHub, Slack, Notion, Linear, Jira, Google Drive, Gmail, Sentry, and Postgres as examples, along with any public MCP server you can sign in to. Some services may only accept approved clients or may not have a public MCP server yet.

    Can a workflow run on a schedule or from a webhook?

    Scheduled runs are available, including daily, weekly, or the first Monday of the month, according to the product page. Starting a workflow from a webhook or an event in a connected tool is listed as coming soon, so it should not be treated as generally available today.

    Do I need to know Mermaid syntax to use Flow?

    The product FAQ says no. You can describe what you want in plain language, or bring a document, a flowchart, or a skill file you already have. The syntax is there if you want it, but Mermaid does not present it as a requirement.