Get a Slack ping for every form submission

The strongest argument for putting form submissions in Slack is response time. An enquiry that lands in a shared channel gets claimed by whoever is around; the same enquiry in a personal inbox waits for one specific person to open their mail. For sales enquiries especially, the gap between a four-minute reply and a four-hour reply is often the deal.

Create the incoming webhook

1. Create a Slack app at api.slack.com/apps (From scratch, pick your workspace).
2. Enable Incoming Webhooks, then Add New Webhook to Workspace.
3. Pick the channel - a dedicated one like #website-leads beats general, because a channel where every message is a lead can have a simple rule: every message gets an emoji when handled.
4. Copy the webhook URL. Treat it like a password; anyone holding it can post to your channel.

Connect it

In the WebForms dashboard, add Slack as a destination and paste the URL. Submissions arrive as formatted messages: fields in order, submitter email ready to copy, source page and spam score in the footer. There is no code in this step, which is the point - the form itself is unchanged, still plain HTML posting to your endpoint.

<form action="https://send.webforms.to/wft_your_key" method="POST">
  <label for="name">Name</label>
  <input id="name" name="name" type="text" required>

  <label for="email">Email</label>
  <input id="email" name="email" type="email" required>

  <label for="message">Message</label>
  <textarea id="message" name="message" required></textarea>

  <button type="submit">Send</button>
</form>

What makes it stick

• Keep email delivery on in parallel. Slack is for speed; the inbox is the archive that survives a workspace migration.
• Agree on a claimed emoji. The whole triage system is one reaction - anything without it is unhandled.
• Route only what needs speed. Job applications do not benefit from real-time pings; sales enquiries do. Routing rules can split by form or by field value.