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 Email

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

toemail.outEmail
toalerts@acme.com

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

in emaildelivered

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

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 →