🔓 Unlock all 10,000+ workflows & prompts free Join Newsletter →
✅ Full access unlocked — explore all 10,000 AI workflow and prompt templates Browse Templates →
Home › n8n › Workflow
January 22, 2026

Shopify + Slack: low stock alerts before you sell out

Shopify + Slack: low stock alerts before you sell out - n8n workflow automation template
Lisa Granqvist Partner Workflow Automation Expert
Shopify + Slack: low stock alerts before you sell out - n8n workflow automation template
Get a free AI assessment → Get a free AI assessment → ⬇️ Use template

Stockouts rarely happen “suddenly.” They happen because inventory data is scattered, reorder decisions are delayed, and no one wants to babysit spreadsheets all day. Then a best-seller goes to zero and you find out from an angry customer.

Shopify Slack alerts hit hardest when your team is small and every missed reorder hurts. Ecommerce Managers feel it during launches. Ops leads feel it when suppliers are slow. And if you run a lean brand, you feel it every weekend.

This workflow watches your inventory hourly, calculates dynamic reorder points from real sales velocity, and posts clear “do this now” alerts in Slack. You’ll see how it works, what you need, and what results to expect.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: Shopify + Slack: low stock alerts before you sell out

The Problem: Low Stock Gets Noticed Too Late

Inventory work tends to live in the cracks between tools. Shopify has “on hand,” your team has a Google Sheet with ideal levels, suppliers have lead times in someone’s inbox, and purchase orders get tracked… somewhere. So the “reorder” moment becomes a messy human decision made under pressure. You pull reports, scan SKUs, second-guess demand, and message the team. Meanwhile, the products that actually pay the bills keep selling. By the time you’re confident enough to order, you are already late.

It adds up fast. Here’s where it breaks down in real stores.

  • You check stock manually, but you’re reacting to yesterday’s numbers instead of current demand.
  • Reorder points stay static, so a product that suddenly spikes sells out before anyone notices.
  • Supplier ordering turns into copy-paste busywork, which means POs get delayed or made with the wrong quantities.
  • There’s no clean audit trail, so you can’t easily answer “When did we order this, and why?”

The Solution: Hourly Inventory Monitoring + Predictive Reordering

This n8n workflow turns inventory monitoring into something your store does automatically, not something you remember to do. Every hour, it pulls live inventory, product details, and recent order history from Shopify. It also reads your Google Sheets sources (Inventory Master, Supplier Directory, and PO Log) so it understands how you want to manage stock, not just what Shopify says is available. Then it calculates sales velocity (based on the last 7 and 30 days), computes a dynamic reorder point per SKU, and checks business rules like minimum order quantities, budget limits, promo windows, and approvals. When risk is real, Slack gets an alert with context. When it’s time to order, the workflow prepares a PO, sends it by email or supplier API, waits for confirmation, and logs everything back to Sheets.

The flow starts on an hourly schedule. From there, Shopify + Google Sheets data is merged into one SKU-level view, the workflow calculates reorder thresholds and stockout risk, and Slack messages go out to keep the team aligned. Finally, POs and metrics are written back to Sheets so you have traceability and a clean operational record.

What You Get: Automation vs. Results

Example: What This Looks Like

Say you track 200 SKUs and do a “low stock pass” twice a week. Manually, that’s often about 2 hours per pass between Shopify exports, spreadsheet checks, and messaging the team, so roughly 4 hours a week. With this workflow, the hourly run is automatic and Slack surfaces only the SKUs that truly need attention. You might spend 10 minutes reviewing alerts and approving a PO, then move on. That’s hours back, plus fewer “oh no” moments.

What You’ll Need

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • Shopify to pull inventory, products, and orders
  • Google Sheets to store inventory rules and PO logs
  • Slack Incoming Webhook URL (get it from Slack app webhook setup)

Skill level: Intermediate. You’ll connect accounts, match sheet columns, and adjust a few business rules.

Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).

How It Works

An hourly schedule kicks things off. The workflow runs automatically each hour, so your inventory picture stays fresh without anyone remembering to “go check.”

Shopify and Google Sheets data get merged into one view. It fetches inventory levels, product details, and recent orders from Shopify, then reads your Inventory Master, Suppliers list, and PO Log from Sheets to add your internal rules and history.

Sales velocity and reorder points are calculated for each SKU. Code steps compute 7/30-day velocity, dynamic reorder thresholds, and stockout risk, then a set of checks apply guardrails like MOQs, budget limits, promo windows, business days, and approval thresholds.

