We build a Make (formerly Integromat) scenario to a spec you supply, using Make’s visual automation builder to connect the apps and logic you’ve specified — implementation of an automation you’ve already planned, not a decision about what that automation should do.
Make (Integromat) scenario build
A Make scenario built exactly to your spec, using Make's own visual automation builder.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- A clear spec of the desired scenario: trigger, modules, and any routing or filtering logic between steps
- A Make account, with access granted to us for building the scenario
- Confirmation of which app accounts (already connected, or needing connection) are involved
This or something else?
| You have a specific Make scenario spec ready to build | This fix covers it |
| You want a Zapier zap instead of a Make scenario | Zapier scenario build from supplied spec, the equivalent for that platform |
| You need help designing the automation’s logic, not just building a spec you’ve already planned | Worth discussing directly — we can share technical feasibility observations, though the business logic decision is yours |
| An existing scenario has stopped working, not a new build | Worth describing the specific failure directly — likely a targeted repair rather than a fresh build |
What we do
- Review the supplied spec for technical feasibility within Make’s capabilities
- Confirm or connect the required app accounts
- Build the scenario exactly to the specified trigger, modules, and logic
- Test with a real trigger event to confirm correct behaviour end to end
- Verify data flows accurately through every step and connected app
- Document the scenario’s configuration for future reference
What is included
- A Make scenario built exactly to your supplied spec
- Verified, tested behaviour with a real trigger event
- Accurate data flow confirmed through every step
- A written note on the configuration
Not included
- Designing the automation’s business logic — that’s your decision, we implement a spec you’ve already planned
- Paying for or upgrading Make plan tiers needed for the scenario’s operation volume
- Resolving an outage or bug on Make’s or a connected app’s own platform
- Ongoing maintenance as connected apps change their own APIs over time
Questions about this fix
How is Make different from Zapier for this kind of work?
Make's visual builder handles more complex branching and routing logic more naturally than Zapier's more linear structure — which platform fits better depends on your specific automation's complexity, though we can build on either given a clear spec.
Can you help me figure out what my scenario should actually do?
We can share technical feasibility observations on what Make can and can't do, but the actual business logic decision — what should trigger what — stays with you; this fix implements a spec you've already planned.
What if my scenario needs a Make plan tier I don't currently have?
We'd tell you plainly if the scenario's operation volume or connected apps require a specific plan tier — upgrading is your decision with Make directly.
Will this scenario keep working indefinitely without attention?
Depends on whether connected apps change their own APIs over time — a scenario working correctly today can need adjustment if a connected service changes how it works, an inherent, ongoing characteristic of third-party integrations.
Can this scenario include conditional routing based on data values?
Yes, if your spec includes that logic, Make's builder supports this kind of branching, and we'd implement it exactly as specified.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.