The cleanest way to send a webhook when a post is published in WordPress is to hook into the transition_post_status action and fire an HTTP POST using wp_remote_post(). If you want retry logic, execution logs and a visual editor instead of code, a workflow plugin handles all of that in about five minutes. This tutorial covers both paths, including the failure-handling gap that every other guide skips.

We tested both approaches on WordPress 6.5 with PHP 8.2. The code path works on any host.

The plugin path works on shared hosting too, because it queues requests through Action Scheduler rather than firing them synchronously during the publish request. That difference matters more than most tutorials admit.

Before you choose a path, it helps to understand what can go wrong. When WordPress publishes a post, the browser is waiting. If your webhook fires synchronously during that same request and the receiving endpoint takes three seconds to respond, the editor hangs for three seconds.

If the endpoint is down, the webhook fails silently with no log and no retry. Neither the code snippets on most blogs nor the basic plugin guides address this, so we will.

Which Approach Is Right for You?

Path 1: The Code Approach

The correct hook is transition_post_status, not publish_post. The difference is important: publish_post fires on every save to a published post, including updates. transition_post_status lets you check the previous status, so you can fire only on the transition from any status to publish for the first time.

Add this to your theme’s functions.php or, better, a site-specific plugin so it survives theme changes. The WordPress developer documentation for transition_post_status covers all the parameters.

add_action( 'transition_post_status', 'my_send_publish_webhook', 10, 3 );

function my_send_publish_webhook( $new_status, $old_status, $post ) {
    // Fire only on the first publish, not on updates
    if ( $new_status !== 'publish' || $old_status === 'publish' ) {
        return;
    }

    // Restrict to a specific post type if needed
    if ( $post->post_type !== 'post' ) {
        return;
    }

    $payload = wp_json_encode( array(
        'post_id'       => $post->ID,
        'title'         => get_the_title( $post ),
        'url'           => get_permalink( $post ),
        'thumbnail_url' => get_the_post_thumbnail_url( $post, 'full' ),
        'published_at'  => get_the_date( 'c', $post ),
        'categories'    => wp_get_post_categories( $post->ID, array( 'fields' => 'names' ) ),
    ) );

    wp_remote_post( 'https://your-endpoint.example.com/hook', array(
        'body'        => $payload,
        'headers'     => array( 'Content-Type' => 'application/json' ),
        'timeout'     => 5,
        'blocking'    => false, // Non-blocking: does not hold up the editor
    ) );
}

Setting blocking to false is the most important line in that snippet. With blocking => false, WordPress fires the request and immediately moves on.

The editor does not hang while waiting for a response. The trade-off is that you get no response body and no way to detect failure at the point of sending.

Non-blocking solves the latency problem and creates the reliability problem. You cannot have both without a queue.

Firing Only on First Publish, Not on Every Edit

The $old_status === 'publish' check is what prevents the webhook from firing again every time the post is edited after it goes live. Without that guard, updating the title six months later fires the webhook again, which breaks most downstream integrations. This is the most common cause of duplicate webhook deliveries, and it is not mentioned in most tutorials.

Restricting to a Post Type or Category

To fire only for a specific post type, change $post->post_type !== 'post' to match the post type slug you want, for example !== 'product' or !== 'news'. To fire only for posts in a specific category, add a check after the post type guard:

$categories = wp_get_post_categories( $post->ID );
if ( ! in_array( 42, $categories ) ) { // 42 is your category term ID
    return;
}

What the Code Path Does Not Give You

• No retry: if the endpoint returns a 500 or times out, the webhook is lost with no record of the attempt.
• No logs: you have no way to see which posts triggered the webhook, what was sent, or whether it arrived.
• No dry-run testing: you must publish a real post to test, which pollutes your site with test content.
• No visual editing: changing the payload or the endpoint means editing PHP code and redeploying.

For a single low-stakes webhook to a reliable endpoint, those limitations are acceptable. For anything more critical, the next path is worth the five minutes of setup.

Path 2: The No-Code Workflow Approach

Krom Automation is a visual workflow plugin for WordPress. It includes a Post Published trigger and an HTTP Request action in the free version, so this entire workflow costs nothing.

Execution runs through Action Scheduler, which means the webhook fires after the publish request completes, not during it. That solves the synchronous timing problem without any code.

Install the free plugin from the WordPress.org plugin directory. If you have not installed it before, the installation guide walks through the first activation steps.

Step 1: Create a New Workflow

Go to Krom Automation in your WordPress admin sidebar and click Add New Workflow. You will see a blank canvas with a prompt to add a trigger. Click the trigger node to open the trigger selector panel on the right.

Step 2: Set the Trigger to Post Published

In the trigger panel, choose Post from the category list, then select Post Published. You will see configuration options appear below the trigger selector:

• Post type: choose Post, Page, or any custom post type registered on your site.
• Category filter: leave blank to fire for all categories, or enter one or more category slugs to restrict.
• Run once per post: this toggle is on by default and prevents the workflow from firing again if the post is later updated. Leave it on.

The full list of available triggers and their configuration options is documented in the free triggers reference.

Step 3: Add an HTTP Request Action

Click the plus icon below the trigger node to add an action. Choose Integration from the action categories, then select HTTP Request. The action panel opens with these fields:

• URL: paste your destination endpoint URL here.
• Method: select POST.
• Headers: add Content-Type: application/json.
• Body: paste your JSON payload here, using merge tags for dynamic values.

Step 4: Build the Payload with Merge Tags

Merge tags pull live data from the trigger event into any action field. In the body field, build your payload like this:

{
  "post_id": "{{post.id}}",
  "title": "{{post.title}}",
  "url": "{{post.permalink}}",
  "thumbnail_url": "{{post.thumbnail_url}}",
  "published_at": "{{post.published_date}}",
  "author": "{{post.author_name}}"
}

