Make.com — formerly Integromat — is frequently the better choice for trade show lead automation than the more common alternative, for two specific reasons: routing and error handling.
Neither matters much for a simple two-step connection. Both matter enormously when 200 leads arrive over three days on unreliable venue wifi.
The router advantage
Event leads are not homogeneous. A single scenario often needs to handle:
- Qualified prospects → CRM as an opportunity, owner assigned, task created
- Unqualified scans → CRM as a basic contact, nurture list
- Partners → different owner, different pipeline entirely
- Existing contacts → update rather than create
In Zapier this typically means several separate zaps, or heavy use of paths. In Make, a router module branches a single scenario into as many routes as needed, each with its own filter and its own modules.
One scenario, visible on one canvas, with the whole routing logic legible at a glance. When something breaks mid-event, that legibility is worth a great deal.
Error handling is the real reason to choose Make
This is the decisive feature for trade shows.
Make lets you attach an error handler to any module, with directives:
| Directive | Behaviour |
|---|---|
| Resume | Substitute a value and continue |
| Rollback | Undo the whole execution |
| Commit | Keep what succeeded and stop |
| Break | Store the execution for retry later |
| Ignore | Discard the error and continue |
Break is the one that matters at events. With Break configured, a failed execution goes into the incomplete executions queue rather than vanishing. When the CRM comes back, or the connection recovers, you retry the queue and the leads land.
Without it, a CRM API outage during a busy afternoon means those leads are gone with no record they ever existed.
A workable event scenario
1. Webhook — lead captured at booth
2. Set variables — normalise email, trim whitespace
3. CRM: Search Contact — by email [error handler: Break]
4. Router
├─ Route A: not found + qualified
│ → CRM: Create Contact [error handler: Break]
│ → CRM: Create Deal
│ → CRM: Create Task (48h)
│ → Slack: notify owner
├─ Route B: not found + unqualified
│ → CRM: Create Contact
│ → Add to nurture list
└─ Route C: found
→ CRM: Update Contact
→ CRM: Add note with event context
→ CRM: Create Task (48h)
Every module touching an external service gets a Break handler. That single decision is what makes the scenario survive a real trade show.
Connectivity planning
Exhibition halls have poor, contended wifi. Make cannot process a webhook it never receives.
Mitigations, in order of effectiveness:
- A capture tool that queues locally and retries — solves the problem at source
- Mobile data instead of venue wifi
- Daily reconciliation — compare badge scans against CRM records at the end of each day
Reconciliation is the safeguard people skip and then regret. It takes two minutes and catches a broken pipeline on day one instead of after the show.
Operations consumption
Make bills by operation — each module execution counts as one.
A ten-module scenario processing 200 leads is 2,000 operations. Routers help here: only the modules on the taken route execute, so a well-designed router-based scenario consumes fewer operations than running everything and filtering afterwards.
Before an event, check your remaining operations against expected volume and upgrade for the month if needed.
Scheduling and history
Webhook scenarios run instantly on receipt — the right choice for events.
Make's execution history is more detailed than most comparable tools, showing the data at every step of every run. During a show that is genuinely useful for diagnosing a mapping problem quickly, without reproducing it.
Set history retention appropriately before the event, since it is what you will use to debug.
Make or a direct integration?
Make excels at connecting tools you do not control, with complex routing, without engineering resource.
A tool writing directly to the CRM removes the middleware hop entirely — one fewer thing to fail, no operations to consume, no webhook to be lost on venue wifi. That is the approach Confee takes, with structured fields reaching the CRM without an intermediate platform.
For badge scanners, forms and third-party tools you do not control, Make remains an excellent choice.
Pre-event checklist
- Webhook trigger, not scheduled
- Search-before-create in place
- Break error handlers on every external module
- Router logic tested for each branch
- Operations allowance checked against volume
- Incomplete executions queue monitored during the show
- Tested end to end with a real record
- Daily reconciliation planned
The short version
Make suits trade shows because of its router and, above all, its error handling. Attach Break handlers to every module touching an external service so failed leads queue for retry instead of disappearing.
Then check the incomplete executions queue each evening. That is where your missing leads will be — recoverable, if you configured it beforehand.
Related reading:
- Automating Trade Show Leads with Zapier — the alternative platform
- CRM Field Mapping for Event Leads — what to write into the CRM
- How to Sync Trade Show Leads to Pipedrive — a worked CRM example
FAQ
Is Make.com better than Zapier for trade show leads?
For complex routing, generally yes. Make's router branches a single scenario without duplication, and its error handlers allow explicit fallback rather than silent failure. For simple connections Zapier is quicker to set up.
How does Make.com handle errors during an event?
Through module directives — Resume, Rollback, Commit, Break and Ignore. Break stores a failed execution for later retry rather than discarding it, so an outage does not lose the lead permanently.
What is a Make.com scenario for trade show leads?
A webhook trigger, a search module checking for an existing contact, a router branching on found status and lead quality, CRM create or update modules, and notifications — with error handlers on every external module.
How often do Make.com scenarios run?
Webhook-triggered scenarios run instantly. Scheduled scenarios can run as often as every minute on paid plans. Use webhooks for events.