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 Postgres

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

towarehouse.pgPostgres
tableevents.signups

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 Postgres

Insert each event as a row into a table in your own Postgres.

01
add the connection
Paste a Postgres connection string. Connections originate from our EU region — allowlist those egress IPs on your database.
02
point at a table
Name the target table. Top-level event fields map to columns, and the full payload is also available as a jsonb column.
03
map columns
Match event fields to columns with $event.* references, or accept the default mapping into a typed events table.

in postgresdelivered

INSERT INTO events.signups
  (user_id, email, plan, source, payload)
VALUES
  ('u_018f', 'ada@acme.com', 'pro',
   'marketing-site', '{ … }'::jsonb);

notes

The target table must already exist with compatible column types; ingestlayer never runs DDL on your database.
Connections come from fixed EU egress IPs — add them to your firewall, or inserts will time out.
Use a jsonb column for the full payload when your event shape changes often, so a new field never breaks the insert.

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 →