ingestlayer/recipes

Flag high-value leads in Slack

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

  • toslackSlack
    channel#alerts

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 Slack

Post to any channel in your workspace. Connect once with OAuth, pick the channel per pipeline.

  1. 01

    connect your workspace

    Authorize the ingestlayer Slack app over OAuth from the destinations page. We hold only a channel-scoped bot token, in-region, in the same KMS as your other credentials.

  2. 02

    pick a channel

    Choose any public channel, or invite the bot to a private one. The channel is set per pipeline, so different events can land in different places.

  3. 03

    map the message

    Reference event fields with $event.* in the message template. The default renders a titled block with the event name and its key fields.

in slackdelivered
┌─ #alerts ──────────────────────────────┐
│  ingestlayer  APP                       │
│  user.signed_up                         │
│  email   ada@acme.com                   │
│  plan    pro                            │
│  source  marketing-site                 │
└─────────────────────────────────────────┘

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 Slack