ingestlayer/recipes

Track form submissions in Slack

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

  • toslackSlack
    channel#alerts

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 Slack

Post to any channel in your workspace. Connect once with OAuth, pick the channel per pipeline.

  1. 01

    connect your workspace

    Authorize the ingestlayer Slack app over OAuth from the destinations page. We hold only a channel-scoped bot token, in-region, in the same KMS as your other credentials.

  2. 02

    pick a channel

    Choose any public channel, or invite the bot to a private one. The channel is set per pipeline, so different events can land in different places.

  3. 03

    map the message

    Reference event fields with $event.* in the message template. The default renders a titled block with the event name and its key fields.

in slackdelivered
┌─ #alerts ──────────────────────────────┐
│  ingestlayer  APP                       │
│  user.signed_up                         │
│  email   ada@acme.com                   │
│  plan    pro                            │
│  source  marketing-site                 │
└─────────────────────────────────────────┘

notes

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

form submissions, routed elsewhere

more, into Slack