Slack gets the signal, and POs get handled end-to-end. Critical risk alerts and slow-mover suggestions are posted to Slack. When a reorder is justified, the workflow formats PO line items, sends the PO via email or supplier API, waits for confirmation, then updates the PO log and dashboards in Google Sheets.

You can easily modify the reorder rules to match your lead times and cashflow goals based on your needs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Schedule Trigger

Start the workflow on an hourly cadence using the built-in schedule trigger.

  1. Add and configure Hourly Schedule Start.
  2. Set the schedule rule to run every hour (the node uses Interval with Field set to hours).
  3. Connect Hourly Schedule Start to Workflow Settings Loader.

Step 2: Connect Shopify and Google Sheets

Load inventory, product, order, and sheet data in parallel immediately after settings are loaded.

  1. In Workflow Settings Loader, keep Include Other Fields enabled and verify the default values: shopifyStoreUrl https://your-store.myshopify.com, reorderPointMultiplier 1.5, safetyStockDays 7, budgetLimit 50000, largeOrderThreshold 10000, slowMoverThresholdDays 90.
  2. Connect Workflow Settings Loader to data inputs, and note it runs in parallel: Workflow Settings Loader outputs to Fetch Inventory Levels, Retrieve Product Details, Pull Recent Orders 30d, Load Supplier Directory, Read PO History Log, and Read Inventory Master Sheet in parallel.
  3. For Pull Recent Orders 30d, set Created At Min to {{$now.minus({ days: 30 }).toISO()}} and keep Return All enabled.
  4. For Read Inventory Master Sheet, set Sheet Name to Inventory Master and Document ID to {{$env.INVENTORY_MASTER_SHEET_ID || "<__PLACEHOLDER_VALUE__Inventory Master Google Sheet ID__>"}}.
  5. For Load Supplier Directory, set Sheet Name to Suppliers and Document ID to {{$env.SUPPLIERS_SHEET_ID || "<__PLACEHOLDER_VALUE__Suppliers Google Sheet ID__>"}}.
  6. For Read PO History Log, set Sheet Name to PO Log and Document ID to {{$env.PO_LOG_SHEET_ID || "<__PLACEHOLDER_VALUE__Purchase Order Log Google Sheet ID__>"}}.
  7. Credential Required: Connect your Shopify credentials in Fetch Inventory Levels, Retrieve Product Details, Pull Recent Orders 30d, and Apply Inventory Updates.
  8. Credential Required: Connect your Google Sheets credentials (service account) in Read Inventory Master Sheet, Load Supplier Directory, Read PO History Log, Update PO Log Sheet, Write Metrics Dashboard, and Update Scenario Planning.

⚠️ Common Pitfall: The Shopify and Google Sheets nodes in this workflow have no credentials configured. You must add credentials before testing, or the workflow will fail at the first data fetch.

Step 3: Set Up Data Consolidation and Inventory Analytics

Merge the six incoming data feeds and compute sales velocity, reorder thresholds, and stockout risk.

  1. Configure Combine Data Feeds with Mode set to combine, Combine By set to combineByPosition, and Number Inputs set to 6.
  2. Send Combine Data Feeds output to Compute Sales Velocity to calculate velocity_7d, velocity_30d, and avg_daily_sales.
  3. Note the parallel split: Compute Sales Velocity outputs to Compute Reorder Threshold and Detect Slow-Moving Items in parallel.
  4. In Compute Reorder Threshold, keep the dynamic reference to settings: {{$('Workflow Settings Loader').first().json.safetyStockDays}}.
  5. After Compute Reorder Threshold, note the parallel split: Compute Reorder Threshold outputs to Validate Reorder Threshold, Map Inventory Update Fields, and Assemble Analytics Metrics in parallel.
  6. For Validate Reorder Threshold, confirm the condition uses {{$json.current_stock}} ≤ {{$json.reorder_point}}.
  7. Send Validate Reorder Threshold to Compute Stockout Risk and then to Assess Stockout Risk with the condition {{$json.stockout_risk}} > 0.7.
  8. From Assess Stockout Risk, the workflow runs in parallel: Assess Stockout Risk outputs to Evaluate Warehouse Transfer and Notify Critical Stock Risk in parallel.
  9. Configure Map Inventory Update Fields to map available to {{$json.reorder_point}} and updated_at to {{$now.toISO()}}, then connect to Apply Inventory Updates.
  10. For slow movers, connect Detect Slow-Moving Items → Map Slow-Mover Details → Notify Slow-Mover Advice.

Step 4: Add Supplier and Order Qualification Logic

