How Do I Get WooCommerce Order Notifications in Slack?

You can send WooCommerce order notifications to Slack right now using Krom Automation. The free plugin handles it with an HTTP Request action pointed at a Slack Incoming Webhook.

The Pro plan adds a dedicated Slack action with richer message formatting and per-channel routing. No Zapier account, no monthly task fees, and no per-notification billing at any tier.

The setup takes under 15 minutes if you already have a Slack app. If you do not, the Slack side adds another 5 minutes. Everything runs inside your WordPress site, so order data, execution logs and your Slack bot token never leave your own server.

This guide covers four things: basic new-order alerts, rich message formatting with merge tags, a conditional workflow that pings a VIP channel only for orders above a set value, and what to do when notifications stop firing.

Browse the full feature list to see every trigger and action available before you build.

Quick Summary

Goal	Plugin tier needed	Slack setup required
New order alert to one channel	Free	Incoming Webhook URL
Rich message with order fields	Free	Incoming Webhook URL
Different channel per order status	Pro	Incoming Webhook per channel
VIP alert for orders above a threshold	Free (conditional branching)	Incoming Webhook URL
Retry on failed notification	Free (built-in retry)	Incoming Webhook URL
Order lookup via slash command	Pro (Incoming Webhook Receiver)	Slack slash command + bot token

How Do I Create a Slack Bot and Get a Webhook URL?

Go to api.slack.com/apps, click “Create New App”, and choose “From scratch”. Name it something your team will recognise, such as “WooCommerce Orders”. Select your workspace and click Create.

Once the app is created, open the Incoming Webhooks section from the left sidebar and toggle it on. Click “Add New Webhook to Workspace”, pick the channel where order alerts should land, and authorise. Slack gives you a URL starting with https://hooks.slack.com/services/.

Copy it. That is the only credential Krom Automation needs for the free setup.

Keep the webhook URL private. Anyone with it can post to your channel. Treat it like a password and never commit it to a public repository.

How Do I Build the Basic New-Order Workflow?

Install Krom Automation from the WordPress.org plugin directory if you have not already. In your WordPress admin, go to Krom Automation Workflows Add New. The visual canvas opens on a blank workflow.

The setup follows three nodes on the canvas:

1. Trigger: Order Completed (or Order Created, depending on when you want the alert). Drag it onto the canvas and select it from the WooCommerce trigger group.
2. Action: HTTP Request. Set the method to POST and paste your Slack webhook URL into the URL field. Set Content-Type to application/json.
3. Body payload. In the request body field, enter a JSON object. Slack reads the text key for plain messages or the blocks key for rich formatted ones.

A minimal plain-text body looks like this:

{"text": "New order #{{order_id}} from {{customer_name}}, {{order_total}}"}

Those double-brace tokens are merge tags. Krom Automation replaces them at runtime with real values from the triggering event, so every message contains the actual order ID, customer name and total rather than placeholder text.

Save the workflow and toggle it to Active. Place a test order and the alert should appear in Slack within seconds on a live-traffic site. On a low-traffic or staging site where WP-Cron rarely fires, see the troubleshooting section below.

A Slack notification that lands 45 minutes after the order is as useful as no notification at all. Cron timing is the detail most guides skip, and the one that bites teams hardest on launch day.

How Do I Make the Message Richer and More Useful?

Slack’s Block Kit format lets you send structured messages with sections, dividers and bold labels. Krom Automation’s HTTP Request action sends any valid JSON body, so you can use Block Kit directly without a separate plugin or library.

A practical rich message includes these fields, formatted as a Slack section block:

• Order number and a direct link to the WooCommerce order edit screen
• Customer name and email so the team can act without logging in
• Order total and payment method
• Line items, or at minimum the item count, so fulfilment knows what to pull
• Shipping method if you offer more than one, since that changes who acts on the alert

All of these are available as merge tags. See the free actions reference for the full list of available fields on WooCommerce triggers. The messaging integrations documentation has a worked example of a Block Kit payload you can copy and adapt.

Krom Automation Pro adds a dedicated Slack action that builds the message in a visual editor rather than raw JSON. That is worth considering if your team includes non-developers who will maintain the workflows after setup.

How Do I Send VIP Order Alerts to a Separate Channel?

This is where conditional branching earns its place. The free version of Krom Automation includes a Yes/No branch node. You can evaluate any field from the trigger, including order total, before deciding which action to run.

The workflow shape for a VIP alert looks like this:

1. Trigger: Order Completed
2. Condition: Order total is greater than your threshold (for example, $500)
3. Yes path: HTTP Request to your #vip-orders Slack channel webhook
4. No path: HTTP Request to your standard #orders channel webhook, or leave it empty if you only want the VIP alert

