Webhooks, Zapier and Make
Send Nudge events to your CRM, Zapier, Make or your own endpoint, and check every delivery.
What outgoing webhooks do
A webhook is a URL that Nudge calls each time a chosen event happens in your workspace. Nudge sends an HTTPS POST with a JSON body describing the event. Anything that can receive a webhook can react to it: Zapier, Make, n8n, your CRM's inbound endpoint, or your own server.
This page covers setting webhooks up from the app. The payload format, headers and signature verification are documented in the API reference: Webhooks and event payloads.
Who can manage webhooks
Webhooks are managed from Integrations › Zapier, which needs the Manage API keys & webhooks permission as well as access to Integrations. By default, only Admins have both.
Create a webhook
Open the webhooks panel
In Integrations, find Zapier under Alerts and automation and click Configure (or Manage once a webhook exists). The page lists your webhooks; it is the same list whether you use Zapier, Make or your own endpoint.
Add the endpoint
Click Add webhook and fill in:
- Endpoint URL: the full URL that will receive the events. It must start with
https://and point to a public address. Local or private addresses (such aslocalhostor192.168.x.x) are refused. - Events: tick at least one event (see the table below).
- Signing secret (optional): a secret of your choice, for example a long random string starting with
whsec_. When set, every delivery is signed with HMAC-SHA256 so your endpoint can check that it really comes from Nudge.
Save the secret
Click Create. If you entered a signing secret, a yellow panel Copy your signing secret now shows it one last time. Store it in your endpoint's configuration: it is never displayed again. The webhook then shows a Signed badge.
Events you can subscribe to
The event names below are the labels shown in the Events list.
| Label | Event | Sent when |
|---|---|---|
| Lead created | lead_created | A visitor leaves their details through one of your forms or the website agent, or a contact is created through the Nudge API. |
| Contact updated | contact_updated | A contact is updated through the Nudge API. |
| Booking created | booking_created | A booking is created through the Nudge API. |
| Booking rescheduled | booking_rescheduled | A booking is rescheduled through the Nudge API. |
| Booking cancelled | booking_cancelled | A booking is cancelled through the Nudge API. |
| Outcome recorded | outcome_set | A meeting outcome is recorded through the Nudge API. |
| Form submitted | form_submitted | Listed in the app, not delivered today. |
| Contact disqualified | contact_disqualified | Listed in the app, not delivered today. |
Booking events and the app
Submissions made in a preview or test mode do not trigger webhooks.
Connect Zapier
Create the trigger in Zapier
Create a Zap with the trigger Webhooks by Zapier › Catch Hook. Zapier gives you a custom webhook URL.
Add it in Nudge
In Integrations › Zapier, click Add webhook, paste the Zapier URL in Endpoint URL, tick Lead created (and any other event you need), then Create.
Send a first event and map the fields
Submit one of your forms, or chat with the website agent and leave an email address, with a real (non-test) visit. Zapier receives the event; use its fields to build the action, for example Create contact in HubSpot or Add row in Google Sheets.
Connect Make
In Make, add a Webhooks › Custom webhook module as the first step of a scenario and copy its address. In Nudge, add a webhook with that address and the events you want. Run the scenario once, then trigger a real event so Make learns the data structure.
Manage your webhooks
Each webhook in the list shows its URL, its events and, if it has a secret, the Signed badge. On the right:
- The switch pauses or resumes deliveries. A paused webhook receives nothing.
- Delivery logs (eye icon) opens the last 20 deliveries: the event, the date and time, and the HTTP status your endpoint answered. A red badge means the call failed (an error status or no answer at all).
- Delete (bin icon) removes the webhook immediately, without confirmation.
A webhook cannot be edited. To change its URL, events or secret, create a new webhook and delete the old one.
Delivery behaviour
- Your endpoint has 10 seconds to answer. After that, the delivery is recorded as failed.
- Any
2xxstatus counts as a success. Answer quickly and do the heavy work afterwards. - A failed delivery is not retried. Check the delivery logs if you suspect a gap.
- Each request carries
Content-Type: application/jsonandUser-Agent: Nudge-Webhook/1.0. Signed webhooks also carry anX-Nudge-Signatureheader. See Webhooks and event payloads for the exact format and how to verify it.