ingestlayer/recipes

Flag high-value leads in Notion

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

  • tonotion.dbNotion
    databaseSignups

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 Notion

Append events as rows to a Notion database, or content to a page. Connect once with OAuth, pick the target per pipeline.

  1. 01

    connect your workspace

    Authorize the ingestlayer Notion integration over OAuth from the destinations page, then choose which databases and pages it may touch. We hold only that workspace's access token, in-region, in the same KMS as your other credentials.

  2. 02

    pick a target

    Per pipeline, choose a database to append a typed row to, or a page to append content to. The picker lists exactly what you shared with the integration during authorization — nothing else.

  3. 03

    map the columns

    For a database, match event fields to Notion properties — automatically by column name, or per-column with $event.* templates. The title column falls back to the event name, so a row is never blank. For a page, the rendered body is appended as blocks.

in notiondelivered
┌─ Signups · database ───────────────────┐
│  Name        ada@acme.com               │
│  Plan        ● pro                       │
│  Source      marketing-site             │
│  Signed up   2026-06-03                  │
└─────────────────────────────────────────┘

notes

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 pipelineor read the quickstart →

high-value leads, routed elsewhere

more, into Notion