The scenario that nobody can explain
Picture this: you built a Make.com scenario six months ago. It watches for new orders, pulls the customer data, creates a row in Google Sheets, sends a Slack message to your team, and fires off a confirmation email. It runs every day without you touching it. You love it.
Then a client asks you: "Can you walk me through how this works?"
You open Make, stare at the canvas full of modules and arrows, and realize you'd need ten minutes just to remember what each module is doing. If you're a freelancer handing off a finished project, that's not a great look. If you're on a team and someone else needs to maintain the scenario, it's an even bigger problem.
Documentation is one of those things everyone agrees is important and almost nobody actually does. It takes time, it's boring, and when you're in the flow of building something, stopping to write a doc feels like the last thing you want to do.
That's exactly why we built the Scenario Documenter.
What the Scenario Documenter actually does
The tool takes your Make.com blueprint file (a JSON file you export straight from Make) and turns it into a clean, readable document. Not a wall of raw JSON. A proper document with section headers, a list of apps used, a numbered breakdown of every module in the flow, and the settings your scenario is running on.
You get two things out of it. First, an on-screen document you can read right there in the browser. Second, a downloadable Markdown file you can save, share as a Google Doc, paste into Notion, attach to a client handoff, or drop into a GitHub repo.
The whole thing runs in your browser. Your blueprint data never touches a server. You're not uploading anything to a third party. You paste or drop the file, click a button, and the document is ready.
How to use it (step by step)
It takes about 30 seconds. Here's the full process.
Export your blueprint from Make.com
Open your scenario in Make. Click the three dots (...) in the bottom toolbar, then select Export Blueprint. Make will download a .json file to your computer. That's your blueprint.
Drop the file (or paste the contents)
Go to the Scenario Documenter and drag your blueprint file directly onto the input area. You can also click "Browse file" to pick it from your computer, or open the file, copy everything, and paste it in. All three options work the same way.
Click Generate Document
Hit the orange button. The tool parses the blueprint and builds the document instantly. If you used the drag-and-drop or file browser, it even skips the button click and generates it automatically.
Copy or download the result
You'll see the full document on screen. From there you can copy the raw Markdown with one click, or download it as a .md file. Paste it into Notion, Google Docs, a README, a client email, wherever you need it.
What's actually in the document
We thought carefully about what someone reading the document actually needs to know. Here's what gets included.
Scenario name and trigger type
Whether your scenario runs on a schedule or fires instantly via webhook.
Quick stats
Total number of modules, how many different apps are connected, the max error count, and whether sequential execution is on.
Apps used
A clean list of every app your scenario connects to: Google Sheets, Slack, Gmail, Airtable, whatever you have. If an app appears more than once, it shows a count.
Module flow
Every module listed in order, numbered, with the app it belongs to and whether it's the trigger, an action, a router, an iterator, or an aggregator. Router branches are shown as sub-lists so the branching logic is clear.
Settings
Max errors, sequential execution, auto-commit, data loss protection, and confidential mode. The stuff that affects how your scenario behaves when things go wrong.
Who actually needs this
Freelancers and agencies
When you deliver a finished automation to a client, a document showing exactly what you built is part of a professional handoff. It answers the questions before the client even asks them.
Teams
If you work with other people, the person who didn't build the scenario shouldn't have to reverse-engineer it to understand it. A doc makes collaboration and maintenance a lot less painful.
Solo builders
Even if it's just you, you will forget. Six months from now when something breaks at 2am, you'll want a plain-language explanation of what this scenario is supposed to do.
A few things people ask
Does it show the actual data inside my modules? Filters, field mappings, that kind of thing?
Not right now. The Scenario Documenter focuses on structure: which apps are connected, in what order, and how the flow branches. The actual field mappings inside each module can contain sensitive information (API keys, column references, customer data), so we leave those out by default. We're thinking about how to handle that well in a future version.
What happens if my scenario is really large?
It handles large blueprints fine. Even a "simple" Make scenario can export as a 2,000+ line JSON file because the format includes a lot of editor metadata (x/y positions, column specs, interface definitions). The tool ignores all of that and only reads the parts that matter. Parsing is instant regardless of file size.
Is my data safe?
Yes. Everything runs in your browser. Your blueprint is never sent to any server. There's no account, no login, no data stored anywhere. You paste your file, your browser processes it, and that's it.
Is it free?
Completely free. No limits on how many scenarios you document.
Try it on one of your own scenarios
Export any blueprint from Make.com, drop it in, and see what the document looks like. Takes less than a minute.
Open Scenario Documenter