Flag high-value leads in Discord
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
- todiscordDiscordchannel#ops
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 Discord
Send rich embeds to a channel via a connected bot or a channel webhook.
- 01
connect the bot
Add the ingestlayer bot to your server, or paste a channel webhook URL. Either credential is held in-region.
- 02
choose the channel
Select the target channel from the picker. Each connected channel is one reusable destination row.
- 03
shape the embed
The default embed carries the event name as its title and the payload as name/value fields; override with $event.* references.
┌─ #ops ─────────────────────────────────┐ │ ▎ payment.failed │ │ ▎ customer acme-inc │ │ ▎ amount €240.00 │ │ ▎ reason insufficient_funds │ │ ▎ attempt 2 │ └─────────────────────────────────────────┘
notes
- Channel webhooks are limited to about 30 messages per minute; sustained volume should use the bot connection instead.
- An embed allows at most 25 fields and 6000 total characters; larger events are summarized.
- Mentions (@everyone, @role) are suppressed by default — opt in per pipeline if you actually want a ping.
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 TelegramTelegram
- Flag high-value leads in EmailEmail
- Flag high-value leads in WebhookWebhook
- Flag high-value leads in PostgresPostgres
- Flag high-value leads in NotionNotion
more, into Discord
- Track user signups in Discordtrack
- Monitor failed payments in Discordmonitor
- Route support escalations in Discordalert
- Track waitlist signups in Discordtrack
- Track new subscriptions in Discordtrack
- Track canceled subscriptions in Discordtrack
- Track successful payments in Discordtrack
- Track trial conversions in Discordtrack
- Track form submissions in Discordtrack
- Track feature usage in Discordtrack
- Track file uploads in Discordtrack
- Monitor failed logins in Discordmonitor
- Monitor usage-limit hits in Discordmonitor
- Monitor error spikes in Discordmonitor
- Monitor cron-job health in Discordmonitor
- Monitor CI/CD build status in Discordmonitor
- Catch churn-risk signals in Discordalert
- everything you can pipe to Discordhub