Make
Make integration
Make (formerly Integromat) is the visual automation layer we use when Shopify Flow runs out of road: multi-step logic, external APIs and data transforms.
UPDATED OCT 2026 · SOURCES (5)
MAKE INTEGRATION AT A GLANCE
COMPLEXITY
Medium
METHOD
TYPICAL SETUP
3–5 days
WHAT WE DO
Map the workflow, build scenarios with error handling and retries, add logging to Slack or a sheet, and hand over documentation your team can maintain.
CATEGORY
Automation
SETUP BY PLATFORM
How we set up Make
Shopify
Make on Shopify (Native app): Map the workflow, build scenarios with error handling and retries, add logging to Slack or a sheet, and hand over documentation your team can maintain.
Shopify store builds →Shopify Plus
On Shopify Plus (Native + Flow): everything in Shopify, plus the Plus-only hooks (checkout extensions, B2B, Launchpad) where Make can use them.
Hydrogen
On a headless storefront (Hydrogen, Astro or Next.js) we connect Make through Webhooks and own the event and data mapping ourselves.
USE CASES
What teams use it for
Order routing
Route orders to 3PLs, suppliers or spreadsheets by SKU, region or tag.
Data sync
Keep products, inventory and customers in step with an ERP or sheet.
Alerts
Slack alerts for failed payments, low stock and VIP orders.
BEFORE YOU ADD IT
What to watch out for
ERRORS
Scenarios fail silently
Without error handlers a failed run just stops. We add retries and alerts.
COST
Operations add up
Make bills per operation. Polling every minute burns the plan.
OWNERSHIP
Document the scenarios
Automations outlive the person who built them. We document every one.
05
Make on Shopify, in practice
Make (formerly Integromat) is the automation layer we reach for when a store needs two systems to talk and no app exists: ERP order sync, custom fulfilment rules, supplier feeds, B2B approvals, or anything with branching logic Shopify Flow cannot express.
Shopify Flow covers the simple cases inside Shopify — tag a customer, hold a risky order, notify on low stock — and should be used first because it is free and native. Make takes over when the data has to leave Shopify or come from outside: writing orders to an accounting system, pulling inventory from a warehouse, creating Salesforce or HubSpot records, generating documents, or chaining several apps with conditions and retries.
We build scenarios with error handling, idempotency keys so a retry does not create a duplicate order, and alerts to Slack when a run fails. Every scenario is documented with the field map and owned by the client's account, not ours. The usual mistake is a scenario built in an afternoon that runs for two years without anyone knowing what it does; the documentation is the cure.
Make or Zapier for Shopify?
We start with Shopify Flow for simple in-store cases. We use Make when data has to leave Shopify or the logic needs branching, retries and error handling. It bills per operation, so we avoid polling every minute.
Can Make replace Shopify Flow?
No. Flow is native and covers simple cases such as tagging a customer, holding a risky order or low-stock alerts, so use it first. Make takes over when data has to leave Shopify or logic needs branching and retries.
How do we handle failed runs?
Without error handlers a failed run just stops. We build retries, idempotency keys so a retry does not create a duplicate order, and Slack alerts when a run fails.
Who maintains the scenarios?
Every scenario is documented with its field map and owned by your account, not ours. Automations outlive the person who built them, so that documentation is how your team maintains them.
You've reached the end, so now…
Tell us what you're selling.
Send us your store. Within one business day you get a short Loom from a senior: the three things we'd fix first, what it would cost, and whether we're the right team for it.
- No pitch deck, no discovery-call theatre
- You keep the audit whether or not you hire us
- Fixed-scope quotes, no hourly surprises
Prefer to talk? Book 20 minutes with Haniel or call +1 855-764-4977