FlowRunner
Features Pricing
Theme
Start Free

How to migrate from Make to FlowRunner

Migrate your Make scenarios to FlowRunner one at a time: export each blueprint, let FlowRunner Prompt to Flow build the flow, then reconnect accounts and set the schedule.

2026-11-02 Updated November 3, 2026 8 min

This guide migrates your Make scenarios to FlowRunner without rebuilding each one by hand. FlowRunner Prompt to Flow connects to the AI tool you already use, reads a scenario’s exported blueprint, and builds the same workflow as a FlowRunner flow in your workspace.

You convert one scenario at a time. What’s left for you is reconnecting your accounts, setting the schedule, and testing.

1. Export your scenarios from Make

Make exports one scenario per file, as a JSON blueprint:

  1. Go to Scenarios and open the scenario.
  2. Click the three dots in the upper right of the Scenario Builder.
  3. Choose Export blueprint. Make downloads a .json file named after the scenario.

Copy blueprint to clipboard in the same menu gives you the same JSON as text, which you can paste straight into the chat. Make’s help page names no plan limit for either.

According to Make, a blueprint holds the scenario’s modules, their settings, and the values you mapped between them. Two things don’t come with it: your connections, and the scenario’s schedule. Make’s help page doesn’t say whether webhooks, data stores, data structures, or scenario settings are included, so plan as if they aren’t.

Before you leave each scenario:

  • Write down the schedule, or note which webhook or app starts it.
  • Note any data stores the scenario reads or writes, and copy out their records if you need them.
  • Save a few real inputs from the scenario’s recent runs, so you have something to test the new flow with.

Keep the blueprints, too. Make’s own import takes blueprints under 2 MB, so the files are a backup you can bring back into Make.

If you have a lot of scenarios, Make’s API returns any scenario’s blueprint (GET /scenarios/{scenarioId}/blueprint, with an API token), so a short script can save them all.

2. Connect FlowRunner Prompt to Flow to your AI tool

FlowRunner Prompt to Flow is an MCP server you add to the AI tool you already use. You connect it once and sign in with your FlowRunner account. The server URL is the same for every tool: https://app.flowrunner.ai/mcp.

Claude (web and desktop)

  1. In Claude, open Settings > Connectors.
  2. Click + Add, then Add custom connector.
  3. Enter FlowRunner as the name and https://app.flowrunner.ai/mcp as the server URL. If Claude offers sign-in choices, pick Sign in now and Register automatically, and leave the client ID and secret empty.
  4. Click Add, then Connect, and approve the FlowRunner sign-in page that opens.
  5. In a chat, click + > Connectors and check that FlowRunner is on.

On Claude's Team or Enterprise plan, an Owner adds FlowRunner once for everyone under Organization settings > Connectors, with the same URL. Each member then finds it under Settings > Connectors and clicks Connect.

Claude Code

  1. In your project folder, add the server. Add --scope user to use it in every project.

    claude mcp add --transport http flowrunner https://app.flowrunner.ai/mcp
  2. Sign in, and approve the FlowRunner sign-in page that opens in your browser.

    claude mcp login flowrunner
  3. Check the connection with claude mcp list. The flowrunner line ends in ✔ Connected.

ChatGPT

  1. On the web, open ChatGPT Plugins. ChatGPT connects to MCP servers on chatgpt.com only.
  2. Click Add, then Add custom MCP server.
  3. Enter FlowRunner as the name and, under Connection, https://app.flowrunner.ai/mcp as the server URL.
  4. Choose OAuth, select I understand and want to continue, then Create as a plugin.
  5. Install the plugin and approve the FlowRunner sign-in page.
  6. In a chat, type @ and pick FlowRunner.

Whether you can add a custom MCP server depends on your ChatGPT plan and, in a Business, Enterprise or Edu workspace, on your admin's settings.

