Dependency Mapper
Upload your Make.com blueprints and see how your scenarios connect. Find out which scenarios would break if you changed or deleted one.
Everything runs in your browser. Your blueprint data never leaves your device.
What is the Dependency Mapper?
In a large Make.com workspace, scenarios often trigger each other via webhooks. When you have dozens of scenarios, it becomes impossible to know which ones depend on which without mapping it out. The Dependency Mapper reads your blueprint files and draws the connections so you can see the full picture before making changes. Runs entirely in your browser, no account needed.
How to use the Dependency Mapper
- 1Export blueprints from the Make.com scenarios you want to map using the three-dot menu.
- 2Upload them using the file picker in the tool above.
- 3Optionally add the webhook URLs your scenarios use to call each other for more accurate matching.
- 4View the dependency graph and identify which scenarios would break if one was changed or deleted.
Frequently asked questions
How does it detect dependencies between scenarios?
It looks for HTTP and Webhook modules in your blueprints and matches their target URLs to the webhook URLs of other scenarios you have uploaded.
Do I need to upload all my scenarios?
No. You can start with a subset. Scenarios that call URLs not matched to an uploaded blueprint will show as unresolved dependencies in the graph.
Is my data sent to a server?
No. Everything runs in your browser. Your blueprint files never leave your device.
Can I export the dependency map?
You can take a screenshot of the graph. Downloadable exports are on the roadmap.
Related reading
How to Map Dependencies Between Make.com Scenarios
Why cross-scenario dependencies are a hidden risk and how to visualize them before they cause outages.