Webhooks

Put qualified lead and report updates where your team already works.

Embers can send new leads, pipeline status changes, and ready reports to HubSpot (native, Solo and above), Zapier, Make, Clay (signed-webhook recipes, not native SDKs), or internal systems through dedicated, signed HTTPS endpoints.

Get a free Signal Audit Start free trial

Signal Audit: type one keyword, see a public buyer signal. No card.
Trial: your first 2,000 engagers free. Card required.

lead.created200 delivered

{
  "id": "e1b4f6e8-4c4a-4f50-...",
  "type": "lead.created",
  "api_version": "2026-07-20",
  "data": {
    "lead": {
      "score": 91,
      "sources": ["post_engagement"],
      "contact": { "email": "stored when enriched" }
    }
  }
}

Illustrative Solo+ payload. Signed HTTPS delivery.

How a signed event is delivered

Stable event IDs and signatures support verification and safe deduplication.

01 Route lead and report events into your workflow Subscribe an endpoint to lead.created, lead.status_changed, and report.generated events. Each payload names the account that produced it and carries the full lead object.
02 Verify every delivery Signed requests, stable event IDs, and delivery metadata give receiving systems what they need to verify a request and safely deduplicate it.
03 Recover without losing the signal Seven retries over about six days, delivery logs, and manual replay make failed deliveries visible and let your team recover without falling back to a CSV handoff.

lead.createdIllustrative

{
  "id": "e1b4f6e8-4c4a-4f50-...",
  "type": "lead.created",
  "api_version": "2026-07-20",
  "data": {
    "lead": {
      "score": 91,
      "sources": ["post_engagement"]
    }
  }
}

Subscribe an endpoint and route each event into the tools you already use.

Request headersIllustrative

webhook-id: stable event UUID
webhook-timestamp: unix seconds
webhook-signature: v1,<base64 HMAC-SHA256>

Verify the signature before processing, then use the event ID to deduplicate.

Delivery logIllustrative

lead.created 200 delivered
lead.status_changed 500 retry queued
report.generated 200 replayed

Seven retries over about six days, delivery logs, and manual replay, with no CSV handoff.

Supported delivery events

Stable event IDs and signatures support verification and safe deduplication.

Event	When it fires	Delivery
`lead.created`	A qualified lead enters the queue	Signed HTTPS
`lead.status_changed`	A lead’s pipeline status changes	Signed HTTPS
`report.generated`	A report is ready	Signed HTTPS

1. Add an endpoint.Use an HTTPS URL controlled by your team.
2. Verify signatures.Validate the request before processing it.
3. Handle retries.Use event IDs to make processing idempotent.

Delivery policy. Up to 10 HTTPS endpoints, seven retries over about six days, 30-day delivery logs, and manual replay are included. Webhooks are Solo and above and carry stored lead.contact when the lead is already enriched. Zapier, Make, and Clay consume this signed webhook as recipes, not native SDKs.

A dependable handoff from lead signal to your operating system.

Use the lead context you need

Webhook payloads include the event type, stable ID, and relevant lead or report details needed to route each update into the right workflow.

Solo and above, administrators only

Webhooks are configured by an account administrator on Solo and above. Payloads include stored lead.contact (email and phone) when a lead is already enriched, plus workspace and owner when those fields exist.

Your next pass

See which public signals are
worth your time.

Start with a free Signal Audit and review the fit before choosing a plan.

Get a free Signal Audit Or start free trial

Your first 2,000 engagers free · Card required · No LinkedIn login · Cancel anytime