Holded Make (Integromat) integration
Make connected to Holded to automate processes without fragile code or odd dependencies.
Implementation time · 5-10 días laborables
The problem
Make is great for prototyping automations, but when the use case grows (more than 1,000 operations per month, pagination of large lists, serious error handling), native scenarios become fragile. Non-technical teams build them, they work for a few weeks, and one day they break with no alert, and nobody notices until the client complains. Our approach: we keep Make as the automation engine (fast, visual, accessible to the team), but the critical calls to Holded go through our integration layer with a queue, dedupe and retries.
ProposalThe solution
Make (formerly Integromat) is the most widely used low-code platform in Europe for connecting SaaS tools without custom development. But the native Make and Holded connectors are basic: only simple CRUD, no webhooks, no serious pagination, no error handling. We build the layer between the two so your Make scenarios are robust: correct pagination, dedupe, error handling, alerts. You keep the speed of Make with the reliability of custom development.
What we automate
- Custom Holded and Make connector with correct pagination of long lists
- Holded webhooks that trigger Make without polling
- Automatic dedupe to avoid duplicates on retries
- Retries with exponential backoff on critical calls
- Alerts when scenarios fail (Slack, email, SMS)
- Structured logs of every operation for auditing
- Tested Make templates for typical cases (contact sync, invoicing, products)
- Documentation of each scenario so the team can maintain it
Real use cases
These are the profiles that most ask us for the Holded ↔ Make (Integromat) integration and what they get in the end.
Company with 20+ active Make scenarios
Before: Scenarios breaking weekly with no alert.
After: Reliable middleware. Robust scenarios with Slack alerts when something fails.
SMB with low-code marketing building flows
Before: The marketing team built scenarios but the tech team had to rescue them every week.
After: Marketing keeps building flows. The tech team only steps in on structural changes.
Company wants to leave Zapier over cost
Before: Zapier cost them 80 euros a month and they wanted to move to Make.
After: Migration to Make with robust scenarios. Monthly cost drops 60-70%.
What changes exactly
Without the integration
- Fragile Make scenarios that break with no warning
- Tech team firefighting every week
- Duplicates in Holded from uncontrolled retries
- Large lists not paginated, so data is lost
With the integration
- Robust scenarios with reliable middleware
- Alerts when something fails (not days later)
- Idempotency and automatic dedupe
- Correct pagination with no data loss
How we build it
Middleware layer: your Make scenarios call our middleware (BullMQ plus Node), which calls Holded with the robustness required. Make stays as the visual orchestration engine. Our middleware acts as the reliable execution layer. The best of both: the non-technical team maintains the scenarios; critical operations do not break.
Frequently asked questions
Why not use the native Make and Holded connectors?
They work for trivial cases (one invoice every so often). For serious volumes or complex business logic, they fall short: no good pagination, no error handling, no idempotency. The result: duplicated or lost data with no alert.
Do we have to rebuild all our scenarios?
No. We audit your current scenarios, identify the critical ones (those touching invoicing, accounting, sensitive data) and reinforce only those. The trivial ones can stay as they are.
How much does Make plus your layer cost?
Make: your current plan (typically 9-29 euros a month). Our layer: a one-off implementation fee plus optional monthly maintenance (around 100-200 euros). It works out cheaper than having developers firefighting.
What if I prefer n8n instead of Make?
Same approach. Self-hosted n8n plus our layer works the same way. Some companies prefer n8n because it is open-source. We help you decide.
Does it work for Zapier too?
Yes, same model. But Zapier is more expensive at scale, which is why many companies migrate to Make or n8n as they grow.
How long does it take?
Initial audit: 2-3 days. Implementation depending on volume: 4-10 days.
Related integrations
Shall we talk about your Make (Integromat) integration?
A 30-minute call, no strings. You leave with scope and a price.