WordPress form submissions in Slack, with no plugin

Paste a form into a Custom HTML block with its action pointed at your endpoint, add a Slack destination, and submissions post to the channel without a contact form plugin, a Slack plugin or wp_mail(). Slack delivery is on Pro and Agency.

Setting it up

01Add the form in a Custom HTML block

Edit the page, add a Custom HTML block and paste the form. It works the same in Elementor, Divi or any builder's HTML widget, and your theme's form styles apply automatically.

Custom HTML block

<form action="https://send.webforms.to/wft_your_key" method="POST">
  <p hidden><input name="_gotcha" tabindex="-1" autocomplete="off"></p>
  <label for="name">Name</label>
  <input id="name" name="name" 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>

02Connect Slack
Create an incoming webhook for the channel in Slack and paste it into a Slack destination on the form. Keep an email destination alongside it if you want a copy in an inbox as well.

What is different about WordPress and Slack

Two plugins become zero

The usual route is a contact form plugin plus a Slack add-on for it, each with its own updates and its own attack surface. Here nothing is installed and no PHP runs when someone submits, so there is nothing to patch.

No database rows to lose

Submissions are never written to the WordPress database. They survive a migration, a restore from backup or a hacked site, and the Slack message is not your only record of them.

Caching plugins cannot break it

Page caching sometimes serves a stale nonce to plugin forms and they fail silently. A form posting straight to an endpoint has no nonce and no server round trip through WordPress, so a cached page submits the same as a fresh one.

The full guides cover each side on its own: WordPress setup and Slack as a destination.