Send your event data to another system
Point evenclo at a URL and we will POST every registration, check-in, lead and survey answer to it as it happens — into your CRM, into Zapier, or into anything that accepts a web request.
A webhook is a URL you own. Every time something happens at your event, evenclo sends a small message to that URL within a second or two. Your CRM, your dashboard, your Zap — whatever is listening — reacts to it.
It replaces the loop most teams run by hand: export a CSV at the end of each day, open it, paste it somewhere. With a webhook there is no export and no lag.
You will need somewhere to send it to. If you have no developer, use Zapier or Make: both give you a URL to paste, and both can then create a contact, add a spreadsheet row, or send a Slack message from what we send them.
Set one up
Open Webhooks in the sidebar.
- Paste your URL into URL. It has to start with
https://. - Give it a name under What is it for — "Salesforce lead sync", "ops dashboard". You will thank yourself when there are four of them.
- Tick what should be sent. All four are ticked to begin with:- Someone registers- Someone checks in- A booth captures a lead- A survey is answered
- Press Add webhook.
A signing secret appears — a long string starting with whsec_. Copy it now and give it to whoever is building the receiving end.
That is the only time the secret is shown in full. Afterwards the list only shows its first few characters. If it is lost, press New secret — but the old one stops working the moment you do, so tell your developer before you press it.
Check that it works
Press Test on the webhook. We send a sample registration and tell you exactly what came back — *Delivered — they answered 200*, or the error.
Do this before the event, not during it. A webhook pointed at a URL with a typo fails silently the rest of the time: there is nothing to see on your screen when an attendee registers.
After real events start flowing, the webhook shows a status from its last delivery:
| What it shows | What it means |
|---|---|
never fired | Nothing has happened yet that this webhook subscribes to |
OK 200 | The last delivery was accepted |
HTTP 404, HTTP 500 | Their end rejected the last delivery. Nothing was retried |
| an error message | We could not reach them at all — usually a dead URL or a timeout |
paused | Switched off by Pause. Nothing is being sent |
What gets sent, and when
Someone registers fires when a registration is complete — including when the organizer adds someone by hand, when a guest accepts an invitation, and when a paid ticket is actually paid for. It does not fire the moment someone starts a checkout that they might abandon.
Someone checks in fires on arrival. It does not fire for check-outs, for undone scans, or for a scan that was refused.
A booth captures a lead fires for every lead any exhibitor scans. Individual exhibitors can also point their *own* leads at their own CRM — see Send your leads to your CRM in the exhibitor guide — and that is separate from this.
A survey is answered fires on submission. If the survey is anonymous, we send the answers and no name.
Bulk CSV imports do not fire. Importing 500 attendees would fire 500 messages at your CRM in a few seconds, which most of them treat as an attack. Import the same file at both ends instead.
Things worth knowing before you rely on it
We do not retry. If your endpoint is down for ten minutes, those events are gone — they are not queued and re-sent later. The webhook is a live feed, not the record. Your attendee list, your CSV exports and your reports remain the source of truth, and a nightly export is still the right way to reconcile.
We wait five seconds. If your endpoint takes longer than that to answer, we treat it as failed. Have it accept the message and do the slow work afterwards.
Anyone who learns the URL can post to it. That is why we sign every message. Whoever builds your receiving end should verify the signature — the details are in Webhook payloads and signatures.
Pausing and removing
Pause stops delivery without losing the configuration or the secret — right for a CRM that is down for maintenance, or an event that has ended.
Remove deletes it. We stop sending immediately.
Both are per-event. A webhook set up on one event does not carry over to the next one you create.