Codex

  1. Add these lines to ~/.codex/config.toml, creating the file if it doesn't exist.

    [mcp_servers.flowrunner]
    url = "https://app.flowrunner.ai/mcp"
  2. Sign in, and approve the FlowRunner sign-in page that opens in your browser.

    codex mcp login flowrunner
  3. Check the connection with codex mcp list. The flowrunner row shows OAuth in the Auth column.

Cursor

  1. Create ~/.cursor/mcp.json to use FlowRunner in every project, or .cursor/mcp.json in a project folder for that project only. If the file already exists, add the flowrunner entry inside its mcpServers.

    {
      "mcpServers": {
        "flowrunner": { "url": "https://app.flowrunner.ai/mcp" }
      }
    }
  2. Open Customize in the sidebar, then MCPs, and follow the sign-in prompt for flowrunner.

VS Code (GitHub Copilot)

  1. Open the Command Palette, run MCP: Add Server, choose HTTP, enter https://app.flowrunner.ai/mcp, and name it flowrunner.
  2. Open Copilot Chat in agent mode and ask "List my FlowRunner workspaces". The first time, VS Code asks you to sign in: allow it and approve the FlowRunner sign-in page.
  3. Copilot lists your workspaces. FlowRunner is connected.

On the FlowRunner sign-in page, check the account under Logged in as, tick I recognize and trust this URL, and click Authorize. If you don't have a FlowRunner account yet, the Free plan needs no card, and every new account starts with 14 days of Professional. The setup guide in the docs has every tool step by step.

3. Convert one scenario at a time

Start a new chat, paste this request, then paste one blueprint after it:

Rebuild this Make scenario as a FlowRunner flow. It’s a blueprint from Make’s Export blueprint: the JSON lists the modules in order with their settings and mapped values, plus any routers, filters, and error handlers. It doesn’t include connections or the schedule. Keep the same behavior. Make runs each module once per bundle, so where a module received several bundles, use a loop over the list. Before you build, tell me anything you can’t map one to one, and ask me about anything the file doesn’t say.

Then add a line or two about what the blueprint can’t carry:

  • how the scenario starts: its schedule, or the app or form that calls its webhook
  • which data stores it uses and what they hold
  • who approves, and on which channel, if a person signs off anywhere in the scenario

Answer its questions, and it builds the flow in your workspace. Make’s own tool modules (Set variable, Iterator, Aggregator, Sleep) become FlowRunner’s built-in blocks, and error handlers become error paths you can see on the canvas. One scenario per chat keeps the questions specific.

4. Finish what the blueprint can’t carry

Each conversion ends with a short list from the AI. Expect some of these:

  • Connect your accounts. Each one is connected once and shared across your flows. The AI tells you which ones the flow needs.
  • Add keys and secrets. API keys from an HTTP module’s headers, for example. Save each one in API Keys, and the flow reads it through a placeholder. The AI tells you which ones the flow needs.
  • Set the schedule. Use the clock icon in the flow editor, or ask the AI to set it.
  • Note the new address. Every app or form that posts to a Make custom webhook will need the flow’s External Callback URL when you switch over in step 5.
  • Move data store records. Values a single flow keeps between runs fit in its Shared Memory. A table several flows share belongs in a spreadsheet or database the flows connect to.
  • Set up approvals. If a person signs off by webhook, Slack, or email today, the AI builds that as a human-in-the-loop step. Tell it who reviews and on which channel: email, Slack, WhatsApp, phone, or a Form.
  • Add forms and agent tools in the editor. FlowRunner Prompt to Flow can’t create a Form yet, or attach a flow to an AI agent as its tool. If the scenario needs either, the AI tells you which to add in the flow editor.
  • Start the flow, if the AI left it stopped.

5. Test, then switch over

Run each flow with the inputs you saved in step 1 and compare the results with what the scenario produced. With FlowRunner Prompt to Flow connected you can ask your AI tool to do it, for example “Run my Order sync flow with this order.” A test run is a real run and counts as an execution.

When the results match, point the webhook callers at the flow’s new address, turn the scenario’s schedule off in Make, and watch the flow’s runs for a few days before you delete anything.