Enrich inventory items with supplier details, then apply business rules for ordering thresholds and approvals.

  1. Route Evaluate Warehouse Transfer to Verify Supplier Availability, then to Enhance Supplier Details.
  2. In Verify Supplier Availability, confirm the condition is {{$json.supplier_available}} = true.
  3. In Check Business Day Window, confirm the weekday filter: {{$now.weekday >= 1 && $now.weekday <= 5}}.
  4. Set up the approval chain: Check Business Day Window → Validate MOQ Requirement → Check Promo Window → Validate Budget Limit → Review Large Order Approval.
  5. Verify rule expressions: Validate MOQ Requirement uses {{$json.order_quantity}} ≥ {{$json.moq}}, Validate Budget Limit compares {{$json.total_po_value}} < {{$('Workflow Settings Loader').first().json.budgetLimit}}, and Review Large Order Approval uses {{$json.total_po_value > $('Workflow Settings Loader').first().json.largeOrderThreshold}}.
  6. Continue to Compute Order Quantity Value and then Prioritize Profit Ranking before formatting the line items in Format PO Line Items.
  7. In Format PO Line Items, keep the line item ID formula {{$json.sku}}_{{$now.toMillis()}} and total price formula {{$json.order_quantity * $json.unit_price}}.

Step 5: Configure Purchase Order Dispatch

Create purchase order payloads and send them via email and supplier API, then log confirmation.

  1. Ensure Prepare PO Email Data receives formatted items from Format PO Line Items.
  2. Note the parallel split: Prepare PO Email Data outputs to Dispatch PO Email and Send PO via Supplier API in parallel.
  3. In Dispatch PO Email, set Send To to {{$json.supplier_email || "<__PLACEHOLDER_VALUE__Supplier email address__>"}} and Subject to Purchase Order - {{$json.po_number}}.
  4. In Send PO via Supplier API, set URL to {{$json.supplier_api_endpoint || "<__PLACEHOLDER_VALUE__Supplier API endpoint__>"}} and keep the Authorization header set to {{$env.SUPPLIER_API_TOKEN || "<__PLACEHOLDER_VALUE__Supplier API token__>"}}.
  5. From Dispatch PO Email, note the parallel split: Dispatch PO Email outputs to Delay for PO Confirmation and Notify PO Sent in parallel.
  6. Configure Delay for PO Confirmation with Unit hours and Amount 1, then connect to Update PO Log Sheet.
  7. In Update PO Log Sheet, confirm Operation is appendOrUpdate and Document ID is {{$env.PO_LOG_SHEET_ID || "<__PLACEHOLDER_VALUE__Purchase Order Log Google Sheet ID__>"}}.
  8. Credential Required: Connect your Gmail credentials (service account) in Dispatch PO Email.

Tip: Replace all <__PLACEHOLDER_VALUE__...> entries with real IDs or set the corresponding $env variables before running in production.

Step 6: Set Up Alerts and Analytics Outputs

Send operational alerts to Slack and push analytics metrics to Sheets and your accounting endpoint.

  1. For critical stock alerts, configure Notify Critical Stock Risk with its channel set to {{$env.SLACK_CRITICAL_CHANNEL || "<__PLACEHOLDER_VALUE__Slack channel ID for critical alerts__>"}}.
  2. For PO notifications, configure Notify PO Sent with its channel set to {{$env.SLACK_PO_CHANNEL || "<__PLACEHOLDER_VALUE__Slack channel ID for PO notifications__>"}}.
  3. For slow-mover advice, configure Notify Slow-Mover Advice with its channel set to {{$env.SLACK_SLOWMOVER_CHANNEL || "<__PLACEHOLDER_VALUE__Slack channel ID for slow-mover alerts__>"}}.
  4. After Update PO Log Sheet, ensure Aggregate Daily Report feeds into Post Daily Summary with the summary text driven by {{$json.total_pos}} and {{$json.total_value}}.
  5. Note the parallel analytics split: Assemble Analytics Metrics outputs to Write Metrics Dashboard, Update Scenario Planning, and Sync Accounting Endpoint in parallel.
  6. In Sync Accounting Endpoint, keep URL set to {{$env.ACCOUNTING_API_ENDPOINT || "<__PLACEHOLDER_VALUE__Accounting API endpoint URL__>"}} and Authentication set to genericCredentialType with HTTP Header Auth.
  7. Credential Required: Connect your Slack credentials in Notify Critical Stock Risk, Notify PO Sent, Notify Slow-Mover Advice, and Post Daily Summary.
  8. Credential Required: Connect your HTTP Header Auth credentials in Sync Accounting Endpoint.

