Your Team Is Missing Site Events. Fix It With Slack Alerts
Krom Automation is the fastest way to send WordPress Slack alerts for orders, failed payments, low stock, and form submissions, without Zapier, without a monthly task fee, and without touching a line of code. You build a workflow on a visual canvas, connect a Slack webhook, and every matching event sends a formatted message to the right channel automatically.
The problem is not that your site is quiet. A busy WooCommerce store generates dozens of events every hour: orders placed, payments declined, stock running low, leads submitted through contact forms.
The problem is that almost none of those events produce a visible signal unless you build one. Your team checks the dashboard when they remember to, which means a high-value order placed at 9pm on a Friday sits unacknowledged until Monday morning.
This article covers which events deserve a Slack alert, which ones become noise, how to build the workflows in Krom Automation, and what the multi-site setup looks like for teams running more than one store.
Browse all Krom Automation features to see the full list of triggers and actions before we get into the setup.
What Actually Deserves a Slack Alert
Not every WordPress event needs to interrupt your team. The goal is signal, not noise. A Slack channel that fires 200 times a day trains people to ignore it, which is worse than no alert at all.
Apply a simple filter: an event deserves a Slack alert if someone needs to act within a few hours, or if the event represents enough revenue that a delay in response has a measurable cost.
Events that consistently meet that bar:
- New orders above a threshold, for example orders over $500, where a personal follow-up call or a priority fulfilment queue applies
- Failed or declined payments, because the customer is still warm and a recovery message sent within 30 minutes recovers a meaningful percentage of those orders
- Low stock on high-velocity products, ideally before you hit zero rather than after
- Refund requests and disputed orders, where a fast response reduces chargeback risk
- New form leads from high-intent pages, such as a pricing page or a demo request form, where response time affects close rate
- Failed subscription renewals, where a 24-hour window is often the difference between recovery and churn
- New user registrations on gated or paid communities, where a manual approval or a welcome call is part of the onboarding
Events that almost always become noise:
- Every comment submitted on every post
- Every user login, unless you are monitoring for suspicious access patterns
- Every low-value order under a threshold you define
- Post published events on a site with daily editorial output
- Media uploads
A Slack channel that fires 200 times a day is not an alert system. It is a noise machine that trains your team to look away.
The discipline is not in setting up alerts. It is in deciding what does not get one. Build that list before you open a workflow builder.
How Krom Automation Sends Slack Alerts
Krom Automation uses its HTTP Request action to send a JSON payload to a Slack Incoming Webhook URL. Slack’s Incoming Webhooks are a free, stable feature of any Slack workspace. You generate a unique webhook URL inside Slack, paste it into the HTTP Request action in Krom, and every time the workflow fires it sends a POST request with the message you configure.
The full setup for Slack, Discord, Twilio, and Telegram is documented in the messaging integrations guide. It covers the Slack App creation, webhook URL generation, and the exact JSON payload structure.
What makes Krom Automation useful here beyond just “send a webhook” is merge tags. Merge tags inject live event data into any field in the action, including the Slack message body.
A new order alert can include the order ID, customer name, order total, billing city, and payment method, all pulled from the trigger data automatically. The merge tags documentation lists every available variable by trigger type.
A minimal Slack message for a new WooCommerce order might look like this:
- New order #{{order_id}} placed
- Customer: {{customer_name}} ({{customer_email}})
- Total: {{order_total}}
- Status: {{order_status}}
- Payment: {{payment_method}}
That gives whoever reads the Slack message everything they need to act without opening the WordPress dashboard at all.
Building the Workflow: Order Alerts Step by Step
The free version of Krom Automation includes two WooCommerce triggers: Order Created and Order Completed. Those two cover the highest-priority alert scenarios for most stores.
For a new order alert, the workflow structure is:
- Trigger: Order Created
- Condition: order total is greater than your threshold (for example, $500)
- Action: HTTP Request, method POST, URL is your Slack webhook, body is the JSON message with merge tags
The condition step uses Krom’s conditional branching, which creates a Yes path and a No path from any condition node. Orders above the threshold take the Yes path to the Slack action. Orders below it take the No path, which you leave empty or connect to a different, quieter action.
For failed payment alerts, you need a status-change trigger. The Post Status Changed trigger in the free version handles WordPress post statuses, but WooCommerce order status transitions (pending to failed, processing to on-hold) are covered by the Pro trigger set, which includes 80 or more additional triggers across WooCommerce, subscriptions, memberships, and more. The WooCommerce Subscriptions integration is the relevant starting point if failed renewals are your primary concern.
Conditional Routing: Different Events to Different Channels
One Slack workspace typically has multiple channels. The smart setup routes different alert types to different channels rather than dumping everything into #general.
A practical channel structure for a WooCommerce store:
- #orders-vip: orders above a revenue threshold, requires a human response within 2 hours
- #orders-refunds: refund requests and disputed orders, routed to customer support
- #stock-alerts: low stock and out-of-stock events, routed to the inventory team
- #leads: new form submissions from high-intent pages, routed to sales
- #ops: failed payments, failed subscription renewals, technical errors
Each channel gets its own workflow in Krom Automation with its own trigger, condition, and HTTP Request action pointing to that channel’s webhook URL. Slack generates a separate webhook URL per channel, so routing is handled entirely by which URL you put in the action.
Routing alerts to the right channel is not a nice-to-have. It is the difference between a message someone acts on and one they scroll past.
This structure also makes it easy to pause a channel’s alerts without breaking anything else. In Krom Automation, each workflow has an independent on/off toggle, so you can silence #stock-alerts during a planned clearance sale without touching the order or lead workflows.
Form Lead Alerts: Gravity Forms, WPForms, Fluent Forms
Order events are the obvious use case, but form submissions from high-intent pages often represent higher revenue per lead than a standard order. A pricing enquiry or a custom quote request deserves an alert faster than a standard $30 order does.
Krom Automation Pro includes native form triggers for the most widely used WordPress form plugins. The setup documentation covers each one:
- Gravity Forms integration: trigger on any form submission, filter by form ID or field value
- WPForms integration: same pattern, with field-level merge tags available in the Slack message
- Fluent Forms integration: trigger on submission, with support for multi-step forms
A lead alert workflow fires the moment a form is submitted, sends a Slack message with the submitter’s name, email, the form they used, and any qualifying field values (company size, budget range, project type), and optionally creates a draft post or a CRM contact in the same workflow. The team sees the lead in Slack before the person has finished reading the confirmation page.
Multi-Site Alert Routing: The Gap Nobody Else Covers
Most articles on WordPress Slack alerts assume a single site. If you run multiple WooCommerce stores, the practical question is whether you can manage alert routing from one place or whether you are maintaining separate configurations on every install.
Krom Automation is a self-hosted plugin, which means each WordPress install has its own instance and its own set of workflows. That is not a limitation for most teams. It means alert logic lives with the site it monitors, which is actually the correct architecture: a store in Germany routes to the German fulfilment team’s Slack channel, a store in the UK routes to the UK team.
The relevant consideration for multi-site operations is workflow portability. Krom Automation supports import and export of workflows as JSON files. You build and test the alert workflow on one site, export it, and import the same workflow on the other installs.
You update the Slack webhook URL per site (since each store routes to a different channel) and you are done. A workflow that took 20 minutes to build and test takes under 5 minutes to deploy on each subsequent site.
For agencies managing client portfolios, the agency automation guide covers the multi-client workflow management pattern in more detail.
What the Licensing Looks Like Across Multiple Sites
| Scenario | Sites | Recommended Plan | Annual Cost | Lifetime Cost |
|---|---|---|---|---|
| Single store, basic order alerts | 1 | Free version | $0 | $0 |
| Single store, form leads + order status routing | 1 | Basic Pro | $119/yr | $299 once |
| Small agency or multi-brand operator | Up to 5 | Standard Pro | $199/yr | $499 once |
| Agency or franchiser with many stores | Unlimited | Enterprise Pro | $369/yr | $799 once |
The free version handles Order Created and Order Completed alerts via the HTTP Request action with no time limit and no run cap. If your alert needs go beyond those two triggers, the Pro tier adds 80 or more triggers covering every WooCommerce status transition, subscription events, membership changes, and form platforms.
What Breaks and Why Webhooks Stop Firing
Slack alerts that worked yesterday and stopped working today almost always have one of three causes.
The most common is a rotated or revoked webhook URL. Slack webhook URLs are tied to a Slack App.
If the App is deleted, the bot is removed from the channel, or the workspace admin rotates credentials, the URL becomes invalid and every HTTP Request to it returns a 403 or 404. Fix: regenerate the webhook URL in Slack and update it in the Krom workflow action.
The second cause is a workflow that was paused during testing and never re-enabled. Krom Automation shows workflow status clearly on the workflows list, but it is worth checking if alerts suddenly go quiet after a site update or a staging deployment that overwrote the database.
The third cause is a WP-Cron delay on low-traffic sites. Krom Automation runs workflows via Action Scheduler, which relies on WP-Cron firing. On a site that receives very little traffic, WP-Cron can sit dormant for hours.
For time-sensitive alerts, configure a real server cron job to trigger WP-Cron on a 1-minute interval. Most hosting control panels expose this as a standard cron setting.
Krom Automation’s execution logging records every workflow run with a per-step audit trail. If a webhook is failing, the log shows the HTTP response code returned by Slack, which immediately identifies whether the problem is a bad URL, a malformed payload, or a rate limit. Most competing plugins surface nothing beyond “workflow ran” or “workflow failed.” The per-step log is what makes debugging take 2 minutes instead of 20.
Per-step execution logs turn a 20-minute debugging session into a 2-minute one. Most plugins make you guess. Krom shows you the HTTP response code.
Cost Comparison: Native Plugin vs External Automation
| Approach | Setup method | Monthly cost (1 store) | Run limits | Data location |
|---|---|---|---|---|
| Krom Automation free | Visual workflow builder | $0 | None | Your server |
| Krom Automation Pro (Basic) | Visual workflow builder | $9.90/mo (billed annually) | None | Your server |
| Zapier (Starter) | External, cloud-based | $19.99/mo | 750 tasks/mo | Zapier servers |
| Make.com (Core) | External, cloud-based | $9/mo | 10,000 ops/mo | Make servers |
The external platforms charge per task or per operation. A store placing 400 orders per month and running 5 workflows per order event reaches 2,000 operations before accounting for any other automation. That is fine on Make’s Core plan but exhausts Zapier’s Starter allotment in a few days.
Krom Automation has no per-execution billing at any tier, which means a busy sale period or a viral traffic spike does not change your bill. The full migration guide from Zapier walks through what the transition looks like in practice.
What Krom Automation Does Not Do
Krom Automation is WordPress native. The trigger or the action needs to involve your WordPress site. If you want to send a Slack alert when something happens in a completely external system that has no WordPress connection, you need either the incoming webhook receiver (a Pro feature that gives each workflow a unique secret URL any external service can POST to) or a general purpose automation platform.
The plugin does not act as a Slack bot that reads and responds to Slack messages. It sends messages; it does not receive them or interpret commands typed into Slack. Teams that want two-way Slack interaction need a dedicated bot builder.
Delay precision also has a practical ceiling on shared hosting. A delay set to 5 minutes fires within 5 to 10 minutes on a well-configured server, but on shared hosting with WP-Cron only running on visitor traffic, the actual delay could be longer. For alerts, most workflows have no delay at all, so this constraint rarely matters in practice.
The Setup Decision: Free vs Pro for Alert Workflows
The free version of Krom Automation covers the two most common alert scenarios out of the box: new order created and order completed. For a store whose primary need is “tell us when an order arrives,” the free version is complete.
Pro adds value in three specific situations:
- You need alerts on order status transitions beyond Created and Completed (failed, refunded, on-hold, cancelled)
- You want form lead alerts from Gravity Forms, WPForms, Fluent Forms, or other supported form plugins
- You run multiple event types that need routing to different Slack channels, and you want AI workflow generation to build them faster rather than manually configuring each one
For most stores, the Standard Pro plan at $199 per year (5 site activations) is the right level. It covers an operator running a main store and a staging or development environment, with room for a second brand or a client site. If you are evaluating the Pro features, the free vs Pro comparison lists every trigger and action difference in a single reference table.
Our Verdict
If your team is missing orders, leads, or failed payments because the information lives inside a dashboard nobody checks in real time, the problem is not discipline. It is architecture. Dashboards are pull systems.
Your team has to decide to look. Slack alerts are push systems. The information finds your team.
Krom Automation is the right tool for this if your events originate in WordPress or WooCommerce. The free version is enough for basic order alerts with no cost and no run cap. Pro unlocks the full trigger library, native form integrations, and conditional routing that makes the alert system genuinely useful at scale rather than just functional.
Download the free version from the WordPress.org plugin directory and build your first order alert workflow today. The setup takes under 15 minutes.
Who should not prioritize this right now: sites receiving fewer than 20 orders per month where the owner checks the dashboard daily anyway. At that volume, the alert adds process without saving meaningful time. Build it when the volume is high enough that a missed event has a real cost.
See all Krom Automation plans and pricing to choose the right tier for your store count and alert needs.
Frequently Asked Questions
Do I need to write any code to connect WordPress to Slack?
No. Krom Automation’s HTTP Request action handles the Slack webhook connection without code.
You paste your Slack Incoming Webhook URL into the action field, configure the JSON message body using merge tags, and save. The full setup process is in the messaging integrations documentation.
Can I send alerts to different Slack channels for different order types?
Yes. Slack generates a separate webhook URL for each channel.
You create a separate Krom Automation workflow per alert type, each with its own trigger, condition, and HTTP Request action pointing to the relevant channel’s URL. Each workflow is independently toggleable, so you can pause one channel’s alerts without affecting the others.
Does the free version of Krom Automation support Slack alerts for WooCommerce orders?
Yes. The free version includes the Order Created and Order Completed triggers plus the HTTP Request action.
That combination covers the most common alert use case at no cost and with no run limits. The Pro version adds order status transition triggers, form submission triggers, and conditional routing for more granular alert logic.
Will Slack alerts still work after a WooCommerce or WordPress update?
Yes, as long as the Slack webhook URL remains valid and the workflow is active. Krom Automation’s triggers connect to WordPress and WooCommerce hooks at the application layer, so theme changes and most plugin updates do not affect them. After a major WooCommerce update, check the execution log for any failed runs and verify the webhook URL has not been revoked.
How do I include order details like the total and customer name in the Slack message?
Use merge tags in the HTTP Request action’s body field. Merge tags pull live data from the trigger event into any text field.
For an Order Created trigger, available merge tags include order ID, customer name, customer email, order total, billing address, and payment method. The complete list is in the merge tags reference.
Can I set up Slack alerts across multiple WooCommerce stores from one place?
Krom Automation is a per-site plugin, so each store has its own workflow configuration. However, workflows export and import as JSON files.
You build and test the alert workflow on one site, export it, and import it on each subsequent site, updating only the webhook URL for that store’s Slack channel. This takes under 5 minutes per additional site.