How do webhook notifications work
Paste a webhook URL into Branding → Notifications → Webhook URL . LemAudit POSTs a JSON payload to it every time a lead is captured, an audit completes, or a…
Paste a webhook URL into Branding → Notifications → Webhook URL. LemAudit POSTs a JSON payload to it every time a lead is captured, an audit completes, or a report is opened. Use it to push leads into Zapier, Slack, HubSpot, or any tool that listens for HTTPS POST.
What gets sent
3 events fire by default: `lead.created`, `audit.completed`, and `report.opened`. Each POST carries a stable JSON shape: event name, timestamp, lead_id, lead email, audit URL, health score, and the top 3 findings. Hot-lead flagging is included on lead.created so your downstream automation can route urgent leads differently.
Think of it like SMS forwarding. LemAudit keeps the original; your other tool gets a copy in real time.
How LemAudit delivers it
Each event queues through the dispatch-webhook edge function. We POST with a 5-second timeout. On 5xx errors we retry 3 times with backoff (1s, 4s, 16s). 4xx responses are treated as permanent failures and not retried — fix the URL and replay manually from Branding → Notifications → Recent deliveries. The payload is signed with HMAC-SHA256 in the `X-LemAudit-Signature` header; verify it with the secret shown next to your webhook URL.
For Slack delivery (a formatted message, not raw JSON), use the Slack toggle in the same panel. It wraps the payload into Slack Block Kit for you. For more granular control, point Zapier at the webhook URL and route from there. The pipeline view shows the same lead.created event in the activity timeline so you can confirm delivery without leaving LemAudit.
Worked example
A 5-person agency pointed their webhook at a Zapier Catch Hook, then mapped `lead.created` to a HubSpot "Create Contact" action and a Slack #leads channel post. From day 1, every new lead landed in HubSpot with the audit score as a custom field, and the team saw a real-time Slack ping. Their median response time dropped from 4 hours to 11 minutes.
When this isn't right
Webhooks are an Agency-plan feature; lower tiers get email alerts only. For inbound integrations (e.g. importing leads from another tool into LemAudit), webhooks are the wrong direction — use the Bulk Scanner CSV upload instead. If your tool needs a strict OpenAPI contract or rate-limit headers, contact support. The webhook is light by design and not a full REST API.