Do I need a separate call for every plan?

No. Emit one user.signed_up event with a plan field, then branch on it in the pipeline if you want different destinations per plan.

What if the same signup fires twice?

Pass the user id as idempotencyKey. The gate enforces (project, key) uniqueness, so a retry or double-submit counts once.

Can I enrich the signup before it lands?

Yes — the enrich.person action resolves the email to company, role, and country in flight, so the alert arrives already annotated.

ingestlayer/recipes/v0.4

Track user signups in Slack

Know the moment someone signs up — who they are, which plan they picked, and where they came from — without waiting for a daily export or tailing logs.

01source

sourcesdk.eventTypeScript SDK

matchuser.signed_up

02pipeline · 2 steps

01ENRenrich.personemail → company · role · country
02MUTredact.piiemail + ip masked per destination

03destinations · 1

toslackSlack
channel#alerts

the event

You emit user.signed_up 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.

user_idstringyour internal id
emailstring
planstringfree | pro | scale
sourcestringwhere 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 user.signed_up

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

await ingest("user.signed_up", {
  user_id: user.id,
  email:   user.email,
  plan:    user.plan,
  source:  "marketing-site",
}, {
  idempotencyKey: user.id,   // one signup per user, ever
});

route it to Slack

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

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.
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.
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

Slack rate-limits to roughly one message per second per channel; bursts are queued and retried, never dropped.
The bot must be a member of a private channel before it can post there — invite it explicitly.
Block Kit caps a message at 50 blocks and 3000 characters per text field; oversized events are truncated with a link to the full payload.

questions

Do I need a separate call for every plan?: No. Emit one user.signed_up event with a plan field, then branch on it in the pipeline if you want different destinations per plan.
What if the same signup fires twice?: Pass the user id as idempotencyKey. The gate enforces (project, key) uniqueness, so a retry or double-submit counts once.
Can I enrich the signup before it lands?: Yes — the enrich.person action resolves the email to company, role, and country in flight, so the alert arrives already annotated.

build this pipeline or read the quickstart →