Webhooks in Settings
Back to the guide
Settings → Webhooks, for owners and admins. Two tabs: Outgoing sends what happens in your CRM to other tools; Incoming lets other tools add records.
Outgoing webhooks
Add webhook, then give it:
- a name, so you can tell it apart;
- the URL to send to — an
https://address on the public internet, from Slack, Zapier, Make, or your own developers; - the events that should trigger it, or every event;
- optionally, only some objects.
You are shown a signing secret. Give it to whoever runs the receiving end: it is how they know a message really came from Deeluge.
Each webhook acts as its own identity. It sees nothing restricted until you add it — it appears as "name (webhook)" — in Access & permissions.
Keeping an eye on it
- Send test sends a test message now and tells you what the receiver answered.
- Log lists the last 50 messages: what was sent, what came back, and when it will be tried again. Open one to see exactly what was sent; Send again re-sends it.
- Pause holds new messages until you Resume. Nothing is lost.
- A webhook that keeps failing for three days is turned off and says why. Fix the receiver, then Turn on.
Webhooks an app installed are marked App: …. You can pause them, but change them by changing the app.
Incoming webhooks
Add incoming webhook, then choose:
- the object records are created in;
- whether to always create a new record, or update the match — for example, the contact with the same email;
- optionally, a list to add each record to.
You get a URL, shown once. Paste it into the tool that should send you records. Anyone with the URL can add records, so treat it like a password; New URL replaces it if it leaks.
Matching fields
Send JSON whose keys are your field keys — {"name": "…", "email": "…"} — and it just
works. For anything else, send one request first, then press Fields: the fields that
arrived are listed, and you match each to one of yours. Nested fields use dots, such as
contact.email. Fixed values are set on every record, such as Source = Website.
Option fields accept the option's name ("Qualified"), checkboxes accept yes/no, and numbers may include commas and currency signs. Blank answers never wipe a field when updating.
Require a signature refuses requests that are not signed with the secret it shows you. Use it when the sending tool can sign; most no-code tools cannot.
Log shows what became of each request — created, updated, or why it was refused. Request bodies are not kept.