Get new leads and posts sent to your tool with webhooks

#The three events

lead.created: a new lead reaches your Leads tab, including one added through the API.

lead.status_changed: a lead's outcome is set or changed, on the Leads tab or through the API. Each status fires once, so contacted then won fires twice.

post.published: a blog post is published. It carries the title, address, excerpt, image, target search and publish time.

#Subscribe an address

1. Get a public https address from your tool, for example a webhook trigger in Zapier, Make, n8n or Pipedream.
2. Send POST /v1/hooks with the event and the target_url, and your key in the header.
3. Keep the id you get back. You need it to unsubscribe.

#How delivery works

Each new record is sent to your address as a JSON POST within about two minutes of landing. The body has the event, your account, the record under data, and the same fields again at the top level for tools that only read top-level fields.

A subscription starts from now: whatever was already there counts as seen, so switching a workflow on never replays your history. Several records that arrive together go out oldest first.

The API card on Integrations shows a line such as Sending new leads to your connected tools within about two minutes while a subscription is live.

#Stop a subscription

Send DELETE /v1/hooks/{id}. An address that answers 410 Gone is unsubscribed on the spot, and one that fails ten times in a row is switched off. Revoking the key switches off its triggers too.