Can I keep spam out of the channel?

classify labels the intent and a filter drops spam before it's ever posted — no rules to maintain by hand.

Different forms, different places?

Branch on form_id so a demo request reaches sales and a bug report reaches support.

Is PII safe in transit?

redact.pii masks sensitive fields per destination, so the chat copy is clean while the warehouse keeps the full record.

Track form submissions in Email

Route contact, demo, and feedback forms the instant they're submitted — classified by intent and stripped of PII before they reach a channel.

01source

sourcesdk.eventTypeScript SDK

matchform.submitted

02pipeline · 3 steps

01ENRclassifyintent → demo | support | spam
02CTLfilter.matchdrop intent = spam
03MUTredact.piimask email + phone per destination

03destinations · 1

toemail.outEmail
toalerts@acme.com

the event

You emit form.submitted 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.

form_idstringwhich form
emailstring
fieldsobjectraw form values
pagestringpage URL

emit it

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

emit form.submitted

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

await ingest("form.submitted", {
  form_id: form.id,
  email:   form.values.email,
  fields:  form.values,
  page:    location.pathname,
});

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

Can I keep spam out of the channel?: classify labels the intent and a filter drops spam before it's ever posted — no rules to maintain by hand.
Different forms, different places?: Branch on form_id so a demo request reaches sales and a bug report reaches support.
Is PII safe in transit?: redact.pii masks sensitive fields per destination, so the chat copy is clean while the warehouse keeps the full record.

build this pipeline or read the quickstart →