What makes a lead 'hot'?

Your prompt does. classify weighs the enriched firmographics and stated intent against your definition and returns a typed fit label.

Where do the firmographics come from?

enrich.person resolves the email to company, funding, and headcount in flight, so the score is based on real data, not a form field.

Can warm leads still be captured?

Yes — route hot leads to sales and send every lead to your CRM or warehouse in parallel, so nothing is lost.

ingestlayer/recipes/v0.4

Flag high-value leads in Webhook

Score inbound leads in flight and surface only the ones worth a fast follow — by company size, fit, and intent — so sales sees the whales, not the noise.

01source

sourcesdk.eventTypeScript SDK

matchlead.created

02pipeline · 3 steps

01ENRenrich.personemail → company · funding · headcount
02ENRclassifyfit → hot | warm | cold
03CTLfilter.matchfit = hot only

03destinations · 1

towebhook.outWebhook
urlhttps://api.acme.com/hooks

the event

You emit lead.created with this shape. The TypeScript SDK keeps the call type-safe, and the event is stored whole — so every field below is available to the pipeline by name.

emailstring
companystring
company_sizenumberheadcount, optional
plan_intentstringstated interest
sourcestring

emit it

From your code with the TypeScript SDK — or any language over the REST endpoint and signed webhook ingress.

emit lead.created

import { ingest } from "@ingestlayer/sdk";

await ingest("lead.created", {
  email:       form.email,
  company:     form.company,
  plan_intent: form.plan,
  source:      "pricing-page",
}, {
  idempotencyKey: form.email,
});

route it to Webhook

POST the processed event as JSON to any HTTPS endpoint you control.

01
set the URL
Any HTTPS endpoint. The processed event is delivered as a JSON body on POST.
02
choose auth
None, a bearer token, or HMAC signing. Signed requests carry an X-Ingestlayer-Signature header you verify with your shared secret.
03
confirm receipt
Return a 2xx within the timeout. Non-2xx responses trigger retries with exponential backoff before the delivery dead-letters.

in webhookdelivered

POST /hooks HTTP/1.1
Host: api.acme.com
Content-Type: application/json
X-Ingestlayer-Signature: t=1717000000,v1=9f86d08…

{
  "type": "user.signed_up",
  "payload": { "email": "ada@acme.com", "plan": "pro" }
}

notes

Endpoints must respond within 10 seconds; slower responses are treated as failures and retried.
Retries use exponential backoff for several attempts before dead-lettering — make your handler idempotent.
Verify the HMAC signature before trusting a payload; the raw body is signed, so compute the digest before JSON parsing.

questions

What makes a lead 'hot'?: Your prompt does. classify weighs the enriched firmographics and stated intent against your definition and returns a typed fit label.
Where do the firmographics come from?: enrich.person resolves the email to company, funding, and headcount in flight, so the score is based on real data, not a form field.
Can warm leads still be captured?: Yes — route hot leads to sales and send every lead to your CRM or warehouse in parallel, so nothing is lost.

build this pipeline or read the quickstart →