The merge tags documentation lists every available variable for post triggers, including custom field values and taxonomy terms. Click the {} merge tags button in any field to browse available tags without memorising them.

Step 5: Add Conditional Logic (Optional)

If you want the webhook to fire only when a post meets additional conditions, such as being in a specific category or having a certain custom field value, click the branching icon on the action node to add a condition. The conditions and branching documentation covers the full logic options. Connect the HTTP Request action to the Yes path and the workflow ends on the No path with no action taken.

Step 6: Test with the Workflow Simulator

Before going live, click the Simulate button in the top toolbar. The simulator runs the workflow with real post data and shows you exactly what would have been sent to your endpoint, including the resolved merge tag values, without actually firing the HTTP request. This is covered in the workflow simulator documentation.

Once the simulated payload looks correct, toggle the workflow to Active and publish a test post. The execution log will show the request status, the response code from your endpoint, and each step’s outcome.

A webhook that fails silently is worse than no webhook at all. At least when nothing is configured, you know nothing is running.

What Happens When the Endpoint Is Down

This is the question every other guide skips. When you fire a webhook synchronously in PHP and the endpoint returns a 503, the request fails and nothing happens.

You will not know unless you are actively watching server logs. For teams sending post data to a CRM, a Slack channel, or a build pipeline, that silent failure can go unnoticed for days.

The workflow plugin approach handles this differently. Failed HTTP Request actions are logged in the execution history with the response code and error message.

Automatic retry kicks in with configurable backoff, so a temporary outage at the endpoint does not lose the event. Email notifications alert you when a workflow fails, and the analytics dashboard shows a failed execution count so trends are visible at a glance.

If you are using the code path and need similar reliability, you can defer the webhook using wp_schedule_single_event() to push it off the publish request and onto the next WP-Cron pass. The WordPress developer reference for wp_schedule_single_event explains the parameters. This adds async behaviour but still gives you no retry logic or logs without building them yourself.

Sending to Slack or Discord

For Slack and Discord, the HTTP Request action works with their incoming webhook URLs. Format the payload to match the channel’s expected structure. Slack expects a JSON body with a text key or a blocks array.

Discord expects a content key. The messaging integrations documentation shows the exact payload structure for both platforms.

If you also want to notify email subscribers when a post is published, our guide on emailing subscribers when a new post is published covers that workflow alongside the webhook setup.

Common Failure Modes and Fixes

What Gets Sent: A Reference Payload

This is the payload structure we use in production for a standard blog post notification. It covers the fields most downstream services actually need.

{
  "post_id": 1842,
  "title": "How to Configure Redis on WordPress",
  "url": "https://example.com/configure-redis-wordpress/",
  "thumbnail_url": "https://example.com/wp-content/uploads/redis-cover.jpg",
  "excerpt": "A short plain-text excerpt from the post.",
  "author_name": "Sakil",
  "published_at": "2026-04-14T09:00:00+00:00",
  "categories": ["Performance", "Hosting"],
  "tags": ["redis", "caching", "server"]
}

Custom fields can be added to this payload using the get_post_meta() function in code, or via post meta merge tags in the workflow builder. If your destination service requires HMAC signature verification for security, that is a Pro feature covered in the incoming webhook receiver documentation.

Most webhook tutorials give you a snippet that works in development and fails quietly in production. The gap is always retry logic and observability, not the initial send.

Also Worth Knowing About

Pollify is wpRigel’s poll, survey and quiz plugin for WordPress. It builds polls as native Gutenberg blocks, so there are no shortcodes to paste and no separate admin interface to learn. If you are publishing content and want to gather reader feedback inline, it fits into the same post-publish workflow.

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K to jump anywhere in the dashboard, search posts, users and products, and run admin actions without navigating menus. It is the only WordPress command palette with real WooCommerce order, product and customer commands built in.

Next Steps

If you are starting with the code path, copy the snippet above, replace the endpoint URL, and publish a test post on a staging site first. If you need retry logic, failure notifications or the ability to test without publishing real content, the free plugin is the faster path and costs nothing to try. The step-by-step workflow builder guide covers the full setup from first trigger to active workflow in one place.

Try Krom Automation free on WordPress.org

Frequently Asked Questions

Why is my WordPress publish webhook firing multiple times for the same post?

The most common cause is using the publish_post hook without checking whether the post was already published. Every time the post is updated after going live, that hook fires again.

Switch to transition_post_status and add an $old_status === 'publish' guard to skip anything that was already in the published state. A second cause is autosave or revision saves triggering the same action, which a transient lock keyed to the post ID will prevent.

How do I send a webhook only for specific post types or categories?

In the code path, add a $post->post_type check inside the callback and return early if the type does not match. For category filtering, use wp_get_post_categories() and check whether the returned term IDs include your target. In the workflow builder, the Post Published trigger has a post type selector and a category filter field built into the trigger configuration panel, so no code is needed.

What happens to the webhook if the receiving endpoint is down?

With a plain PHP snippet and blocking => false, the request is sent and forgotten. If the endpoint returns an error or is unreachable, the event is lost with no log.

With a queued workflow plugin, the failed attempt is logged with the response code, automatic retry runs with backoff, and an email notification is sent after a configurable number of failures. For any integration where losing the event matters, the queued approach is the correct one.

How do I add the post thumbnail URL and custom fields to the webhook payload?

In the code path, use get_the_post_thumbnail_url( $post, 'full' ) for the thumbnail and get_post_meta( $post->ID, 'your_field_key', true ) for custom fields, then include both in the array passed to wp_json_encode(). In the workflow builder, thumbnail URL and post meta values are available as merge tags. Click the {} merge tags button in the HTTP Request body field to browse all available variables for the Post Published trigger.

Can I test a WordPress publish webhook without publishing a real post?

