Can I treat work emails differently?

Yes. enrich.person resolves the email to a company, then a filter or a branch routes business signups somewhere louder than personal ones.

How do I stop duplicate entries?

Pass the email as idempotencyKey; the gate enforces uniqueness, so a double-submit counts once and keeps positions honest.

Can I keep a full copy of the list?

Fan out: send the alert to a chat channel and the same event to Postgres, so the canonical list lives in your own database.

ingestlayer/recipes/v0.4

Track waitlist signups in Telegram

See who joins the waitlist as it happens — with their position and where they came from — so launch outreach starts the day they sign up, not after the next export.

01source

sourcesdk.eventTypeScript SDK

matchwaitlist.joined

02pipeline · 2 steps

01ENRenrich.personemail → company · role
02CTLfilter.matchskip disposable-email domains

03destinations · 1

totelegramTelegram
chat@oncall

the event

You emit waitlist.joined 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
positionnumberplace in line
referrerstringwhere they came from
created_atstringISO 8601

emit it

From your code with the TypeScript SDK — or any language over the REST endpoint and signed webhook ingress.

emit waitlist.joined

import { ingest } from "@ingestlayer/sdk";

await ingest("waitlist.joined", {
  email:    form.email,
  position: list.length + 1,
  referrer: req.headers.referer,
}, {
  idempotencyKey: form.email,   // one slot per email
});

route it to Telegram

Message a person, group, or channel through a connected bot.

01
connect a bot
Create a bot with @BotFather and paste its token. We register the webhook and verify it in-region.
02
start a chat
Send /start to the bot from the target chat — or add it to the group/channel — then pick the chat from the list.
03
format the text
Messages use MarkdownV2; the default template bolds the event name and lists fields. Reserved characters in field values are escaped for you.

in telegramdelivered

oncall
*support.ticket.created*
ticket    T-4821
subject   API returning 500s
tier      enterprise
urgency   critical

notes

Telegram caps a bot at roughly 30 messages per second overall, and one per second to a single chat.
The bot must be added to a group — and promoted to admin for a channel — before it can post.
MarkdownV2 requires escaping characters like _ * [ ] ( ); ingestlayer escapes field values, but custom templates are your responsibility.

questions

Can I treat work emails differently?: Yes. enrich.person resolves the email to a company, then a filter or a branch routes business signups somewhere louder than personal ones.
How do I stop duplicate entries?: Pass the email as idempotencyKey; the gate enforces uniqueness, so a double-submit counts once and keeps positions honest.
Can I keep a full copy of the list?: Fan out: send the alert to a chat channel and the same event to Postgres, so the canonical list lives in your own database.

build this pipeline or read the quickstart →