How Do I Keep My Team Updated on Black Friday Sales in Real Time?
The fastest way to keep your team updated on Black Friday sales in real time is to connect your WooCommerce store to Slack using Krom Automation. The free plugin covers order alerts via HTTP Request actions. The Pro plan adds native Slack, Telegram, and Google Sheets integrations that take about 20 minutes to configure.
Black Friday 2026 is November 27. Set this up by November 13 so you have two weeks to test.
Every competing guide treats Slack as a passive webhook destination. This one treats it as a live operations channel: one workflow per purpose, a running order log in Google Sheets, and Telegram for whoever is away from their desk. The goal is that your team knows the moment a high-value order lands, a product sells out, or revenue crosses a milestone, without anyone refreshing the dashboard.
This guide covers four workflows you can build once and run all weekend. It also covers the one timing limitation you need to understand before you rely on any of them.
Browse the full feature list to see every trigger and action available before you start building.
Quick Summary
| Alert type | Trigger | Destination | Free or Pro? |
|---|---|---|---|
| New order notification | Order Created | Slack channel | Pro (Slack action) |
| High-value order alert | Order Created + condition | Slack DM or channel | Pro |
| Order completed log | Order Completed | Google Sheets row | Pro |
| Owner alert on the move | Order Created | Telegram message | Pro |
| HTTP Request fallback | Order Created | Any Slack webhook URL | Free |
Why Slack Alone Is Not Enough
A Slack channel full of raw order notifications turns into noise within the first hour of a sale. By midday on Black Friday, your team stops reading them. The fix is not fewer alerts, it is smarter routing: order volume to a shared channel, high-value orders to a dedicated thread, the owner’s phone to Telegram, and a Google Sheets log that gives you the full picture at a glance without anyone having to scroll through chat history.
Each of the four workflows below has exactly one job. That separation is what keeps the channels readable. Conditional branching in Krom Automation lets you split paths inside a single workflow, so a $500 order and a $20 order can trigger different actions from the same starting point.
A Slack channel full of every order is a wall of noise. A Slack channel filtered to orders over $200 is an operations tool.
Workflow 1: New Order Notification to a Slack Channel
This is the baseline alert. Every new WooCommerce order posts a formatted message to a shared team channel. The message should include the order number, customer name, order total, and the items purchased, all pulled in automatically using merge tags.
The setup in Krom Automation Pro uses the Order Created trigger and the Slack action. Connect your Slack workspace once under the integrations settings, choose the target channel, and write your message template.
A typical message takes about 5 minutes to configure once the connection is live. Full setup steps are in the messaging integrations documentation.
If you are on the free plugin and want to start before upgrading, the HTTP Request action works with Slack’s incoming webhook URL. You send a POST request with a JSON body containing the merge tag values. It is more manual to set up but it costs nothing and the result is functionally identical.
What the Slack message should include
- Order number, so the team can pull it up in WooCommerce instantly
- Customer name and email, so support knows who ordered without leaving Slack
- Order total in currency, so revenue milestones are visible in real time
- Product names, so the fulfilment team knows what needs to move
- A direct link to the order edit screen, saving 30 seconds per order lookup
Workflow 2: High-Value Order Alert with Conditional Branching
Not every order deserves the same attention. A conditional branch after the Order Created trigger checks whether the order total exceeds a threshold you set, say $200 or $500.
Orders above that threshold post to a separate #big-orders channel or trigger a direct message to the store owner. Orders below it post to the general channel as normal.
This is the workflow most teams skip because it takes an extra 10 minutes to build. It is also the one that saves the most time on the day, because your senior people stop wading through $15 orders to find the ones that matter. The conditions and branching documentation shows exactly how to configure the Yes and No paths.
For a deeper look at structuring high-value order notifications across a busy sale period, the guide on WooCommerce high-value order notifications covers the threshold logic in more detail.
Ten minutes building a conditional branch on November 13 saves your team two hours of scrolling on November 27.
Workflow 3: Live Google Sheets Order Log
Slack is for alerts. Google Sheets is for the record.
This workflow fires on Order Completed and appends a new row to a spreadsheet with every field you need for end-of-day reconciliation: order ID, customer name, email, total, products, payment method, and timestamp. By midnight on Black Friday, you have a complete log without anyone having to export anything from WooCommerce.
The Google Sheets integration documentation covers the OAuth connection and column mapping. The key decision is whether to trigger on Order Created or Order Completed. Order Created catches everything including orders that later fail or get refunded.
Order Completed catches only paid, fulfilled orders. For a clean revenue log, Order Completed is the right choice.
Columns worth logging from day one
- Timestamp so you can see order velocity by hour
- Order total for a running revenue sum at the bottom of the sheet
- Payment method to flag any unusual patterns quickly
- Product names to track which items are selling fastest
- Customer email so post-sale tagging and follow-up is ready to go
If you plan to tag those customers in Mailchimp or FluentCRM after the sale, the guide on tagging Black Friday customers automatically explains how to chain that into the same workflow or run it as a separate one. The FluentCRM integration documentation covers the contact and tag actions in detail.
Workflow 4: Telegram Alert for the Owner on the Move
Not everyone is at a desk on Black Friday. If the store owner or a senior team member needs order alerts on their phone without needing the Slack app open, Telegram is the right channel.
Krom Automation Pro supports Telegram natively alongside Slack, Discord, and Twilio. One workflow, one trigger, two action branches: Slack for the team, Telegram for the individual.
The practical setup is a Telegram bot connected to a private chat or a small group. The message can be shorter than the Slack version because it is personal context, not a shared operations log.
Order total, product name, and a link is usually enough. The full configuration is covered in the messaging integrations documentation alongside the Slack setup.
The One Timing Limitation to Know Before Black Friday
Krom Automation runs background tasks via Action Scheduler, which relies on WordPress Cron. On sites with consistent traffic, this works well and delays are measured in seconds. On very low-traffic sites where no one visits for an extended period, WP-Cron fires late, and a delayed order alert on Black Friday is nearly as bad as no alert.
The fix is simple: configure a real server cron job to call the WordPress cron endpoint every minute. Your host’s control panel or a tool like WP-CLI handles this in under 5 minutes.
Do it before November 27. The article on whether Black Friday traffic will break your WordPress automations covers this and other load considerations in full.
If you are running any delayed actions, the delays and scheduling documentation explains how to configure backoff and what happens when a queued action misses its window.
Set It Up by This Date: A Countdown Timeline
Black Friday is November 27, 2026. Cyber Monday is November 30. These deadlines are not generous, they are the minimum lead time to build, test, and fix anything before the sale starts.
| Date | What to complete |
|---|---|
| November 7 | Install Krom Automation Pro, connect Slack, Telegram, and Google Sheets |
| November 10 | Build Workflow 1 (order to Slack) and Workflow 3 (completed order to Sheets) |
| November 12 | Build Workflow 2 (high-value branch) and Workflow 4 (Telegram) |
| November 13 | Run the workflow simulator on all four workflows. Fix anything that fails. |
| November 17 | Place two test orders in WooCommerce staging. Confirm all four destinations receive messages. |
| November 20 | Configure real server cron. Confirm it fires every minute. |
| November 24 | Final check: all workflows active, execution logs clean, Slack channels live |
Test with the Simulator Before Any Real Orders Arrive
Krom Automation includes a workflow simulator that runs a full dry-run of any workflow with zero side effects. No Slack messages are sent, no rows are added to Google Sheets, no Telegram messages fire. You see exactly what would have happened, including merge tag values, branch decisions, and action outputs, without touching a real order.
Run the simulator on each of the four workflows before November 27. Check that merge tags resolve to real values, that the high-value branch fires on the correct path, and that the Google Sheets column mapping lands in the right columns. A 15-minute simulation session on November 13 is the difference between a smooth Friday and a morning of emergency fixes.
The simulator also catches silent failures, the kind where a workflow appears active but never fires because a connection credential expired. Silent failures on Black Friday are expensive. The article on what happens when an automation fails silently explains how to catch them before they cost you.
The simulator is the most underused feature in Krom Automation. Running it costs 15 minutes. Not running it can cost a sale.
What Krom Automation Pro Costs vs. the Alternatives
The free plugin is free forever with no run caps and no feature locks on the core engine. The HTTP Request action in the free version handles basic Slack webhooks at no cost. Pro adds native Slack, Telegram, Google Sheets, and 22 other integrations, plus the schedule trigger, incoming webhook receiver, and 101 additional workflow templates.
| Option | Cost for 1 site, year 1 | Cost from year 2 | Run limits | Native Slack action |
|---|---|---|---|---|
| Krom Automation Free | $0 | $0 | None | No (HTTP Request workaround) |
| Krom Automation Pro Basic | Starts at $69/year | $119/year | None | Yes |
| Uncanny Automator (as of September 2026) | From $199/year | $199/year | None stated | Via integration add-on |
| Zapier Professional (as of September 2026) | Around $240/year | Around $240/year | 750 tasks/month, overages charged | Yes |
Zapier’s task-based billing is worth thinking about specifically for Black Friday. If your store processes 1,000 orders over the weekend and each order fires three Zaps, that is 3,000 tasks in 72 hours. At 750 tasks per month on the Professional plan, you hit overage charges before Saturday morning.
Krom Automation has no per-task or per-execution billing at any tier. The full breakdown of what Zapier costs during Black Friday runs through the numbers scenario by scenario.
Lifetime plans for Krom Automation Pro start at $199 for one site, which covers all 25 integrations and every Pro feature with no annual renewal. See full pricing details for the current launch rates across all plans.
What This Setup Does Not Cover
These four workflows handle alerting. They do not handle stock management, coupon creation, or post-sale follow-up.
If you also need low-stock alerts before you sell out, that is a separate workflow covered in the guide on avoiding running out of stock on Black Friday. If you need to automate coupon codes as part of the sale itself, the guide on sending Black Friday coupon codes automatically covers that workflow.
These workflows also do not apply to sites with no WooCommerce involvement. Krom Automation is WordPress native, so both the trigger and the action touch your site. If you need to monitor a third-party retailer’s price page and alert in Slack, that is a page-monitoring tool problem, not a WordPress automation problem.
Also from wpRigel
Pollify is wpRigel’s Gutenberg native poll, survey, and quiz plugin. Polls are built as real blocks inside the editor, with no shortcodes to paste and no separate interface to configure. Useful for gathering post-sale feedback or running a quick audience poll directly on a post or page.
Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K to jump anywhere, search orders, products, and customers, and run admin actions without clicking through menus. It is the only WordPress command palette with real WooCommerce order, product, and customer commands, which makes it useful exactly on a day when speed in the admin matters.
Our Verdict
If your team is currently refreshing the WooCommerce dashboard or checking a shared inbox for order notifications on Black Friday, these four workflows replace that with a live operations setup that runs without anyone managing it. The free plugin gets you most of the way with the HTTP Request action. Pro makes it faster to configure and adds Telegram and Google Sheets without custom code.
Build by November 13, simulate on November 13, test with real staging orders by November 17, and you will have two full weeks of buffer before the sale starts. Teams that build this on November 26 find something wrong on November 27.
Build it now. Download the free plugin from the WordPress.org plugin directory and install Pro when you are ready to connect Slack natively.
Compare all three Pro plans and pick the one that fits your site count. The 14-day money-back guarantee covers the full sale weekend if you start this week.
Frequently Asked Questions
Do I need Krom Automation Pro to send Black Friday alerts to Slack?
No. The free plugin includes the HTTP Request action, which works with Slack’s incoming webhook URL.
You write the JSON body manually and use merge tags to inject order data. Pro adds a native Slack action that removes that manual step and also adds Telegram and Google Sheets as destinations.
Will WP-Cron delay my order alerts during peak traffic?
On high-traffic sites, WP-Cron fires frequently and delays are minimal. On low-traffic sites, alerts can arrive late if no request hits the site for an extended period. The fix is a real server cron job calling the WordPress cron endpoint every minute, which your host’s control panel can configure in under 5 minutes.
Can I send different alerts to different Slack channels from one workflow?
Yes. Use conditional branching after the Order Created trigger. Orders above your threshold go to one channel action, orders below go to another.
Both branches can include different message formats and different Slack channel targets. The conditions and branching documentation covers the configuration.
How do I test these workflows without placing real orders?
Use the built-in workflow simulator. It runs a complete dry-run of every step, resolves merge tags, and shows you what each action would have sent, without actually sending anything to Slack, Telegram, or Google Sheets.
Run it before November 27. Full details are in the simulator documentation.
Does Krom Automation charge per order or per workflow execution?
No. There is no per-task, per-execution, or per-order billing at any tier, including the free version. You pay once for the Pro licence and run as many workflows as your site generates, across the full Black Friday weekend and beyond.
Can I use the Google Sheets log alongside the Slack alerts in the same workflow?
Yes. A single workflow can have multiple action branches.
The Order Created trigger fires once, and Krom Automation can post to Slack, send a Telegram message, and append a Google Sheets row all from the same execution. Alternatively, run them as separate workflows if you want to pause or test them independently.