The branching documentation at Conditions and Branching explains how to set the comparison operator and value. The same logic applies to any other condition: product category, customer location, shipping method or payment gateway.

For stores with five or more staff routing orders to fulfilment, marketing and support separately, this single feature removes a daily overhead that typically costs 20 to 40 minutes of manual triage. The Kestrel-style “each team sees only what is relevant” approach is fully achievable in the free tier.

Conditional routing is not a power-user feature. It is the thing that turns a noisy notification into one your team actually reads.

Can I Look Up Orders From Slack Without Opening WordPress?

Yes, but this requires Krom Automation Pro. The Incoming Webhook Receiver gives each workflow a unique secret URL that external services can POST to.

You configure a Slack slash command, such as /order 1234, to POST the order number to that URL. Krom Automation receives it, queries WooCommerce for that order, and POSTs the details back to Slack.

The incoming webhook has HMAC-SHA256 signature verification and nine security layers, so random internet traffic cannot trigger your workflows. See the Incoming Webhook Receiver documentation for the full setup, including how to configure the Slack slash command endpoint and validate signatures.

This approach is more involved than a simple alert. Plan for 30 to 60 minutes of setup if you have not built a Slack slash command before. The payoff is that your support or fulfilment team can answer customer order questions from Slack without a WordPress login, which matters when you have contractors or part-time staff who should not have admin access.

What Does This Cost Compared to Other Options?

Option	Year 1 cost	Year 2 cost	Run limits	Self-hosted
Krom Automation free	$0	$0	None	Yes
Krom Automation Pro (1 site)	From $69/year	From $69/year	None	Yes
Krom Automation Pro lifetime (1 site)	$199 once	$0	None	Yes
Zapier (Professional, as of September 2026)	~$240/year	~$240/year	750 tasks/month, then overage	No
Dedicated Slack-for-WooCommerce plugin (free tier)	$0	$0	Varies by plugin	Yes

The free version of Krom Automation sends unlimited notifications with no run caps. If you process 3,000 orders a month, that is 3,000 Slack messages at no extra cost.

Zapier’s Professional plan at around $240 a year (as of September 2026) counts each notification as a task. At 3,000 orders a month you exhaust the 750-task monthly allowance in the first week and start paying overage.

A dedicated Slack-for-WooCommerce plugin is a reasonable choice if all you ever want is order alerts and nothing else. Krom Automation makes sense when you want the same tool to handle your other automations, including tagging customers in FluentCRM, syncing orders to Google Sheets, or sending follow-up emails, so you are not running four separate plugins to do things one workflow builder can handle.

Why Are My WooCommerce Slack Notifications Not Firing?

This is the question every other guide skips. Here are the real failure modes, in order of how often they occur:

• WP-Cron has not fired. Krom Automation runs actions via Action Scheduler, which depends on WP-Cron. On a low-traffic site where no page loads happen for hours, the action sits in the queue and waits. Fix this by setting up a real server cron job to call wp-cron.php every minute. Most managed WordPress hosts have a cron manager in their dashboard.
• The webhook URL has been rotated or deleted. Slack lets you delete webhooks. If someone cleaned up old apps in the Slack workspace, your URL may no longer be valid. Generate a new one and update the HTTP Request action body.
• A caching plugin intercepted the order hook. Some caching plugins alter WooCommerce’s hook execution order. If you are using a page cache that also caches REST API responses, disable it for the WooCommerce order endpoints and test again.
• The JSON body is malformed. A merge tag that contains an apostrophe or special character can break the JSON structure. Wrap string values in the body and test with the workflow simulator before going live. The simulator runs a dry execution with no side effects, so it is safe to test against a real order.
• The workflow fired but Slack returned an error. Check the execution log in Krom Automation. Each step shows the response code and body. A 400 from Slack means your JSON payload is wrong. A 403 means the webhook URL is invalid or revoked. A 429 means you are sending too fast, which almost never happens in WooCommerce but can occur if a test loop fires repeatedly.

Krom Automation’s built-in failure notifications send you an email when a workflow step fails, and the retry system re-attempts with configurable backoff. You do not have to watch the execution log manually. The triggers reference documents exactly which WooCommerce hooks each trigger listens to, which helps narrow down conflicts with other plugins.

The execution log is the feature that separates a workflow tool from a webhook sender. Without it, a silent failure looks exactly like a working notification.

What About Refunds, Cancellations and Status Changes?

