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 Webhook

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

towebhook.outWebhook
urlhttps://api.acme.com/hooks

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 Webhook

POST the processed event as JSON to any HTTPS endpoint you control.

01
set the URL
Any HTTPS endpoint. The processed event is delivered as a JSON body on POST.
02
choose auth
None, a bearer token, or HMAC signing. Signed requests carry an X-Ingestlayer-Signature header you verify with your shared secret.
03
confirm receipt
Return a 2xx within the timeout. Non-2xx responses trigger retries with exponential backoff before the delivery dead-letters.

in webhookdelivered

POST /hooks HTTP/1.1
Host: api.acme.com
Content-Type: application/json
X-Ingestlayer-Signature: t=1717000000,v1=9f86d08…

{
  "type": "user.signed_up",
  "payload": { "email": "ada@acme.com", "plan": "pro" }
}

notes

Endpoints must respond within 10 seconds; slower responses are treated as failures and retried.
Retries use exponential backoff for several attempts before dead-lettering — make your handler idempotent.
Verify the HMAC signature before trusting a payload; the raw body is signed, so compute the digest before JSON parsing.

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 →