How Make maps to FlowRunner

Migration map from a Make scenario to a FlowRunner flow: triggers, actions, filters, and routers carry over; Make's error directives and Incomplete Executions map to Handle Error and Repeat plus Wait, and a native Human Review Flow is added. The logic carries over; the execution model changes.

MakeFlowRunnerWhat changes
ScenarioFlowA flow can start with any block, not only a trigger.
ModuleBlockOne run is one execution, however many blocks run.
ScheduleFlow scheduleOnce, every X seconds, daily, weekly, monthly, or cron.
Custom webhookExternal CallbackNew URL. The same block can also resume a paused run.
FilterConditionThe No branch can do something instead of only stopping.
RouterValue Router or ConditionWhere several routes ran for the same bundle, the AI asks how to lay them out.
IteratorList IteratorThe steps for each item sit inside the loop.
AggregatorA variable collected in the loop with Transform DataAdd To List builds the result one item at a time.
Set variableSet VariablesSame idea, for the run.
Data storeShared MemoryBelongs to one flow; shared tables go to a database or sheet.
SleepWaitA run waits up to 30 days on Free, Starter, and Growth, and up to a year on Professional and up.
HTTP moduleHTTP RequestA Retry Policy per request.
Error handlers and Incomplete ExecutionsHandle Error, plus Repeat and WaitFailures get their own path on the canvas.
ConnectionsOAuth ConnectionsConnect each account once for the whole workspace.

Quick wins on day one

These are the differences you see as soon as the first scenario runs on FlowRunner. Each is covered in FlowRunner vs Make.

  • One execution per run. A 3-module scenario over 10 items is roughly 31 Make credits. On FlowRunner the whole run is one execution.
  • Longer waits. A Make run stops at 40 minutes on paid plans, and Sleep tops out at 5 minutes. A FlowRunner run waits up to 30 days on Free, Starter, and Growth, and up to a year on Professional and above.
  • Approvals on every plan. Make’s Human in the Loop app is on the Enterprise plan only and in closed beta. FlowRunner has human-in-the-loop on every plan, including Free, and the reviewer answers by email, Slack, WhatsApp, phone, or a Form.
  • Compliance on published plans. Make signs no BAA on any plan and keeps audit and RBAC on its Enterprise plan. FlowRunner has audit trails and RBAC from Professional ($299 a month) and signs a BAA on Business ($999 a month) and up.

Want a hand with a bigger migration? Contact us.

Frequently asked questions

How do I export a scenario from Make?

Open the scenario, click the three dots in the upper right of the Scenario Builder, and choose Export blueprint. Make downloads a JSON file named after the scenario. Copy blueprint to clipboard in the same menu gives you the same JSON as text.

Can I export all my Make scenarios at once?

Not from the Make interface; it exports one scenario per file. If you have many, Make's API returns any scenario's blueprint with an API token, so a short script can save them all.

Does FlowRunner import Make blueprints directly?

There is no upload button for them. You paste the blueprint into the AI tool you use, with FlowRunner Prompt to Flow connected, and the AI reads it and builds the same flow in your FlowRunner workspace, one scenario at a time. It asks about anything it can't map one to one before it builds.

Do my connections and schedules come over?

No. Make's own help says to create connections again after importing a blueprint and to schedule the scenario again. In FlowRunner you connect each account once and every flow in the workspace can use it, and you set the flow's schedule in the flow editor or ask the AI to set it.

What happens to Make's error handlers?

Each one becomes an error path on the canvas with FlowRunner's Handle Error block, and a retry becomes a Repeat and Wait loop. The AI asks what should happen where the scenario used Rollback, Commit, or Break, because those depend on the modules involved.

How many executions will a converted scenario use?

One per run. FlowRunner counts one complete run as one execution, however many modules it had and however many items it processes, so a 3-module scenario over 10 items that used roughly 31 credits on Make is one execution.

Editorial policy

Ready to try it?

Start on the Free plan. No card required, and every new account gets 14 days of Professional.