With the code path, no. You must publish a real post or temporarily hook into a different action for testing.

With the workflow plugin, the built-in simulator runs the full workflow against real post data and shows the resolved payload and simulated action output without firing the HTTP request or touching any external service. This means you can verify the payload structure before the workflow goes active.

You can send Contact Form 7 entries to Google Sheets automatically, and the setup takes under 15 minutes with no code required. The method we cover here uses a WordPress-native workflow plugin to connect the form submission event to a Google Sheets action, so every new entry appends a row in real time.

Most tutorials stop the moment the data lands in Sheets. This one does not. We cover setup, field mapping, the three failure modes that break the sync silently, and what you can automate downstream once the entries are flowing.

What You Need Before You Start

Before touching any settings, confirm you have all four of these in place. Missing any one of them is the most common reason the integration fails silently on the first test submission.

• Contact Form 7 installed and active, with at least one published form that has been tested and is receiving submissions correctly.
• A Google account with a Sheets file already created. The sheet should have a header row matching the fields you plan to capture.
• Krom Automation Pro installed, since Google Sheets is a Pro integration. The free version covers 16 triggers and 21 actions, but Google Sheets sync requires Pro.
• Google API credentials: a Client ID and Client Secret from Google Cloud Console, used to authorise the connection via OAuth 2.0.

The Google Sheets and Google Calendar integration documentation covers the credential setup step by step, including exactly which scopes to enable in Google Cloud Console. Follow that before proceeding here.

Step 1: Install and Connect the Plugin

Install Krom Automation from the WordPress.org plugin directory, then activate the Pro licence alongside it. Pro requires the free plugin active as a base layer. Once both are active, you will see a “Krom Automation” menu item in your WordPress admin sidebar.

Go to Krom Automation Settings Integrations and locate the Google Sheets tile. Click Connect, paste your Google Client ID and Client Secret, then click Authorise. Google will prompt you to select an account and grant access.

After approval, the tile shows a green “Connected” badge. If you see an error at this stage, double-check that your OAuth redirect URI in Google Cloud Console matches your site’s URL exactly, including the trailing slash.

An OAuth mismatch on the redirect URI is the single most common reason the Google connection fails. It looks like a permissions error but it is a URL typo.

Step 2: Create the Workflow

Go to Krom Automation Workflows Add New. You will land on the visual canvas, built on a drag-and-drop interface. The canvas starts with a trigger node waiting to be configured.

Click the trigger node and search for Contact Form 7: Form Submitted. Select it. A panel opens on the right where you choose which form triggers this workflow.

You can select a specific form by name, or set it to fire on any CF7 submission. For most setups, selecting the specific form is cleaner and avoids unintended rows from other forms.

The full list of available triggers, including this one, is documented in the Contact Form 7 integration reference.

Next, click the plus icon below the trigger node to add an action. Search for Google Sheets: Append Row.

Select it. The action panel asks you to:

1. Choose the Google account you connected in Step 1.
2. Select the Spreadsheet from a dropdown populated from your Google Drive.
3. Select the Sheet tab within that spreadsheet.
4. Map each column to a value using merge tags.

Step 3: Map Your Form Fields to Sheet Columns

Field mapping is where most tutorials gloss over the detail that actually matters. Each column in your sheet corresponds to one mapped value in the action panel. You set the value using merge tags, which pull live data from the form submission.

Here is a worked example for a standard contact form with four fields:

The merge tag format follows the pattern {{cf7.field-name}}, where field-name is the name attribute of the input in your CF7 form editor, not the label the visitor sees. Check your CF7 form in the Form tab to confirm the exact field names. A full reference for merge tag syntax is in the merge tags documentation.

Adding a timestamp column is worth doing even if you do not plan to use it immediately. Sorting or filtering by submission date becomes useful the moment you have more than a few dozen rows.

Step 4: Test Before Going Live

Save the workflow in draft mode first. Use the built-in workflow simulator to do a dry run: it fires the trigger logic without actually appending a row to your sheet.

This catches mapping errors and missing fields without creating junk data. The simulator is documented in the testing and simulator guide.

Once the simulator passes, set the workflow to Active and submit a real test entry through your Contact Form 7 form. Check your Google Sheet within 10 to 30 seconds. You should see a new row with all mapped fields populated.

If the row does not appear, go to Krom Automation Execution Logs and check the run for that submission. The per-step audit trail shows exactly which step failed and why.

A workflow failing silently 20 percent of the time looks identical to a working one until you check the execution log. Build the habit of checking it after the first real submission, not just after the test.

Troubleshooting: Why Contact Form 7 Data Is Not Reaching Google Sheets

These are the three failure modes we see most often, in order of how frequently they occur. Work through them in this sequence rather than jumping to re-authentication, which is rarely the actual problem.

1. Wrong Field Name in the Merge Tag

The merge tag {{cf7.your-email}} only works if your CF7 form has an input with name="your-email". If you renamed the field or used a custom name, the tag returns blank and the sheet column is empty. Open your CF7 form editor, click each field, and confirm the Name attribute matches what you typed in the merge tag exactly, including hyphens and capitalisation.

2. OAuth Token Expired or Revoked

Google OAuth tokens expire. If submissions were syncing and then stopped after a few weeks, go to Krom Automation Settings Integrations Google Sheets and check whether the account still shows “Connected”.

If it shows “Disconnected” or “Error”, click Reconnect and go through the OAuth flow again. This takes under 2 minutes and restores the sync immediately.

3. Spam Submissions Filling the Sheet

Contact Form 7 with no spam protection passes every submission to the workflow trigger, including bot entries. If your sheet is filling with obvious spam, add a conditional branch to the workflow that checks whether the email field contains a real-looking value, or enable reCAPTCHA in your CF7 form settings. Filtering at the form level is cleaner than filtering in the workflow, but both work.

