ingestlayer/recipes

Track user signups in Discord

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

  • todiscordDiscord
    channel#ops

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 Discord

Send rich embeds to a channel via a connected bot or a channel webhook.

  1. 01

    connect the bot

    Add the ingestlayer bot to your server, or paste a channel webhook URL. Either credential is held in-region.

  2. 02

    choose the channel

    Select the target channel from the picker. Each connected channel is one reusable destination row.

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

in discorddelivered
┌─ #ops ─────────────────────────────────┐
│ ▎ payment.failed                        │
│ ▎ customer   acme-inc                   │
│ ▎ amount     €240.00                    │
│ ▎ reason     insufficient_funds         │
│ ▎ attempt    2                          │
└─────────────────────────────────────────┘

notes

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 pipelineor read the quickstart →

user signups, routed elsewhere

more, into Discord