Flag high-value leads in Email
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
02pipeline · 3 steps
- 01ENRenrich.personemail → company · funding · headcount
- 02ENRclassifyfit → hot | warm | cold
- 03CTLfilter.matchfit = hot only
03destinations · 1
- toemail.outEmailtoalerts@acme.com
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.
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 Email
Send a transactional email to one or more recipients, addressable from event fields.
- 01
set the recipient
Enter a fixed address, or reference an event field like $event.payload.email to route per event.
- 02
write subject and body
Both accept $event.* templates. The body renders as plain text with an optional summary table of the payload.
- 03
confirm the sender
Mail goes out from mail@notify.ingestlayer.com with SPF and DKIM aligned. Set a reply-to if you want responses to reach you.
From: mail@notify.ingestlayer.com To: alerts@acme.com Subject: Payment failed — acme-inc (€240.00) A charge failed for acme-inc. amount €240.00 reason insufficient_funds attempt 2
notes
- Outbound email is metered against a monthly quota that scales with your plan; over-quota sends are deferred, not dropped.
- Sending from a fixed ingestlayer domain keeps deliverability high, but the From address is not your own domain.
- Recipient addresses pulled from event fields are validated at send time; a malformed address dead-letters that delivery.
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.
high-value leads, routed elsewhere
- Flag high-value leads in SlackSlack
- Flag high-value leads in DiscordDiscord
- Flag high-value leads in TelegramTelegram
- Flag high-value leads in WebhookWebhook
- Flag high-value leads in PostgresPostgres
- Flag high-value leads in NotionNotion
more, into Email
- Track user signups in Emailtrack
- Monitor failed payments in Emailmonitor
- Route support escalations in Emailalert
- Track waitlist signups in Emailtrack
- Track new subscriptions in Emailtrack
- Track canceled subscriptions in Emailtrack
- Track successful payments in Emailtrack
- Track trial conversions in Emailtrack
- Track form submissions in Emailtrack
- Track feature usage in Emailtrack
- Track file uploads in Emailtrack
- Monitor failed logins in Emailmonitor
- Monitor usage-limit hits in Emailmonitor
- Monitor error spikes in Emailmonitor
- Monitor cron-job health in Emailmonitor
- Monitor CI/CD build status in Emailmonitor
- Catch churn-risk signals in Emailalert
- everything you can pipe to Emailhub