What to Do After the Data Lands in Sheets

This is the part almost no tutorial covers, and it is where the real value of the integration appears. Appending a row is not the end of the workflow; it can be one node in a longer chain.

Here are four things you can trigger from the same form submission event, running in parallel with the Sheets append:

• Send a Slack notification to your team channel with the submitter’s name, email and message. The Contact Form 7 to Slack guide covers this exact setup, and it can run as a second action node on the same workflow.
• Add the contact to your CRM or email list. If you use FluentCRM, the FluentCRM integration lets you create or update a contact from the same trigger. Mailchimp, ActiveCampaign, MailerLite and ConvertKit all have equivalent action nodes.
• Send a confirmation email to the submitter using the Send Email action or the visual email builder for a formatted message. This runs automatically without touching CF7’s own mail settings.
• Notify the admin of high-priority submissions by adding a condition node that checks for a keyword in the message field. If it matches, route to a separate Slack channel or send an SMS via Twilio. The messaging integrations reference covers Twilio setup.

Each of these runs from the same “CF7 Form Submitted” trigger. You do not need separate workflows for each destination. Add action nodes on the canvas, and the workflow handles all of them in sequence every time someone submits the form.

Sending data to Sheets is a storage decision. What you do with that data after is where the time savings actually accumulate.

Cost and Licensing: What Is Actually Free

Several plugins on WordPress.org advertise “free and unlimited” Google Sheets sync for Contact Form 7. The honest picture is more nuanced. Here is how the main approaches compare on dimensions that matter for a real decision:

The dedicated plugin approach works if Sheets is your only destination. The moment you want to also notify Slack, tag a contact in FluentCRM, or send a confirmation email, you need either a second plugin or an automation layer anyway. Starting with a workflow plugin means you only configure the Google connection once and add destinations as nodes.

Zapier prices shown are as of September 2026 and reflect the Professional plan at approximately $240 per year for 750 tasks per month with task-based billing. Overages apply above that threshold. There is no Zapier lifetime plan.

For a deeper look at what WordPress automation actually costs across different tools and configurations, the WordPress automation cost breakdown is worth reading before committing to any paid tier.

Other Tools Worth Knowing About

Pollify is wpRigel’s poll, survey and quiz plugin for WordPress. It is built as native Gutenberg blocks, so you create a poll exactly like you write a paragraph.

No shortcodes, no separate interface, no embedding step. If you are collecting structured opinion data alongside contact form data, Pollify handles the survey side and outputs results you can export directly.

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K from anywhere in the dashboard and you can search posts, jump to settings, manage WooCommerce orders, and run admin actions without clicking through menus. Teams managing high-volume sites find it cuts navigation time considerably, particularly for order lookup and status changes.

Next Steps

If you are running the setup described above, the Contact Form 7 integration documentation is the right reference to keep open during configuration. It lists every available trigger and shows which merge tags each one exposes.

For the Google Sheets side, the Google Sheets integration docs cover OAuth credential setup, column mapping, and the append versus update row distinction. Once the basic sync is working, revisit the workflow canvas and consider which post-submission actions would save your team the most time per week.

Try Krom Automation free on WordPress.org to start building workflows. The Pro upgrade, which includes Google Sheets, starts at $69 a year. You can compare all plans and pricing before committing, and every Pro plan includes a 14-day money-back guarantee.

Frequently Asked Questions

Does Contact Form 7 automatically send submissions to Google Sheets?

Not by default. CF7 stores submissions in the database and sends email notifications, but has no built-in Google Sheets export. You need either a dedicated connector plugin or a workflow automation plugin to route submissions to a sheet automatically on every submission.

How do I map Contact Form 7 fields to Google Sheets columns?

In the Google Sheets action node, each column maps to a merge tag in the format {{cf7.field-name}}, where field-name is the Name attribute of the input in your CF7 form editor. The column order in your action node should match the column order in your sheet header row. Adding a timestamp column using {{workflow.triggered_at}} is recommended even if you do not use it immediately.

Why is my Contact Form 7 data not showing up in Google Sheets?

The three most common causes are: a merge tag referencing a field name that does not match the actual CF7 input name, an expired or revoked Google OAuth token, and a workflow that is saved but not set to Active. Check the execution log first, as it shows the exact step and error message rather than requiring you to guess.

Can I connect one Contact Form 7 form to multiple Google Sheets?

Yes. Add multiple Google Sheets: Append Row action nodes to the same workflow, each pointing to a different spreadsheet or tab.

All actions run from the single trigger. You can also add conditions between nodes so certain submissions route to one sheet and others route to a different one based on field values.

Is the Contact Form 7 to Google Sheets integration really free?

It depends on which tool you use. Some dedicated connector plugins offer a free tier with no run caps, but cover only the Sheets destination with no further automation.

Workflow plugins that also handle post-submission actions, like CRM tagging or Slack alerts, typically require a paid plan. The Google Sheets action in Krom Automation requires Pro, which starts at $69 per year with no per-submission fees and no run limits.

You can send Contact Form 7 entries to a Slack channel without a paid third-party service. The three practical routes are: a visual WordPress workflow builder, a lightweight dedicated plugin, or a custom function using CF7’s own wpcf7_mail_sent hook and WordPress’s built-in wp_remote_post(). Each takes under fifteen minutes to configure, and none requires a Zapier account or a recurring automation subscription.

This tutorial covers all three methods in order of effort. Work through the decision table first, then jump to the section that matches your setup. We tested each approach on WordPress 6.5 with Contact Form 7 5.9 and confirmed that Slack notifications arrived within two seconds of a form submission.

Which Method Is Right for You?

The right choice depends on how many automations you run, whether you want a visual audit trail, and how comfortable you are editing functions.php. Use this table before reading further.

Step 1: Create a Slack Incoming Webhook

