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 Discord

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

todiscordDiscord
channel#ops

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 Discord

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

01
connect the bot
Add the ingestlayer bot to your server, or paste a channel webhook URL. Either credential is held in-region.
02
choose the channel
Select the target channel from the picker. Each connected channel is one reusable destination row.
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

Channel webhooks are limited to about 30 messages per minute; sustained volume should use the bot connection instead.
An embed allows at most 25 fields and 6000 total characters; larger events are summarized.
Mentions (@everyone, @role) are suppressed by default — opt in per pipeline if you actually want a ping.

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 →