# Send lead events to your own endpoint

URL: https://useembers.com/help/integrations/webhooks/
Category: Integrations
Plan: Solo and above
Updated: 2026-09-12
Last verified: 2026-09-12

> Create a signed HTTPS webhook endpoint in Embers, choose its events, save the signing secret, send a test, and read the 30-day delivery log.

A webhook endpoint gets you the full event, in JSON, at your own URL, signed so you can prove it came from Embers. It is the destination to choose when you want every field, or when the tool you use is not Slack or HubSpot.

> **Warning: Solo and above, administrators only**
>
> Developer, then Webhooks (`/developer/webhooks`) requires Solo or above, and only account administrators can manage endpoints and signing secrets.

## Before you start

- A public HTTPS receiving URL on the default port. Embers rejects plain HTTP, a non-standard port, a username or password in the URL, and any URL containing a `#` fragment, because browsers never send fragments in an HTTP request.
- With a service like Webhook.site, copy the unique receiving URL, not the dashboard or viewer URL you have open in the browser.
- Somewhere safe to keep the signing secret.

## Create an endpoint

### Open Developer, then Webhooks

In the Embers app, go to **Developer**, then **Webhooks** (`/developer/webhooks`).

### Add the endpoint

Give it a **Name** that says where the events go, for example `Sales CRM`, and paste the receiving URL into **Endpoint URL**. An account can have up to 10 endpoints.

### Choose the events

Each endpoint has its own subscriptions:

| Event | What it means | New endpoint |
| --- | --- | --- |
| New ICP lead | A scored engager matched your ICP or was approved manually | Selected |
| New engagement | A known lead engaged again. One event per lead per scan | Not selected |
| Lead status changed | A lead moved to a different pipeline status | Selected |
| Report ready | A report finished 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 the traffic. At least one event has to be selected.

### Save the signing secret

When the endpoint is created, Embers shows the signing secret once, prefixed `whsec_`. Copy it into your receiving system's secret manager. It is not shown again. **Rotate secret** issues a new one when it is lost or exposed.

### Send a sample event

Use **Test**, then pick an event from **Send a sample event**. The list contains the events this endpoint subscribes to.

Every sample is delivered with the event type `webhook.test` and `data.is_test` set to `true`, so a test can never create a real CRM record. The nested lead or report fields match the production shape of the event you picked, which is what makes tests useful for building a Zapier, Make, or Clay mapping.

## The delivery log

Each endpoint has a **Recent deliveries** list, filterable by status (Pending, Delivered, Failed, Blocked) and by event type. Open a delivery to see the state, the attempt count, when it was created, the next attempt, the raw JSON payload, and every attempt with its HTTP status, duration, and response.

History is kept for 30 days. Failed and blocked deliveries have a **Replay** button while the endpoint is active.

> **Tip: Turning delivery off without deleting anything**
>
> **Send events** is a per-endpoint switch. Turn it off to stop deliveries while keeping the endpoint, its URL, its subscriptions, and its secret. Events created while it is off are retained as blocked rather than sent.

## What happens after you save

Embers signs every request with Standard Webhooks headers and retries failures on a fixed schedule. See [Verify webhook signatures](/help/integrations/verify-webhook-signatures/) and [Webhook retries and pauses](/help/integrations/webhook-retries-and-pauses/) for both.

Account administrators are emailed when an endpoint is created, updated, removed, paused, resumed, or has its secret rotated. Those notices name the endpoint, the workspace, the destination hostname, who acted, and what changed. They never contain the URL path, query credentials, or the signing secret. Saving an endpoint without changing anything sends nothing.

## Related

- [Webhook payload reference](/help/integrations/webhook-payload-reference/): The envelope, every event type, and every lead field.

- [Verify webhook signatures](/help/integrations/verify-webhook-signatures/): Check the HMAC before you trust a request.

- [Retries and pauses](/help/integrations/webhook-retries-and-pauses/): The eight attempts, and what pauses an endpoint.

## Frequently asked questions

**How many endpoints can one account have?**

Up to 10. Each has its own name, event subscriptions, signing secret, and delivery history.

**Can I see the signing secret again later?**

No. It is shown once when the endpoint is created or the secret is rotated. If you lose it, rotate the secret and update your receiver.