Every method in this guide requires a Slack Incoming Webhook URL. This is a unique endpoint Slack generates for your workspace. When your WordPress site posts data to that URL, Slack delivers it as a message in the channel you specify.

Here is exactly what you will see on screen:

1. Go to api.slack.com/apps and click Create New App.
2. Choose From scratch, name the app (e.g. “CF7 Notifications”), and select your workspace.
3. In the left sidebar, click Incoming Webhooks, then toggle Activate Incoming Webhooks to On.
4. Scroll down and click Add New Webhook to Workspace.
5. Choose the channel you want to receive notifications, click Allow.
6. Copy the webhook URL. It begins with https://hooks.slack.com/services/.

Keep that URL in a text file. You will paste it into whichever method you choose below. The official Slack Incoming Webhooks documentation covers rate limits (one message per second per webhook) and payload formatting in detail.

A Slack webhook URL is a secret. Anyone with it can post to your channel. Store it in your WordPress options table or an environment variable, never in a public repository.

Method A: Visual Workflow Builder (Recommended for Most Sites)

This is the approach we use and recommend for sites that handle more than a handful of automations. You build the workflow on a drag-and-drop canvas, which means every trigger, action, and condition is visible, editable, and logged without touching any code.

Browse the full feature list to see what else the workflow builder handles beyond Slack notifications.

Install and Activate the Plugin

1. In your WordPress dashboard, go to Plugins Add New and search for Krom Automation.
2. Click Install Now, then Activate. Alternatively, download it free from WordPress.org and upload the ZIP under Plugins Add New Upload Plugin.
3. After activation, a Krom item appears in the left admin menu.

Connect Slack as a Messaging Integration

1. Go to Krom Integrations and find the Slack card.
2. Paste your Incoming Webhook URL into the field provided.
3. Click Test Connection. If the connection is valid, a test message arrives in your Slack channel within a few seconds.
4. Save the integration.

The full setup is documented in the messaging integrations reference for Slack, Discord, Twilio, and Telegram, including how to configure multiple webhooks for different channels.

Build the CF7 Workflow

1. Go to Krom Workflows and click New Workflow.
2. On the canvas, click the trigger node and search for Contact Form 7: Form Submitted. Select the specific form you want to watch, or leave it set to “Any form” to catch all submissions.
3. Click the plus icon below the trigger node to add an action. Search for Send Slack Message.
4. In the action panel, select the Slack integration you just connected and choose the target channel.
5. Write your message. Use merge tags to inject live form data. For example: New enquiry from {{cf7.your-name}}. Email: {{cf7.your-email}}. Message: {{cf7.your-message}}.
6. Click Save, then toggle the workflow to Active.

Submit a test entry through your CF7 form. The notification should appear in Slack within two to three seconds. You can check the execution log under Krom Logs to confirm the workflow ran and see the exact payload that was sent.

For full details on the Contact Form 7 trigger and the fields it exposes, see the Contact Form 7 integration documentation, which lists every available merge tag and covers multi-form setups.

Add Conditional Routing (Optional)

If you want VIP leads routed to #sales and general enquiries to #general, add a condition node between the trigger and the action. Set the condition to check a form field value (such as “Budget” or a checkbox), then connect each branch to its own Slack action pointing at the appropriate channel.

The conditions and branching documentation explains Yes/No path logic in detail, including how to match partial strings and combine multiple conditions.

Conditional routing is where a visual canvas earns its place. Trying to replicate branching logic in functions.php takes four times as long and is invisible when something breaks.

Method B: Dedicated CF7 Slack Plugin

If Slack notifications are the only automation your site needs, a dedicated plugin is a lighter option. Several exist on WordPress.org. The setup pattern is identical across all of them:

1. Install the plugin and activate it.
2. Go to the plugin’s settings page, usually under Contact CF7 Slack or Settings CF7 to Slack.
3. Paste your Slack Incoming Webhook URL.
4. Select which forms trigger notifications.
5. Configure the message template using the plugin’s placeholder syntax.
6. Save and submit a test entry.

The trade-off is narrow functionality. These plugins handle one job well.

The moment you need a second action (logging to a spreadsheet, tagging a CRM contact, sending a follow-up email), you install a second plugin. Three automations can mean three plugins, three settings screens, and three failure points.

Method C: Custom Code via wpcf7_mail_sent

This approach adds zero plugins. It uses Contact Form 7’s own action hook, which fires after a form submission passes validation and sends its mail, and WordPress’s native HTTP API to POST data to Slack. According to the Contact Form 7 developer documentation, wpcf7_mail_sent receives the WPCF7_ContactForm object, giving you access to all submitted field values.

Add the following to your theme’s functions.php or a site-specific plugin:

add_action( 'wpcf7_mail_sent', 'send_cf7_to_slack' );

function send_cf7_to_slack( $contact_form ) {
    $webhook_url = 'https://hooks.slack.com/services/YOUR/WEBHOOK/URL';
    $submission  = WPCF7_Submission::get_instance();

    if ( ! $submission ) {
        return;
    }

    $data    = $submission->get_posted_data();
    $name    = sanitize_text_field( $data['your-name'] ?? 'Unknown' );
    $email   = sanitize_email( $data['your-email'] ?? '' );
    $message = sanitize_textarea_field( $data['your-message'] ?? '' );

    $payload = wp_json_encode( [
        'text' => "*New CF7 Submission*\nName: {$name}\nEmail: {$email}\nMessage: {$message}",
    ] );

    wp_remote_post( $webhook_url, [
        'body'    => $payload,
        'headers' => [ 'Content-Type' => 'application/json' ],
        'timeout' => 10,
    ] );
}

Replace the field names (your-name, your-email, your-message) with the actual names from your CF7 form. You can find these under Contact Contact Forms Edit Form. The name attribute inside each field shortcode is what you need.

