Send lead events to your own endpoint

A webhook endpoint sends every lead event, as signed JSON, to a URL you control. Choose it when you want every field Embers has, or when the tool you use is not one of the native destinations you can choose from for your leads.

Before you start

• A public HTTPS receiving URL on the default port (443). Embers rejects plain HTTP, any other port, a username or password in the URL, a hostname that resolves to a private address, and any URL containing #, because a fragment is never sent in an HTTP request.
• With a service such as Webhook.site, copy the unique receiving URL, not the dashboard or viewer URL open in your browser.
• Somewhere safe for the signing secret, such as your receiver’s secret manager.

Create an endpoint

For Zapier, Make, or Clay you can skip these steps: Set up on the tool’s row on Integrations adds an endpoint named after the tool, subscribed to new leads. See the guides for Zapier, Make, and Clay.

1. Open the Webhooks page

   Open Integrations in the sidebar (/integrations). On the Build your own shelf, choose the button on the Webhooks row: Configure, or Fix when an endpoint needs you. It opens the Webhooks page (/integrations/webhooks).

   Settings, then Developer, then Webhooks (/developer/webhooks) manages the same endpoints in its own layout, and every step below works there too. The Developer entry only appears for administrators.

2. Add the endpoint

   Choose Add endpoint on the Endpoints card. Give it a Name that says where the events go, for example Sales CRM, and paste the receiving URL into Endpoint URL. A workspace can have up to 10 endpoints; Add endpoint turns off at the tenth.

3. Choose the events

   Each endpoint has its own subscriptions, and at least one must be selected:

   In the app	Event type	Fires when	New endpoint
   New ICP lead	lead.created	A scored engager matches your ICP or is approved manually	Selected
   New engagement	lead.engagement.added	A lead you already have engages again. One event per lead per scan	Not selected
   Lead status changed	lead.status_changed	A lead moves to a different pipeline status	Selected
   Report ready	report.generated	A client report finishes generating or regenerating	Selected

   New engagement is the highest-volume event, which is why a new endpoint does not subscribe to it. Add it once your receiver can handle repeats.

4. Save the signing secret

   When you choose Create endpoint, Embers shows Save the signing secret with a secret that starts whsec_. Copy it into your receiver’s secret manager, then choose I saved the secret. It is not shown again.

5. Send a sample event

   Open the endpoint’s … menu and choose Send test. It sends a sample of the first event the endpoint subscribes to, and the delivery shows on the Activity card. Send test beside the status at the top of the page does the same for the first endpoint that can deliver. Under Settings, then Developer, Test lets you pick the event under Send a sample event.

   The sample arrives with the event type webhook.test and data.is_test set to true, so your receiver can tell it apart from a real event. The lead or report inside matches the production shape of the sampled event, which is what you map fields from in the recipes for Zapier, Make, Clay, and n8n.

Before your receiver trusts a request, verify its signature. The webhook payload reference lists every field.

Which leads trigger an event

lead.created and lead.engagement.added fire only for qualified leads: a score above zero, an ICP match or a manual approval, and a company that is not on your company blocklist. Each person produces lead.created once, the first time they qualify. When a lead qualifies in the same scan that found new engagement, you get lead.created alone, because it already carries that engagement.

lead.status_changed fires whenever someone moves a lead to a different status, including when blocking a company dismisses the lead. report.generated fires when a client report is ready.

Delivery rules do not apply to webhook endpoints. The endpoint receives every event it subscribes to, and your receiver decides what to keep.

Read the Webhooks page

The page reads top to bottom by urgency:

• Status: one sentence, such as “Sending to Zapier”, “Delivery to Zapier is paused”, “Every endpoint is turned off”, or “Not sending yet: add an endpoint”, with Send test beside it once there is an endpoint.
• Needs attention, only when something does: a paused endpoint with its reason and Resume, an endpoint that is off with Turn on, and the newest three failed deliveries across every endpoint, each with Replay.
• Endpoints: one row each, with an Active, Paused, or Disabled badge, where it Sends to, its Events, and a switch under On.
• Activity: one endpoint’s deliveries, newest first, filtered All or Failed (pick the endpoint at the top of the card). Webhooks have no delivery rules, so nothing is held back; a delivery kept while the endpoint was paused or off is Blocked, under All. Each row names the lead, its state, and why it did not go out, such as “Your endpoint answered HTTP 500”.
• Works with (the Zapier, Make, and Clay rows), Signatures, and the Payload schema.

A row’s chevron opens Delivery details: its status, the attempt count, when it was created, the next attempt, the JSON payload, and every attempt with its HTTP status (or “Network error”), duration, and the start of your response. Under Settings, then Developer, the same history is Recent deliveries, filterable by status and by event.

History is kept for 30 days. Replay appears on Failed and Blocked deliveries while the endpoint is active. Webhook retries and pauses explains the retry schedule and what pauses an endpoint.

Change, pause, or remove an endpoint

Choose an endpoint’s row to edit it, use its switch, or open its … menu (Edit, Send test, Rotate secret, Resume while it is paused, and Remove):

• Edit changes the name, URL, or events. Changing the URL of a paused endpoint also clears the pause.
• The switch, the same setting as Send events inside Edit, stops deliveries without deleting anything. Events created while it is off are kept as Blocked rather than sent, and you can replay them later.
• Rotate secret issues a new secret and shows it once. New deliveries are signed with it straight away.
• Remove deletes the endpoint and its delivery history after a confirmation.

Account administrators are emailed when an endpoint is created, updated, removed, paused, resumed, or has its secret rotated. The email names the endpoint, workspace, destination hostname, who acted, and what changed, never the URL path, query parameters, or secret.

Troubleshooting

The URL is rejected when you save. It uses HTTP, a non-default port, credentials, or a # fragment, or its hostname does not resolve to a public address. Paste the receiving URL your tool gives you, exactly as given.

Send test is unavailable. The endpoint is paused or switched off. Resume it or turn it back on, then test.

A new lead never produced an event. The person has not qualified yet, the endpoint does not subscribe to that event, or the delivery is sitting in Blocked. Check the endpoint’s Activity to find out which.

Requests arrive but your receiver rejects them. Your receiver answered with a 4xx. A 400, 409, or 422 fails only that event, until five in a row pause the endpoint; any other 4xx pauses it at once. Work through a webhook endpoint is paused.

Related