The free version includes an Order Status Changed trigger (listed as Post Status Changed in the core triggers, mapped to WooCommerce order statuses). You can build a separate workflow for each status transition you want to monitor, or use a single workflow with conditional branches that route to different channels depending on which status the order moved to.

Useful status-change alerts most stores eventually want:

• Order moved to Refunded, ping the finance channel
• Order moved to Cancelled within 1 hour of creation, flag for review
• Order moved to On Hold, alert the team to check payment
• Order moved to Processing after a manual review, confirm to fulfilment

For stores running subscriptions, the WooCommerce Subscriptions integration in Krom Automation Pro adds renewal, cancellation and failed payment triggers. Those feed into the same Slack action so your retention team gets notified the moment a subscription lapses.

If you need alerts for digital product sales specifically, the Easy Digital Downloads integration covers the same pattern for EDD-based stores.

What Does Not Work and What to Be Honest About

Krom Automation is WordPress-native. The trigger must originate inside WordPress. If you are routing notifications between two external services with no WordPress involvement, a different tool fits better.

The delay and retry system depends on WP-Cron, as noted above. This is not unique to Krom Automation; it applies to every WordPress scheduler. But it means you should not rely on exact-second delivery for time-critical alerts on a low-traffic site without a real server cron configured.

The free version’s HTTP Request action sends raw JSON. That is flexible but it means you write the Slack Block Kit payload by hand.

Krom Automation Pro’s visual message builder removes that friction if your team is not comfortable with JSON. See the free vs Pro comparison to decide which fits your workflow.

Also from wpRigel

Pollify is wpRigel’s Gutenberg-native poll, survey and quiz plugin. It builds polls as real editor blocks, so there are no shortcodes to paste and no separate interface to learn. Useful for gathering post-purchase feedback directly on your WooCommerce thank-you page.

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K to search orders, edit products, look up customers 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 a natural companion to the Slack notification workflows described here.

Our Verdict

If you want WooCommerce order notifications in Slack today and you process more than a few hundred orders a month, start with the Krom Automation free plugin. The HTTP Request action plus a Slack Incoming Webhook gets you there in under 15 minutes, with no per-notification cost and no external account required beyond Slack itself.

Upgrade to Pro if you need the dedicated Slack action with visual message building, the Incoming Webhook Receiver for slash command order lookup, or the 80+ additional triggers covering subscriptions, form submissions and membership events. Pro starts at $69 a year, and if you are running the workflow on multiple client sites, the 5-site Standard plan at $149 a year is the better unit cost. Lifetime plans start at $199 if you prefer to avoid annual renewals.

Do not upgrade just for Slack notifications. The free tier handles that completely. Upgrade when you want to consolidate five separate single-purpose plugins into one workflow builder that also handles your email sequences, CRM sync and Google Sheets logging.

Download the free plugin from WordPress.org and build the workflow before you evaluate the Pro features. The canvas, the execution log and the simulator are all available at no cost, so you can verify the setup works on your specific stack before spending anything.

See Krom Automation pricing and compare all plans if you are ready to add Pro features.

Frequently Asked Questions

Does the free version of Krom Automation support Slack notifications?

Yes. The free plugin includes an HTTP Request action that posts to any Slack Incoming Webhook URL. You get unlimited notifications, merge tags for dynamic order data, and execution logging at no cost.

Can I send different WooCommerce order statuses to different Slack channels?

Yes. Build one workflow per status transition, each with its own HTTP Request action pointing to a different channel webhook.

Alternatively, use a single workflow with Yes/No conditional branches that route to different webhook URLs depending on the status. Conditional branching is included in the free version.

How do I include the order total and customer name in the Slack message?

Use merge tags in the HTTP Request body. Krom Automation replaces tokens like {{order_total}} and {{customer_name}} with real values from the triggering event at runtime. The merge tags documentation lists every available field for WooCommerce triggers.

Why did my Slack notification not arrive after a test order?

Check the execution log in Krom Automation first. A failed step shows the HTTP response code from Slack, which tells you whether the problem is a bad URL (403), malformed JSON (400) or a WP-Cron delay. On low-traffic sites, configure a real server cron job so Action Scheduler fires reliably rather than waiting for the next page load.

Can I get a Slack alert only for orders above a certain value?

Yes. Add a condition node between your Order Completed trigger and the HTTP Request action. Set the condition to evaluate order total greater than your chosen threshold.

Orders below it skip the Slack action entirely. No Pro upgrade is needed for this; conditional branching is in the free version.

Does Krom Automation work on a multisite WordPress network?

Krom Automation can be activated per site on a multisite network. Each site manages its own workflows independently, so you can route order notifications from site A to one Slack workspace and site B to another. There is no cross-site workflow sharing in the current version.