This runs synchronously on the page load that processes the form. On a site with very slow Slack responses (rare but possible), a 10-second timeout could delay the thank-you message. Setting blocking to false in wp_remote_post() makes the call fire-and-forget, which avoids that risk at the cost of losing the response for debugging.

What Gets Sent: Field Mapping Reference

Regardless of method, this is the data available from a Contact Form 7 submission and where it lands in a Slack message:

Custom field names you add to your form are immediately accessible using the same pattern. A field named company becomes {{cf7.company}} in merge tags or $data['company'] in code.

Troubleshooting: Why Slack Notifications Fail

This is the section most tutorials skip. Here are the four failure modes we have seen in practice, ordered by how often they occur:

1. The webhook URL is invalid or revoked

Slack returns a 400 Bad Request or invalid_payload error. The most common cause is copying the webhook URL with a trailing space, or regenerating the webhook in Slack without updating WordPress. Go to api.slack.com/apps, find your app, navigate to Incoming Webhooks, and confirm the URL matches what is stored in your plugin or code.

2. The form did not actually submit

CF7’s wpcf7_mail_sent hook only fires when the form passes validation AND the mail action succeeds. If CF7’s own email is failing (misconfigured SMTP, blocked by hosting), the Slack notification will not fire either. Check Contact Integration Additional Settings and use CF7’s built-in mail debugging, or install WP Mail Log to confirm whether CF7 emails are being sent at all.

3. Spam filter interception

CF7’s Akismet integration can silently reject a submission before the hook fires. If you are testing with data that looks like spam (short messages, common test phrases), Akismet may drop it. Use realistic test data: a real-looking name, a valid email address, a sentence-length message.

4. WP-Cron delay on low-traffic sites

If your workflow builder processes actions via Action Scheduler (a background queue), and your site receives fewer than a few visits per hour, WP-Cron may not fire promptly. The fix is to disable the default WP-Cron in wp-config.php and configure a real server cron to call wp-cron.php every minute.

Your hosting provider’s documentation will have the exact command. This is also covered in the guide to testing automations before they go live.

A workflow that fires on 80% of submissions is not a workflow. It is a guessing game. Always check execution logs after setup, not just the first test.

Year-One Cost Comparison

This table covers the realistic first-year cost for each approach, including your time at an estimated developer rate of $75 per hour.

The custom code route looks cheapest until you factor in debugging time. A silent failure in a functions.php hook has no log, no retry, and no alert.

You find out when a client asks why they received no follow-up. The visual builder’s execution log alone is worth the additional six minutes of setup.

Extending the Workflow Beyond Slack

Once CF7 is triggering a workflow, adding a second action costs nothing and takes about ninety seconds. Common combinations we see on agency sites:

• Send to Slack AND add the submitter as a contact in FluentCRM (see the FluentCRM integration docs).
• Send to Slack AND log the row to Google Sheets for monthly reporting (see the Google Sheets integration docs).
• Send to Slack AND subscribe the user to a Mailchimp audience (see the Mailchimp integration docs).
• Route to different Slack channels based on which CF7 form was submitted, using conditional branching.

If you are also routing WooCommerce orders to Slack, the same workflow builder handles both. The guide to WooCommerce order notifications in Slack covers the order-specific setup alongside form notifications.

For sites already using other form plugins, the same pattern applies. The workflow builder also supports Gravity Forms, WPForms, Fluent Forms, Elementor Forms, and Ninja Forms with the same trigger-and-action structure.

Other Tools from wpRigel Worth Knowing About

Pollify is a Gutenberg-native poll, survey and quiz plugin. Polls are built as real blocks inside the editor, so there are no shortcodes to paste and no separate dashboard to learn. It suits content sites and community platforms that want audience feedback without a separate SaaS subscription.

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K to jump anywhere, search posts, users, and settings, and run admin actions without clicking through menus. It is the only WordPress command palette with genuine WooCommerce depth: orders, products, and customers are all searchable and editable from the palette.

Next Steps

If you are setting up Slack notifications for one form and nothing else, any of the three methods works. If you have more than one automation on this site, or you expect to add more within the next six months, the visual workflow builder pays back its setup time within the first debugging session it saves you. Start with the free version, which includes the CF7 trigger, the Slack action, merge tags, and execution logging at no cost.

Try Krom Automation free on WordPress.org

Frequently Asked Questions

Does Contact Form 7 have a built-in Slack integration?

No. CF7 handles form capture and email delivery natively, but has no built-in Slack connection. You need either a plugin, a workflow builder, or custom code using the wpcf7_mail_sent hook to bridge the two.

Can I send different CF7 fields to different Slack channels?

Yes, using conditional branching in a visual workflow builder. You set a condition on a specific field value (such as a dropdown selection or a budget range), then connect each branch to a separate Slack action pointing at a different channel. This is not possible with most dedicated CF7 Slack plugins, which send all submissions to one channel.

Why is my CF7 not sending notifications to Slack even though the form submits?

The most common causes are: an invalid or revoked webhook URL, CF7’s own mail action failing before the hook fires, or a spam filter (usually Akismet) rejecting the submission silently. Check your execution log if you are using a workflow builder, or add temporary error_log() calls if you are using custom code, to isolate which step is failing.

Is there a free way to do this without Zapier?

Yes. The custom code method is entirely free and has no run limits.

A visual workflow builder also offers a free tier with the CF7 trigger and Slack action included. Zapier’s Professional plan costs around $240 per year as of September 2026, with task-based billing that adds charges if you exceed 750 tasks per month.

Can I notify a specific Slack user (not a channel) when a CF7 form is submitted?

Slack’s Incoming Webhooks post to a channel, not directly to a person. The practical approach is to post to a private channel where only that person is a member, or include an @mention in the message body (e.g.

@jane.smith New lead received). Slack will then send Jane a notification from within the channel.

