Make.com automation expert

Make (the platform once called Integromat) is a visual automation tool. You build a scenario on a canvas, one module at a time, and it passes data between the apps your business already runs on: your website forms, CRM, accounting software, shop and spreadsheets. This page is for UK businesses that have picked Make, are deciding whether to, or have inherited scenarios that fail without anyone noticing. I design, build and document Make scenarios, and everything I build lives in your own account.

What Make does well

Make earns its place when a process has more than one path. A router can send the same record down several branches, each with its own filter, so a new enquiry can go to sales, to the email list and to a reporting sheet in one run. Iterators and aggregators handle lists properly, which matters for things like order line items or a batch of invoices.

It also reaches well beyond its list of ready-made app modules. The HTTP module can call almost any API, and a custom webhook lets a website form or another system push data into a scenario the moment something happens. When a supplier has an API but no Make app, that is rarely a dead end.

The run history is the other strength. Every execution is logged, and you can open each module to see exactly what data went in and what came out. When a lead goes missing, that turns an afternoon of guessing into a few minutes of reading.

Where Make is weaker

• Polling costs add up. A trigger that checks an app for new records uses part of your allowance on every check, even when nothing has arrived. A scenario polling every five minutes runs 288 times a day before it has done any work.
• Big scenarios get hard to read. The canvas is pleasant at ten modules and confusing at sixty. Without naming conventions and notes, the next person to open it has to reverse-engineer it.
• It is hosted only. You cannot run Make on your own servers. Data passes through Make’s infrastructure, in the hosting region chosen when your organisation was set up.
• Mapping takes some getting used to. Staff who are comfortable with a simple step-by-step editor often find arrays, bundles and field mapping in Make harder to maintain without help.

What I build on Make

When I would recommend something else

Make is not always the right answer, and I would rather say so before you pay for it. The trade-offs are covered in more depth in the glossary entry on Zapier and Make, but in short:

• For a handful of simple two-step automations that a non-technical team will maintain alone, Zapier is usually easier to live with.
• If data must stay on servers you control, or volumes are high enough that usage pricing hurts, self-hosted n8n is worth comparing.
• If the whole process happens inside Google Workspace, Apps Script may do it with no extra subscription.
• If both ends of the process sit in one platform, such as HubSpot or Klaviyo, its own built-in workflows are simpler and cheaper to keep running.
• If the process itself is still changing every week, it is too early to automate. Settle it by hand first.

How a build runs

1. Map the process. We talk it through, then I write it down step by step: what starts it, which apps are involved, who acts at each point and what should happen when something fails.
2. Set up access properly. The Make organisation is in your name and on your billing, and I join as a member. App connections are authorised with shared business accounts where possible, not someone’s personal login.
3. Build and test on sample data. I build in a copy, then run it with awkward real-world records: blank fields, duplicate contacts, phone numbers written as 07 and +44, postcodes with and without spaces.
4. Add error handling. Each scenario gets error routes, an alert to an inbox or chat channel you watch, and stored incomplete executions so a failed run can be fixed and replayed instead of lost.
5. Go live and watch. For a period we agree before work starts, I check the run history after launch and tune schedules and filters.
6. Hand over. A walkthrough with whoever will own it, plus the written documentation below.

Problems I see most often in inherited Make accounts

• Scenarios sitting in a former freelancer’s personal account, so the business does not actually own them.
• No error handling at all. Failures go unnoticed, and depending on its settings Make can stop scheduling a scenario after repeated errors.
• Polling triggers set to run every few minutes on processes that need checking once an hour, quietly using up the plan.
• Connections authorised by someone who has since left, which break the day their account is closed.
• Customer details copied into data stores and Google Sheets and kept indefinitely. Under UK GDPR you should hold only what the process needs, for as long as it needs it; data minimisation applies to automations as much as to forms.
• Modules left with default names, so nobody can tell what “HTTP 4” does without opening it.

What you receive

• Working scenarios in your own Make organisation, consistently named, with a note on every module that is not obvious.
• Exported blueprints of each scenario, stored with you as a backup.
• A short runbook for each scenario: what triggers it, what it changes, where errors are reported, how to pause it and how to replay a failed run.
• A list of the personal data each scenario touches and where it ends up, for your own records. Make processes that data on your behalf, so its data processing agreement and hosting region belong in the same file.

Pricing

There are two separate costs. The first is your Make subscription, which you pay to Make directly. Make prices by usage: each module action in each run draws on a monthly allowance, so the bill depends on how many steps your scenarios have and how often they run. Plan names, prices and allowances change, so check Make’s current price list before you choose. Before you commit, I estimate the monthly usage of the scenarios we plan, so the plan you choose fits.

The second is my fee for the build. I write each quote in GBP after a free first call, once I know which scenarios are needed, and we agree it in writing before work starts, along with any support after launch. I do not resell Make, add a margin to your subscription or hold your account on my side. If we stop working together, you keep everything and I remove my access.