Make automation
Scenarios that connect your tools, with no server to run
We build Make scenarios in your own account for the work that sits between your tools: enquiries into the CRM, orders into the warehouse, documents into the right folder. Each one is tested, documented and handed over.
Make · new lead
- Web formLead sent
- MakeRouter
- HubSpotContact created
- Google SheetsRow added
- LargeTask for a salesperson
- SmallSend the catalogue
What it is
A visual automation tool that runs in the cloud
Make, formerly Integromat, connects apps through scenarios: a trigger followed by modules that read, change and send data. It has ready-made modules for a very large number of apps, runs entirely in the cloud and shows every run step by step, which makes it easy to see what happened. We choose it when the process is clear, the apps are common and you would rather not run a server.
- Routers and filters send each case down the right branch
- Iterators and aggregators handle lists such as order lines
- Error handlers decide what happens when a module fails
- Data stores keep small amounts of state between runs
Scenario history · sample data
- Enquiry to CRMSuccess · 5 modulesActive
- Signed quote to folderSuccess · 4 modulesActive
- Enquiry to CRMSuccess · 5 modulesActive
- Overdue invoice reminderWaiting for approvalActive
What we deliver
Scenarios that hold up on real data
Scenario design
The process drawn first, with its exceptions, so the scenario covers what really happens and not only the usual case.
Build and mapping
Modules, routers and field mapping built in your account and tested with examples taken from your own data.
Error handling
Handlers that retry, skip or stop on purpose, and a notification to a person when a run needs attention.
Efficient runs
Scenarios built to use as few operations as the job needs, so usage stays predictable as volume grows.
Approval points
A step where a person confirms before an email goes to a customer or a record is changed in the books.
Documentation
A short description of each scenario: what triggers it, what it touches and how to pause it.
How a project runs
Small, tested, then switched on
- 01
Map the process
We go through one real case with the person who does the work today and note every step and exception.
- 02
Build in your account
The scenario is built with its connections under your logins, so nothing depends on an account of ours.
- 03
Test on real cases
We run it on recent examples and compare the result with what was done by hand.
- 04
Switch on and watch
The scenario goes live. We check the run history in the first weeks and adjust what real data shows up.
What Make connects to
- Make building blocks
- Webhooks, Routers, Filters, Iterators and aggregators, Data stores, Error handlers
- Commonly connected
- Google Workspace, Microsoft 365, Pipedrive, HubSpot, Shopify, WooCommerce, Slack, Airtable
- When there is no module
- HTTP module, Custom webhooks, A small service we write
We start from what you already have. The list shows what we reach for when something is missing, not tools you must adopt.
Is Make the right tool?
A good fit when…
- The apps you use are common and already have Make modules
- You want something running soon, with no server to maintain
- Someone on your team would like to read and adjust scenarios
- Volumes are moderate and the logic is mostly straightforward
Probably not for you when…
- Data must not leave infrastructure you control
- Workflows run so often that usage-based billing becomes the main cost
- The logic needs a lot of custom code
- The process depends on a system with no API at all
Use cases
What we build in Make
Each of these can start as a single scenario.
Every enquiry in the CRM, without retyping
Enquiries from forms, email and chat become contacts and deals in your CRM, with the right person notified.
Open use case SalesBusiness automationCRM implementationQuotes drafted from your price list
A quote is drafted from the deal, your price list and current stock, and waits for a salesperson to approve it.
Open use case SalesCRM implementationBusiness automationNo open quote left without a follow-up
The CRM reminds the owner, drafts the follow-up and shows which deals have gone quiet.
Open use case SalesCRM implementationBusiness automationA sales report nobody has to build
Pipeline, won and lost deals and activity, delivered on a schedule straight from the CRM.
Open use case Finance and adminAI integrationsBusiness automationSupplier invoices read, matched and ready to post
Incoming invoices are read, matched to purchase orders and sent for approval before they reach the books.
Open use case Finance and adminAI integrationsBusiness automationData out of documents, into your systems
Contracts, forms, delivery notes and statements are read and their data placed where it is needed.
Open use case Finance and adminBusiness automationERP and business systemsOverdue invoices chased politely and on time
Reminders go out on a schedule from your open invoices, and the awkward cases go to a person.
Open use case Finance and adminBusiness automationAI integrationsThe monthly report, assembled for you
Figures from accounting, sales and operations pulled into one report on a schedule, with a written summary.
Open use case Customer supportAI integrationsBusiness automationA support inbox that sorts itself
Incoming messages are sorted by topic and urgency, routed to the right person and given a draft reply.
Open use case Customer supportBusiness automationAI integrationsCustomers check their order without writing to you
Order and delivery status available on your site or by reply, pulled live from the shop and the courier.
Open use case OperationsBusiness automationERP and business systemsOrders that reach the warehouse on their own
An order placed in the shop or by email appears in the ERP, on the pick list and with the courier, entered once.
Open use case OperationsERP and business systemsBusiness automationOne stock figure in every system
Stock levels kept in step between the warehouse, the ERP and every sales channel.
Open use case OperationsBusiness automationCustom softwareNew colleagues ready on day one
Accounts, equipment, documents and first-week tasks set in motion from one form.
Open use caseQuestions about Make
Make or n8n: which should we use?
Make is the quicker start: no server, many ready-made modules and a clear visual history. n8n is the better choice when workflows run very often, need custom code or must run on your own infrastructure. We build in both and say which one fits after seeing the process.
Whose account do the scenarios run in?
Yours. You hold the Make subscription and the connections use your logins. We work in it as an invited user and you can remove us at any time.
Where is our data processed?
Make is a cloud service, so data passes through its servers while a scenario runs. When you create the account you choose the region it is hosted in. If that is not acceptable for a particular process, we build that one in a self-hosted tool instead.
We already have scenarios that someone built. Can you take them over?
Yes. We start by reading what is there, note what each scenario does and where it fails, and then fix or rebuild the ones that cause trouble. Working scenarios are left alone.
How do we know when something breaks?
Each scenario has error handling and a notification to a named person. We also agree which failures should stop the scenario and which should be skipped and reported.
What if we outgrow Make?
Because the process is documented, moving a scenario to n8n or to custom code is a rebuild of known steps, not a rediscovery. We tell you when we think that point has come.
Show us one process. We will show you what it could look like.
The analysis is free, takes about an hour of your time, and ends with a written summary you keep.
Prefer to read first? See examples