WordPress sends an admin notification email the moment a user registers, but the default setup is fragile: it goes to one address, carries no context, and fails silently when your hosting blocks outgoing mail. This guide covers every method for getting reliable registration alerts, from fixing the built-in email to routing conditional notifications to different team members based on the role a user receives.

We tested each approach on a standard WordPress 6.5 install and on a WooCommerce site with three staff roles. The results are below, in order of how much they actually fix.

How WordPress Registration Notifications Work by Default

WordPress fires the register_new_user() function when someone completes the registration form. That function calls wp_new_user_notification(), which sends two emails: one to the new user with a password setup link, and one to the site admin email address set under Settings > General > Administration Email Address.

The admin email is a single address. If your site has 5 staff members who all need to know about new registrations, only one of them gets the alert.

That is the first problem. The second is deliverability: on most shared hosting, WordPress sends email through PHP mail, which major providers treat as spam.

A registration notification that lands in spam is functionally identical to no notification at all. Fix delivery before you fix anything else.

Here is what the default notification does and does not include:

• Sends to: the single admin email in Settings > General
• Contains: username, email address, and a link to the user’s profile
• Does not include: user role, registration source, IP address, or any custom field data
• Delivery method: PHP mail, unverified, no DKIM or SPF alignment by default
• Failure behaviour: silent, no retry, no log entry

Step 1, Confirm the Default Notification Is On

Go to Settings > General in your WordPress admin. Check that Administration Email Address contains a working address you actually monitor. That is the only place the default notification can be controlled without code or a plugin.

WordPress does not provide a toggle to turn the admin notification on or off from the Settings screen. The email fires unconditionally unless something in your setup suppresses it.

Check whether any plugin on the site is calling remove_action( 'register_new_user', 'wp_new_user_notification' ) or filtering wp_new_user_notification_email_admin to return false. A security or membership plugin sometimes does this silently.

If the address is correct and nothing is suppressing the hook, move immediately to the delivery problem below. That is where most missing notifications actually fail.

Step 2, Fix Email Delivery First

This step resolves the majority of missing notification complaints. WordPress’s built-in PHP mail has no authentication layer. Gmail, Outlook and most business mail servers reject it or route it to spam, because the sending IP is a shared hosting server with no relationship to your domain.

The fix is SMTP. Install a plugin like WP Mail SMTP and point it at a transactional email service.

We use Postmark in our own setup, but Mailgun, SendGrid and Brevo all work. Any of them gives you:

• Proper DKIM and SPF alignment, so the mail passes authentication checks
• A sending IP with a reputation, not a shared hosting pool
• A delivery log so you can confirm whether the email was sent and whether it bounced
• Retry on soft bounce, rather than WordPress’s fire-and-forget approach

The WordPress.org documentation on the wp_mail() function explains what the function does and does not handle. It does not handle SMTP routing. That is your plugin’s job.

After switching to SMTP, register a test account and check the transactional log. If the email now shows as delivered, the problem was always delivery. If it still does not arrive, move to the next step.

Step 3, Send Notifications to Multiple or Different Email Addresses

The default notification goes to one address. Changing it to a different address or adding more recipients requires either a short code snippet or a plugin that handles it without touching functions.php.

Option A: A Code Snippet

Add this to your site using a snippet manager like Code Snippets. Replace the two addresses with the ones you need:

add_filter( 'wp_new_user_notification_email_admin', function( $email, $user, $blogname ) {
    $email['to'] = 'manager@example.com, team@example.com';
    return $email;
}, 10, 3 );

This filter was added in WordPress 4.9 and is documented on the official developer reference. The to field accepts a comma-separated string of addresses, so you can notify as many recipients as you need from a single filter.

The limitation is that this sends the same email to everyone. If you need different content or different recipients based on the user’s role, you need conditional logic, which Option B covers.

Option B: A Visual Workflow

If you want to avoid touching code, or if you need logic the filter cannot express (for example, notify the sales manager only when a vendor role registers, and notify support only when a customer role registers), a visual workflow handles this cleanly.

The approach we use is a User Registered trigger with a conditional branch. The Yes path fires when a condition matches, the No path handles everything else.

Each path ends in a Send Email action with its own recipient and body. No code, no fragile filter stacking, and you can test the logic before it goes live using the workflow simulator.

The full setup for a welcome email using the same trigger is documented in the first workflow guide, which you can follow alongside this tutorial.

Step 4, Build a Conditional Registration Notification

This is the gap none of the competing guides address. The default filter sends the same alert to the same address regardless of context. The workflow approach lets you route based on any user attribute available at registration time.

Here is the exact setup we tested, using Krom Automation:

1. Install the plugin from the WordPress.org plugin directory. Activate it.
2. Go to Krom Automation > Workflows > Add New. You will see a blank canvas.
3. Click Add Trigger and select User Registered. This trigger fires the moment WordPress completes registration.
4. Click Add Condition and set the condition to User Role equals Vendor. The canvas splits into a Yes branch and a No branch.
5. On the Yes branch, add a Send Email action. Set the recipient to your sales manager’s address. In the subject and body, use merge tags to pull in the user’s display name, email, and role. For example: {{user.display_name}} and {{user.email}}.
6. On the No branch, add a second Send Email action pointing to your support inbox, with a body suited to standard registrations.
7. Save the workflow and toggle it active.

The workflow fires in the background via Action Scheduler, so registration page performance is not affected. Execution logs give you a per-step audit trail for every registration, so you can see exactly which branch fired and what was sent.

The conditions and branching documentation covers every available condition type, including user meta fields set by membership plugins and WooCommerce customer data.

Conditional routing is not a premium feature reserved for enterprise tools. It belongs in the default registration setup for any site with more than one staff role.

What Each Approach Actually Costs You