⚠️ Common Pitfall: If the Slack channel IDs are left as placeholders, the Slack nodes will fail even if credentials are valid.

Step 7: Test and Activate Your Workflow

Run a controlled test to verify data inputs, approvals, and outputs before enabling hourly automation.

  1. Click Execute Workflow to run Hourly Schedule Start manually and watch each branch complete.
  2. Confirm that Combine Data Feeds receives six inputs and that Compute Sales Velocity produces avg_daily_sales.
  3. Verify that at least one path reaches Dispatch PO Email or Send PO via Supplier API, and that Update PO Log Sheet appends a record.
  4. Check that Slack notifications appear from Notify Critical Stock Risk, Notify PO Sent, and Notify Slow-Mover Advice when criteria are met.
  5. Once validated, toggle the workflow to Active so Hourly Schedule Start runs automatically every hour.
🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

  • Shopify API credentials can expire or lack the right scopes. If inventory pulls fail, check your Shopify app permissions and credential status inside n8n first.
  • If you’re using Wait nodes or external confirmations, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
  • Google Sheets breaks quietly when column names change. If logs stop updating, check the Inventory Master and PO Log headers match what the workflow expects.

Related Workflows

If your team also needs cleaner product creation, Google Sheets to Shopify, products added without duplicates pairs well because it keeps your catalog tidy before this inventory automation starts making reorder decisions.

For teams doing sales across multiple storefronts, Shopify + WooCommerce: inventory stays in sync helps prevent the classic problem where one channel sells the last unit and the other channel keeps taking orders.

Need a lighter-weight version of purchasing automation? Google Sheets + Gmail: low stock POs sent for you is a good fit when you already manage reorder rules in Sheets and mostly want the PO sending handled.

When leadership wants a heads-up on demand, Google Sheets to Gmail, weekly sales forecasts sent complements Slack alerts by adding a predictable weekly forecast email for planning and cashflow.

Finally, if you want tighter operational reporting, Shopify to Google Sheets, orders logged without gaps gives you a reliable orders dataset, which makes sales velocity calculations and inventory decisions more trustworthy.


Quick reference:

Frequently Asked Questions

How long does it take to set up this Shopify Slack alerts automation?

About an hour if your Sheets are already structured.

Do I need coding skills to automate low stock alerts?

No. You’ll mostly connect accounts and match your Google Sheets columns. The “math” is already built into the workflow.

Is n8n free to use for this Shopify Slack alerts workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Shopify API usage (usually fine) and optional OpenAI usage if you keep the AI Agent enabled.

Where can I host n8n to run this automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

Can I customize this Shopify Slack alerts workflow for multi-warehouse transfers instead of reordering?

Yes, and it’s one of the best parts. You can lean harder on the warehouse redistribution path by adjusting the warehouse transfer checks and the transfer formatting step, then route more “low stock” cases into transfer suggestions before any PO logic runs. Common customizations include adding warehouse priority rules, excluding certain SKUs from transfers (fragile, regulated, or bundles), and setting a minimum transfer quantity so you don’t create noisy micro-movements.

Why is my Shopify connection failing in this workflow?

Usually it’s missing scopes on the Shopify private app, or the credentials in n8n no longer match the app. Regenerate the API credentials, update them in n8n, then re-run a single Shopify fetch node to confirm it’s working. If it fails only on busy days, rate limiting can also be the culprit, so reduce the number of items pulled per run or add short waits between requests.

How many SKUs can this Shopify Slack alerts automation handle?

A few hundred SKUs is typical on a basic setup, and you can scale from there by self-hosting and optimizing how much order history you pull each run.

Is this Shopify Slack alerts automation better than using Zapier or Make?

Often, yes, because this isn’t a simple “if low stock then ping Slack” recipe. The value comes from merging multiple data sources, running velocity calculations, applying business rules (MOQ, budget, approvals), and then branching into different outcomes like transfer suggestions, PO sending, and logging. n8n is built for that kind of logic and it doesn’t punish you for adding branches. Zapier or Make can still work if you keep the scope small, but you may end up stitching together several zaps/scenarios to match the same behavior. If you want a second opinion before you commit, Talk to an automation expert.

Once this is running, inventory risk stops being a surprise and starts being a Slack message with a clear next action. Honestly, that calm is the real win.

Need Help Setting This Up?

Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.

Talk to Automation Expert →

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

×

Use template

Get instant access to this n8n workflow Json file

Copy and import json workflow into your n8n workflow

💬
Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.

Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.