Skip to main content

Tutorial

WordPress Slack Integration: Post a Form Submission to a Channel

Post a WordPress form submission to Slack with an incoming webhook. The message template, the conditional filter, and the cases where email is still the better inbox.

A WordPress Slack integration posts the submission into a channel your team already watches. Core Forms does it with Slack’s incoming webhook. There is no Slack app to install inside WordPress and no OAuth step.

I build Core Forms. The Slack integration page is the same action. Email still keeps the record. Slack is the ping.

Email is a bad live inbox for leads. Subject lines collide, the from-address is your own server, and three people reply because nobody could see that the others had. A channel fixes the “who has this” problem. It does not replace the submission stored in WordPress.

Step 1: Make the Slack incoming webhook

In Slack:

  • Click your workspace name → Settings & administration → Manage apps.
  • Search Incoming Webhooks, install it.
  • Click Add to Slack.
  • Pick the channel you want submissions to land in (#leads, #contact, #support, your call).
  • Authorize.
  • Copy the Webhook URL Slack gives you. It looks like https://hooks.slack.com/services/T0/B0/abc123.

That URL is the only auth Slack needs. Keep it secret like a password.

Step 2: Wire the action in Core Forms

In your form’s Actions tab:

  • Add action → Send to Slack.
  • Paste the webhook URL.
  • Compose the message body, and set a username the channel will recognize.

The Send to Slack action in Core Forms with the webhook URL, a message using the NAME, COMPANY and EMAIL variables and the username set to Website leads The Variables row under the message lists every field on the form, so the tokens are one click away.

This is where most setups go wrong. They paste the form data verbatim and end up with a wall of text in the channel. Don’t.

A message the channel will read

Three lines is enough. Who it was, what they wanted, and the one field that decides who replies.

New lead: [NAME] at [COMPANY]
[EMAIL] · [PHONE]
Wants: [INTEREST]

The Variables row under the message lists every field, so you are not guessing the token. Put a username on the message, “Website leads” or the form’s name, so the channel can tell a contact form from a job application.

React with an emoji to claim it. Thread the follow-up. If the channel is noisy, the next section is the fix, not a longer message.

Only ping Slack when it matters

The action can run only when a condition matches. A support form can post to #urgent when the priority field is High and stay quiet otherwise. The same idea is the conditional logic guide.

Do not post every field, every time, to #general. People mute the channel, and then the integration is theater.

When email is the better inbox

Slack is the alert. It is a poor archive. Messages scroll away, workspaces change, and a webhook URL is a secret that leaks if you paste it into a screenshot. The submission in WordPress, and the notification email, are the record you can search in a year.

Use email, or the submissions inbox, when:

  • the message contains something you would not put in a shared channel
  • the team that must reply does not live in Slack
  • you need a thread the customer can answer by email

Discord is the same pattern for a different chat tool. The Discord guide is that setup.

The message format that actually works

Here’s the pattern I use on every client site:

*New {form name} submission*

*From:* [name]
*Email:* [email]
*Reason:* [inquiry]
*Page:* [CF_REFERRER_URL]

*Message:*
[message]

Asterisks make the field labels bold (Slack Markdown). Tokens in [brackets] are Core Forms data variables. The form field values get inlined when the message sends.

Three things to notice:

  1. The first line is the headline. It’s what your teammates skim. Keep it short.
  2. Email is on its own line. Click-to-email works in Slack.
  3. The page URL is in there. So you know whether the lead came from /pricing/ or /contact/.

Use the Slack thread for follow-up

When a teammate claims a lead, they reply in a thread on that message. The whole conversation about that submission stays attached.

This is the actual unlock. Email threading is a hot mess. Slack threads are cheap and obvious.

Set a team norm: react with :eyes: to claim a lead, :white_check_mark: when responded. Two emojis, no process doc, the whole flow visible at a glance.

Conditional posting

Don’t pipe every submission to Slack. Pipe the ones that matter.

In the action’s Conditions section, set:

inquiry equals demo

Now only “demo request” submissions hit Slack. Everything else stays out of the channel. Saves you from “another job application notification at 2am” fatigue.

For a lead-gen site, I usually set:

  • Slack for “demo request” or “high-intent” submissions.
  • Email auto-responder for everything else.
  • Notion as the persistent record for all of it.

Three actions on one form. Each does one thing well.

What this won’t do

Two-way reply. You can’t respond to a Slack message and have it email the lead. You’d need a separate inbox for that. (Front, Help Scout, Missive — pick one.)

Search history beyond Slack’s free retention. If you’re on the free Slack plan, messages older than 90 days are gone. Pair Slack with Notion or Airtable for the actual archive.

File attachments. Slack incoming webhooks don’t accept attachments. If a submission has a file upload, the Slack message will link to the file URL, not embed it. Click through to view.

Test it before the first lead

The Slack action has no test panel, so submit the form once from a draft page and watch the channel. The message arrives with the sample values you typed, which is the fastest way to see the formatting before a visitor does.

The Discord variant

The Discord integration guide covers the Discord side in full, including the 25-field limit on an embed.

The exact same pattern works on Discord. Different webhook URL, slightly different markdown (Discord uses **bold**, Slack uses *bold*), otherwise identical.

If your team’s already in Discord, use Discord. Don’t migrate communities just to wire a form.

The next step

Pick the highest-intent form on your site. Pipe its submissions to Slack with the message format above. Start the team norm of :eyes: to claim.

The shift from “I check the form email when I remember” to “the team triages leads in real-time” happens on the first lead.

Slack is bundled with every Core Forms license. Pricing here.

Build the form. Stop reading.

Every note here came out of a real Core Forms setup. Use code BLACKFRIDAY for 40% off either plan. Ends December 2 (IST).

Black Friday Sale

40% off Core Forms

Forms, polls, surveys, payments, and licensing — every feature, unlimited sites, one plugin.

Copy your code

Those are the after-discount prices. Paste BLACKFRIDAY at checkout to apply it. BLACKFRIDAY40 works too.

Ends December 2 (IST)