The free tier covers the User Registered trigger, conditional branching, the Send Email action, merge tags, and execution logging. You do not need Pro for the setup described in Step 4. Pro adds richer trigger data and additional actions like Slack, Discord, and SMS via Twilio, which is useful if your team does not monitor email reliably during peak hours.

Extending Registration Notifications Beyond Email

Email is the obvious channel but often not the fastest. If your team uses Slack, you can add a Slack message action to the same workflow that sends the admin email.

The message arrives in under 2 seconds in our testing. For high-value registrations (for example, a new vendor on a marketplace), that speed difference matters.

If your registration flow runs through a form plugin rather than the native WordPress form, the trigger changes. For Gravity Forms, the relevant setup is in the Gravity Forms integration documentation.

For WPForms, see the WPForms integration documentation. Both give you access to form field data at trigger time, so you can route based on what the user actually filled in, not just their assigned role.

If your site uses a membership plugin and registration flows through it rather than through WordPress core, check whether the plugin fires its own hook. MemberPress, for example, fires on subscription creation rather than user registration. The MemberPress integration handles that correctly.

You might also want to extend what happens after a registration notification: adding the user to a CRM, subscribing them to an email list, or tagging them in FluentCRM. The FluentCRM integration and the Mailchimp integration both connect to the same User Registered trigger, so a single workflow can notify your team and start the onboarding sequence at the same time.

One registration event can notify three team members, tag the user in a CRM, and add them to a welcome sequence. That is not a complicated setup. It takes about 20 minutes on a blank canvas.

Common Reasons Registration Notifications Stop Working

Work through these in order. Skipping ahead wastes time if the problem is actually step one:

1. Delivery failure: Check your transactional mail log or SMTP plugin log first. If the email was sent but not received, the problem is spam filtering or an authentication failure, not WordPress configuration.
2. A plugin suppressing the hook: Security plugins, membership plugins, and some caching plugins occasionally remove the default notification hook. Search your active plugins for calls to remove_action on register_new_user or wp_new_user_notification.
3. The admin email address is wrong: Check Settings > General > Administration Email Address. WordPress requires you to confirm a change to this address via a verification link. If you updated it recently and did not click the link, it reverted.
4. Custom registration forms bypassing core: Forms built with WPForms, Gravity Forms, or Elementor sometimes create users directly via the REST API or a custom handler, skipping register_new_user() entirely. In that case, the core notification never fires. Use the form plugin’s own notification settings or a form-specific trigger instead.
5. User registration is disabled: Go to Settings > General and confirm Anyone can register is checked. If registration is off, no notification fires because no registrations occur.

Disabling Admin Notifications Without Breaking User Notifications

A common but overlooked need: you want the new user to receive their password email, but you do not want the admin alert. On a high-volume membership site that registers hundreds of users a day, the default admin notification becomes noise rather than signal.

The cleanest approach is a one-line filter. Add this to a snippet:

add_filter( 'wp_new_user_notification_email_admin', '__return_false' );

This returns false for the admin email only. The user still receives their password setup email. The WooCommerce documentation notes a similar pattern for order notification suppression, which gives you a sense of how widely this filter approach is used across the WordPress ecosystem.

If you are using a visual workflow for notifications, simply do not include a Send Email action directed at the admin. The workflow can handle the user-facing email and leave the admin untouched.

Also from wpRigel

Pollify is a Gutenberg-native poll, survey, and quiz plugin. Polls are built directly inside the block editor as native blocks with no shortcodes to paste, which makes adding audience feedback to any post or page a two-minute task rather than a configuration exercise in a separate interface.

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl and K to search anything, navigate anywhere, and run admin actions without clicking through menus. It is the only command palette with real WooCommerce order, product, and customer commands built in, which makes it genuinely useful on busy store sites rather than just a convenience shortcut.

Next Steps

If registration emails are missing, start with SMTP and work through the five-point checklist above. If the core email works but you need conditional routing or multiple recipients, the visual workflow approach in Step 4 takes about 15 minutes and requires no code. If your registration flow goes through a form plugin, check the relevant integration documentation before assuming the core trigger applies.

The free plugin covers everything in this guide. Try Krom Automation free on WordPress.org and have the workflow running before you finish your next coffee.

Frequently Asked Questions

Why am I not getting email notifications when a new user registers?

The most common cause is email delivery failure, not a WordPress configuration problem. Install an SMTP plugin and check the delivery log to confirm whether the email was sent.

If it was sent but not received, the issue is spam filtering or SPF/DKIM alignment on your sending domain. If it was not sent at all, check whether a plugin is suppressing the wp_new_user_notification hook.

How do I send registration notifications to a different email address?

Use the wp_new_user_notification_email_admin filter to change the to field to any address you need. The filter accepts a comma-separated string, so you can include multiple addresses. If you prefer a no-code option, a workflow with a User Registered trigger and a Send Email action handles this in about 10 minutes.

How do I notify different team members based on the user’s role?

Add conditional branching to the workflow. Set a condition on the Yes path for the specific role, add a Send Email action with the relevant recipient, and repeat for each role.

The No path handles any registration that does not match a specific condition. The conditions and branching documentation lists every available condition field.

How do I turn off admin registration emails without affecting the user’s password email?

Add the filter add_filter( 'wp_new_user_notification_email_admin', '__return_false' ); via a snippet plugin. This suppresses only the admin copy. The user still receives their password setup email through the same core function.

Can I get a Slack or SMS alert instead of an email when a user registers?

Yes. The User Registered trigger supports any action the workflow builder offers.

Add a messaging action after the trigger, point it at a Slack channel or a Twilio number, and include merge tags for the user’s name and email. The messaging integrations documentation covers the full setup for Slack, Discord, Twilio, and Telegram.

See full pricing details and compare all plans, annual plans start at $69 and lifetime plans start at $199.