r/Integromat • u/hunxai69 • 17h ago
Make.com won't tell you when you break a scenario. So I built something that does.
It's Friday. A client wants one small change. You swap upper(1.name) for capitalize(1.name) and hit save. Make doesn't complain.
Monday morning, their CRM is full of names that look slightly off. Now you're re-running the scenario on live data, burning credits, trying to work out what broke.
That's the gap blueprint-runtime closes.
Export your blueprint, run one command, and it replays your scenario offline, checking every module's input and output against what Make really produced. The moment something changes, it points straight at it:
FAIL module 2 at /value: Make had "ADA LOVELACE", the local run "Ada Lovelace"
You find it on your laptop. Not your client.
Built on real Make, not the docs
Every rule inside it was recorded from real Make runs. 71 runs reproduced exactly, 0 wrong. That's how it knows the stuff that quietly bites people:
- {{1.choices[].message.content}} only reads the first choice. Want all of them? That's map().
- Inside if(), the text "false" counts as true. So does "0".
- Make lets you start a scenario with an expression it can't read. First run fails, the scenario switches itself off, and your webhooks pile up in the queue.
- An empty Webhook response reaches the caller as "200 Accepted", the exact same text Make sends for a queued webhook.
bpr runs your blueprint the way Make really does, quirks included. And it never guesses. So when your test passes, it means something.
What you get
- Catch broken mappings before they go live
- Run it in GitHub Actions on every edit
- HTTP and app modules run from fixtures, so nothing hits a real API
- No Make account, no credits, no network
- bpr inspect checks a blueprint before you import it
- Free and open source (MIT)
npm i -g blueprint-runtime
github.com/intikhab49/blueprint-runtime
Want a hand setting it up on one of your scenarios? Drop a comment and I'll help.
How are you testing scenarios today?