January 22, 2026

WooCommerce to Slack, catch return surges fast

Lisa Granqvist Partner Workflow Automation Expert

Get a free AI assessment → ⬇️ Use template

Returns don’t usually explode all at once. They creep up, SKU by SKU, until you’re suddenly refunding a “normal” product all day and nobody can explain why. By the time you notice it in a weekly report, you’ve already eaten the shipping, the support time, and the hit to margin.

This is where WooCommerce Slack alerts save you. eCommerce ops feels the damage first, but support leads and product teams get dragged in fast when the same item keeps coming back. You want a heads-up while the problem is still small.

This workflow watches refunds, detects unusual SKU-level return surges, alerts your team in Slack, and logs every surge to Airtable so you can investigate patterns instead of guessing.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: WooCommerce to Slack, catch return surges fast

Click to explore

flowchart LR

    subgraph sg0["Schedule Flow"]
        direction LR
        n0@{ icon: "mdi:play-circle", form: "rounded", label: "Schedule Trigger", pos: "b", h: 48 }
        n1@{ icon: "mdi:swap-horizontal", form: "rounded", label: "If", pos: "b", h: 48 }
        n2["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/slack.svg' width='40' height='40' /></div><br/>Send a message"]
        n3["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/airtable.svg' width='40' height='40' /></div><br/>Create a record"]
        n4["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Orders_Fetch"]
        n5["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Refund_details"]
        n6["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Time_window"]
        n7["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>HTTP Orders"]
        n8["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>HTTP Refunds"]
        n9@{ icon: "mdi:swap-vertical", form: "rounded", label: "Edit Fields1", pos: "b", h: 48 }
        n10["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Code in JavaScript"]
        n1 --> n9
        n7 --> n8
        n6 --> n7
        n9 --> n2
        n8 --> n4
        n4 --> n5
        n5 --> n1
        n2 --> n10
        n0 --> n6
        n10 --> n3
    end

    %% Styling
    classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
    classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
    classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
    classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
    classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
    classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
    classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
    classDef disabled stroke-dasharray: 5 5,opacity: 0.5
    class n0 trigger
    class n1 decision
    class n3 database
    class n7,n8 api
    class n4,n5,n6,n10 code
    classDef customIcon fill:none,stroke:none
    class n2,n3,n4,n5,n6,n7,n8,n10 customIcon

The Problem: Return surges get noticed too late

Most WooCommerce stores can tell you how many refunds happened. Fewer can tell you which SKU is suddenly “going bad” today versus last week. That’s the gap that hurts. A packaging change, a supplier batch issue, or a misleading product photo can trigger a wave of returns, and the early warning signs are buried inside orders, refunds, and line items that don’t roll up cleanly. You end up reacting based on vibes, scattered screenshots, or someone in support saying “I’m seeing a lot of these.” Honestly, that’s not a system.

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

Refund data lives in WooCommerce, but SKU-level patterns are tedious to piece together manually.
By the time a weekly report shows the spike, you’ve already refunded a chunk of inventory and paid for the support load.
Teams lose time chasing the “why” because there’s no consistent log of when the surge started and how big it was.
Without a shared alert in Slack, issues stay trapped in one inbox or one person’s head.

The Solution: Detect SKU return spikes and alert Slack automatically

This n8n workflow runs on a schedule and checks your WooCommerce store for recent orders and refund activity through the WooCommerce REST API. It then connects the dots: each refund is mapped back to the original order so the workflow can attribute returns to the correct SKUs (not just the order number). Next, it calculates return counts per SKU across rolling 24-hour windows, comparing “current” activity versus the previous window to spot unusual changes. When a surge crosses your threshold, n8n posts a clean, structured alert to Slack so the right people see it immediately. Finally, it writes a record to Airtable, creating a searchable history of every surge for later analysis and root-cause work.

The workflow starts with a scheduled trigger and a time window calculation. From there it pulls orders and refunds, aggregates SKU-level return metrics, and checks surge conditions. If it’s a real spike, Slack gets notified and Airtable gets a timestamped log entry.

What You Get: Automation vs. Results

What This Workflow Automates

Results You’ll Get

Pulling recent WooCommerce orders and refund records on a schedule.
Mapping refunds back to their parent orders to identify affected SKUs.
Comparing rolling 24-hour windows and calculating SKU return increases.
Sending Slack alerts and logging each surge event into Airtable automatically.

Catch problems the same day, not “next report,” which often saves a few hours of scrambling.
Fewer missed incidents because alerts show up where your team already works.
Cleaner investigations because every surge is logged with consistent fields.
Faster handoffs between support, ops, and product since everyone sees the same signal.
More confident decisions on pausing promos, updating listings, or escalating to suppliers.

Example: What This Looks Like

Say you run a catalog of 200 SKUs and you do a quick return check twice a day. Manually, it’s common to spend about 20 minutes pulling refunds, filtering line items, and trying to spot a pattern, so call it 40 minutes a day. With this workflow, you set the schedule once, and the “check” becomes a Slack alert only when something’s actually wrong, plus an Airtable log entry for reference. Most days, that’s effectively zero minutes of monitoring, and you still catch the ugly spikes within the same 24-hour window.

What You’ll Need

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
WooCommerce to access orders and refunds
Slack to notify your team instantly
Airtable to store a searchable surge log
WooCommerce REST API keys (get them from WooCommerce → Settings → Advanced → REST API)

Skill level: Intermediate. You’ll connect accounts, paste API keys, and adjust a couple of threshold settings confidently.

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

How It Works

A schedule kicks it off. n8n runs on your chosen interval (hourly, every few hours, daily) so you’re not relying on someone remembering to check refunds.

Time windows are calculated. A code step defines the “current” 24-hour window and the previous 24-hour window, which gives you a simple baseline to compare against.

WooCommerce data is pulled and normalized. Two HTTP requests fetch orders and refunds, then code nodes map refunds back to parent orders and aggregate returns at the SKU level.

Surges are checked and routed. If the increase meets your surge rule (for example, doubling versus the previous window, or hitting a high absolute count), the workflow enriches the alert fields, posts a message in Slack, and logs the event into Airtable.

You can easily modify the surge threshold and the window size to fit your business rhythms. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Scheduled Run Trigger

Set the automation to run on a timed schedule so return monitoring happens consistently.

Add the Scheduled Run Trigger node and open its settings.
Set Interval to hours so the workflow runs hourly.
Confirm the connection flow starts with Scheduled Run Trigger → Compute Time Window.

Step 2: Connect WooCommerce APIs

Pull orders and refunds from WooCommerce to detect return surges.

In Fetch Order API, set URL to https://{your_wocommerce_domain}/wp-json/wc/v3/orders.
Enable Send Query in Fetch Order API and keep Authentication set to genericCredentialType.
In Retrieve Refund API, set URL to =https://{your_wocommerce_domain}/wp-json/wc/v3/refunds.
Credential Required: Connect your httpBasicAuth credentials in both Fetch Order API and Retrieve Refund API.

⚠️ Common Pitfall: Replace {your_wocommerce_domain} with your actual WooCommerce domain; leaving the placeholder will cause failed API calls.

Step 3: Set Up Processing Nodes

Compute time windows, map orders to refunds, and aggregate return metrics before applying surge logic.

In Compute Time Window, keep the provided JavaScript that sets WINDOW_HOURS = 24 and outputs timeWindow.currentStart and timeWindow.currentEnd.
Confirm execution order matches: Compute Time Window → Fetch Order API → Retrieve Refund API → Map Orders to Refunds → Aggregate Return Metrics.
In Map Orders to Refunds, keep the references to $items("Fetch Order API") and $items("Retrieve Refund API") to correctly join orders and refunds.
In Aggregate Return Metrics, keep the logic that counts refunds in the current and previous 24-hour windows and produces percent_increase.

Step 4: Configure Surge Logic and Alert Fields

Filter SKUs that meet surge thresholds and assign consistent alert metadata.

In Return Surge Check, set conditions to trigger when {{ $json.percent_increase }} is gte 100 OR {{ $json.current_returns }} is gte 25.
In Assign Alert Fields, set status to alerted.
Set run_date_utc to {{ new Date().toISOString() }}.
Set cooldown_key to {{ $json.sku + "_" + new Date().toISOString().slice(0,10) }} and keep Include Other Fields enabled.

Step 5: Configure Slack Alerts and Airtable Logging

Send Slack alerts, parse the message for structured fields, and log each alert to Airtable.

In Post Slack Alert, set Channel to your target Slack channel and keep Text set to the provided expression starting with =⚠️ Return Surge Detected.
Credential Required: Connect your slackApi credentials in Post Slack Alert.
In Parse Slack Payload, keep the JavaScript that extracts sku, current_returns, previous_returns, and percent_increase from the Slack message.
In Log Alert Record, set Operation to create and map columns using expressions like {{ $json.sku }}, {{ $json.reasons_raw }}, and {{ $json.percent_increase }}.
Credential Required: Connect your airtableTokenApi credentials in Log Alert Record.

⚠️ Common Pitfall: The Airtable field key is resons (not reasons) in Log Alert Record. Ensure your Airtable table uses the same field name or update the mapping.

Step 6: Test and Activate Your Workflow

Validate the end-to-end flow, then enable it for live monitoring.

Click Execute Workflow to run a manual test from Scheduled Run Trigger.
Confirm data flows through Compute Time Window → Fetch Order API → Retrieve Refund API → Map Orders to Refunds → Aggregate Return Metrics → Return Surge Check.
Verify a Slack alert appears from Post Slack Alert when thresholds are met and that Log Alert Record creates a new Airtable row.
When satisfied, toggle the workflow to Active for hourly monitoring.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

WooCommerce credentials can expire or lack permissions. If things break, check WooCommerce → Settings → Advanced → REST API and confirm the key has read access to orders and refunds first.
If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
Slack alerts can “work” but still miss the right channel if permissions are limited. Double-check the Slack app scopes and confirm the selected channel in the Slack node matches where your ops team actually lives.

Frequently Asked Questions

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

About 30 minutes if your WooCommerce, Slack, and Airtable accounts are ready.

Do I need coding skills to automate WooCommerce Slack alerts?

No. You will connect credentials and edit a couple of values like the schedule and thresholds.

Is n8n free to use for this WooCommerce 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 Airtable plan limits (if your base grows fast) and any optional AI usage if you extend the workflow.

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 WooCommerce Slack alerts workflow for a different surge definition?

Yes, and it’s the first thing most teams tweak. Change the conditions inside the Return Surge Check node to match how you think about “bad” (for example, raise the absolute return count, or require a bigger jump versus the previous window). You can also adjust the comparison window in the Compute Time Window code node, then update the alert text in Post Slack Alert so your team sees the right context.

Why is my WooCommerce connection failing in this workflow?

Usually it’s an API key issue. Regenerate the WooCommerce Consumer Key and Secret, then update the credentials used by the HTTP Request nodes that fetch orders and refunds. Also confirm the key has permission to read both resources, and that your store URL is correct (no staging domain by accident). If you run this very frequently, rate limiting can show up too, so spacing the schedule out a bit often fixes it.

How many refund records can this WooCommerce Slack alerts automation handle?

It depends on your n8n plan and your WooCommerce API performance, but most small stores can run it hourly without issues.

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

Often, yes, because the “surge” logic is the whole point and n8n handles branching and code-based calculations cleanly. Zapier or Make can send a message when a refund happens, but comparing rolling 24-hour windows and aggregating by SKU gets messy fast, and can become expensive as volume grows. n8n also gives you the self-hosting option, which is a big deal when you want lots of executions without thinking about task counts. That said, if you only need a basic “refund happened” ping, Zapier or Make is fine. If you’re torn, Talk to an automation expert and we’ll point you in the right direction.

Return spikes are expensive because they stay invisible until they’re obvious. This workflow makes them visible early, then leaves you with a clean trail in Airtable so fixing the root cause gets a lot easier.

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.

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

{
"id": null,
"meta": {
"instanceId": "8505b3b6379bcbc56883f0fb75c107d7b7e04ea87d3e15816e25548756c2cd87",
"templateCredsSetupCompleted": null,
"templateId": null
},
"name": "Automated WooCommerce Return Monitor",
"tags": [],
"nodes": [
{
"id": "flowpast-topbar-11945",
"name": "Flowpast Branding",
"type": "n8n-nodes-base.stickyNote",
"position": [
155,
75
],
"parameters": {
"color": 7,
"width": 1415,
"height": 80,
"content": "## Flowpast.com | Automation Workflow Library\n**\ud83d\udcd6 Full tutorial & setup guide:** flowpast.com"
},
"typeVersion": 1
},
{
"id": "fa1bf279-3572-473d-be40-cb188bc6dfe7",
"name": "Scheduled Run Trigger",
"type": "n8n-nodes-base.scheduleTrigger",
"position": [
230,
215
],
"parameters": {
"rule": {
"interval": [
{
"field": "hours"
}
]
}
},
"typeVersion": 1.2
},
{
"id": "748f44df-885d-498e-b355-ac5e2936a753",
"name": "Compute Time Window",
"type": "n8n-nodes-base.code",
"position": [
640,
175
],
"parameters": {
"jsCode": "const now = new Date();\nconst WINDOW_HOURS = 24;\nconst ms = WINDOW_HOURS * 60 * 60 * 1000;\n\nconst currentEnd = now;\nconst currentStart = new Date(now.getTime() - ms);\nconst prevEnd = currentStart;\nconst prevStart = new Date(prevEnd.getTime() - ms);\n\nfunction iso(d) {\n  return d.toISOString().split('.')[0] + 'Z';\n}\n\nreturn [\n  {\n    json: {\n      timeWindow: {\n        currentStart: iso(currentStart),\n        currentEnd: iso(currentEnd),\n        prevStart: iso(prevStart),\n        prevEnd: iso(prevEnd),\n      }\n    }\n  }\n];\n"
},
"typeVersion": 2
},
{
"id": "ecbf350d-858c-4959-9e1a-77f59ad8772d",
"name": "Fetch Order API",
"type": "n8n-nodes-base.httpRequest",
"position": [
1020,
240
],
"parameters": {
"url": "https://{your_wocommerce_domain}/wp-json/wc/v3/orders",
"options": [],
"sendQuery": true,
"authentication": "genericCredentialType",
"genericAuthType": "httpBasicAuth",
"queryParameters": {
"parameters": [
[]
]
}
},
"credentials": {
"httpBasicAuth": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 4.3
},
{
"id": "2e89c61b-d2b4-444c-8b91-36ecaefded9e",
"name": "Retrieve Refund API",
"type": "n8n-nodes-base.httpRequest",
"position": [
1470,
205
],
"parameters": {
"url": "=https://{your_wocommerce_domain}/wp-json/wc/v3/refunds",
"options": [],
"authentication": "genericCredentialType",
"genericAuthType": "httpBasicAuth"
},
"credentials": {
"httpBasicAuth": {
"id": "credential-id",
"name": ""
}
},
"executeOnce": false,
"retryOnFail": false,
"typeVersion": 4.3,
"alwaysOutputData": false
},
{
"id": "0e2a51dd-9df1-4ec1-8fd4-00076b35ecb9",
"name": "Map Orders to Refunds",
"type": "n8n-nodes-base.code",
"position": [
1435,
460
],
"parameters": {
"jsCode": "// Get data from specific nodes by name\nconst orders = $items(\"Fetch Order API\");\nconst refunds = $items(\"Retrieve Refund API\");\n\nconst output = [];\n\n// Create lookup map for orders\nconst orderMap = {};\nfor (const o of orders) {\n  orderMap[o.json.id] = o.json;\n}\n\n// Loop refunds and attach line items\nfor (const r of refunds) {\n  const refund = r.json;\n  const order = orderMap[refund.parent_id];\n\n  if (!order || !order.line_items?.length) continue;\n\n  for (const li of order.line_items) {\n    output.push({\n      order_id: refund.parent_id,\n      refund_id: refund.id,\n      sku: li.sku || li.name || li.product_id,\n      quantity: li.quantity,\n      reason: refund.reason,\n      refund_date_utc: refund.date_created_gmt\n    });\n  }\n}\n\nreturn output.map(o => ({ json: o }));\n "
},
"typeVersion": 2
},
{
"id": "22b0ae06-01a6-4ae9-b9eb-2c253b7bef54",
"name": "Aggregate Return Metrics",
"type": "n8n-nodes-base.code",
"position": [
980,
480
],
"parameters": {
"jsCode": "// ================= CONFIG =================\nconst WINDOW_HOURS = 24;\n\n// ================= TIME WINDOWS =================\nconst now = new Date();\nconst currentStart = new Date(now.getTime() - WINDOW_HOURS * 60 * 60 * 1000);\nconst previousStart = new Date(currentStart.getTime() - WINDOW_HOURS * 60 * 60 * 1000);\n\n// ================= AGGREGATION MAP =================\nconst stats = {}; // \u2705 THIS WAS MISSING (root cause)\n\n// ================= PROCESS RETURNS =================\nfor (const item of items) {\n  const sku =\n    item.json.sku ||\n    item.json.product_id ||\n    \"UNKNOWN_SKU\";\n\n  const refundDateRaw = item.json.refund_date_utc;\n  const reason = item.json.reason || \"Unknown\";\n\n  if (!refundDateRaw) continue;\n\n  const refundDate = new Date(refundDateRaw);\n  if (isNaN(refundDate)) continue;\n\n  if (!stats[sku]) {\n    stats[sku] = {\n      current: 0,\n      previous: 0,\n      reasons: {}\n    };\n  }\n\n  // \ud83d\udc49 Count refunds (NOT quantity \u2014 more reliable)\n  if (refundDate >= currentStart) {\n    stats[sku].current += 1;\n  } else if (refundDate >= previousStart && refundDate < currentStart) {\n    stats[sku].previous += 1;\n  }\n\n  stats[sku].reasons[reason] =\n    (stats[sku].reasons[reason] || 0) + 1;\n}\n\n// ================= BUILD OUTPUT =================\nconst output = [];\n\nfor (const sku in stats) {\n  const current = stats[sku].current;\n  const previous = stats[sku].previous;\n\n  const absolute_increase = current - previous;\n\n  const percent_increase =\n    previous === 0\n      ? (current > 0 ? null : 0) // null = no baseline\n      : Math.round((absolute_increase / previous) * 100);\n\n  output.push({\n    json: {\n      sku,\n      current_returns: current,\n      previous_returns: previous,\n      absolute_increase,\n      percent_increase,\n      reasons: stats[sku].reasons\n    }\n  });\n}\n\nreturn output;\n"
},
"typeVersion": 2
},
{
"id": "02cfb150-eb94-4184-9fb2-1079012e4c1f",
"name": "Return Surge Check",
"type": "n8n-nodes-base.if",
"position": [
600,
440
],
"parameters": {
"options": [],
"conditions": {
"options": {
"version": 2,
"leftValue": "",
"caseSensitive": true,
"typeValidation": "strict"
},
"combinator": "or",
"conditions": [
{
"id": "b0851e90-a23d-45d7-9ff9-8b2ac3058d31",
"operator": {
"type": "number",
"operation": "gte"
},
"leftValue": "={{ $json.percent_increase }}",
"rightValue": 100
},
{
"id": "71ef4b6f-f439-47a5-b1ed-7c5b381b06d7",
"operator": {
"type": "number",
"operation": "gte"
},
"leftValue": "={{ $json.current_returns }}",
"rightValue": 25
}
]
}
},
"typeVersion": 2.2
},
{
"id": "805bd643-a0da-4bac-9767-a01201809d24",
"name": "Assign Alert Fields",
"type": "n8n-nodes-base.set",
"position": [
155,
485
],
"parameters": {
"options": [],
"assignments": {
"assignments": [
{
"id": "27d7d91b-4e21-4bb8-8c61-bbb9d91f3eb3",
"name": "status",
"type": "string",
"value": "alerted"
},
{
"id": "36e7c447-0b6f-41c1-b133-3295deeca6a5",
"name": "run_date_utc",
"type": "string",
"value": "={{ new Date().toISOString() }}"
},
{
"id": "289792bc-e6bd-4525-a18f-c5a9b1c983d0",
"name": "cooldown_key",
"type": "string",
"value": "={{ $json.sku + \"_\" + new Date().toISOString().slice(0,10) }}"
}
]
},
"includeOtherFields": true
},
"typeVersion": 3.4
},
{
"id": "4542948e-6687-4eb7-9377-8513ccf0a34f",
"name": "Post Slack Alert",
"type": "n8n-nodes-base.slack",
"position": [
275,
715
],
"webhookId": "d384f50d-31c0-4cf2-9ae4-8014d1ba727f",
"parameters": {
"text": "=\u26a0\ufe0f Return Surge Detected\n\nSKU: {{$json.sku}}\nIncrease: {{$json.percent_increase ?? 'N/A'}}%\n\nCurrent Returns: {{$json.current_returns}}\nPrevious Returns: {{$json.previous_returns}}\n\nReasons:\n{{ Object.entries($json.reasons ?? {})\n  .map(r => r[0] + \" : \" + r[1])\n  .join(\"\\n\") }}\n\nStatus: {{$json.status}}\nRun Date (UTC): {{$json.run_date_utc}}\nCooldown Key: {{$json.cooldown_key}}\nAction: Please review recent orders, packaging, and QC logs for this SKU.\n",
"select": "channel",
"channelId": {
"__rl": true,
"mode": "list",
"value": "[YOUR_ID]",
"cachedResultName": "n8n-demo"
},
"otherOptions": {
"includeLinkToWorkflow": false
}
},
"credentials": {
"slackApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 2.3
},
{
"id": "bfd46423-5da8-43f6-8224-8620810c15c7",
"name": "Parse Slack Payload",
"type": "n8n-nodes-base.code",
"position": [
720,
655
],
"parameters": {
"jsCode": "const output = [];\n\nfor (const item of items) {\n  const text = item.json.message?.text || \"\";\n\n  // Helper function\n  const getMatch = (regex) => {\n    const m = text.match(regex);\n    return m ? m[1].trim() : null;\n  };\n\n  // Extract basic fields\n  const sku = getMatch(/SKU:\\s*(.+)/);\n  const increaseRaw = getMatch(/Increase:\\s*([^\\n]+)/);\n  const currentReturns = getMatch(/Current Returns:\\s*(\\d+)/);\n  const previousReturns = getMatch(/Previous Returns:\\s*(\\d+)/);\n  const status = getMatch(/Status:\\s*(.+)/);\n  const runDateUtc = getMatch(/Run Date \\(UTC\\):\\s*(.+)/);\n  const cooldownKey = getMatch(/Cooldown Key:\\s*(.+)/);\n\n  // Percent increase (handle N/A)\n  const percentIncrease =\n    increaseRaw && increaseRaw !== \"N/A%\"\n      ? parseInt(increaseRaw.replace(\"%\", \"\"), 10)\n      : null;\n\n  // Extract reasons block\n  const reasonsBlockMatch = text.match(/Reasons:\\n([\\s\\S]*?)\\n\\nStatus:/);\n  const reasonsText = reasonsBlockMatch ? reasonsBlockMatch[1].trim() : \"\";\n\n  // Convert reasons into object\n  const reasons = {};\n  reasonsText.split(\"\\n\").forEach(line => {\n    const parts = line.split(\":\");\n    if (parts.length === 2) {\n      const reason = parts[0].trim();\n      const count = parseInt(parts[1].trim(), 10);\n      if (!isNaN(count)) {\n        reasons[reason] = count;\n      }\n    }\n  });\n\n  output.push({\n    json: {\n      sku,\n      current_returns: currentReturns ? parseInt(currentReturns, 10) : null,\n      previous_returns: previousReturns ? parseInt(previousReturns, 10) : null,\n      percent_increase: percentIncrease,\n      reasons_raw: reasonsText,               // human-readable\n      reasons_json: JSON.stringify(reasons),  // machine-readable\n      status,\n      run_date_utc: runDateUtc,\n      cooldown_key: cooldownKey\n    }\n  });\n}\n\nreturn output;\n"
},
"typeVersion": 2
},
{
"id": "9af0266e-0136-4605-9c04-1b1974633b9a",
"name": "Log Alert Record",
"type": "n8n-nodes-base.airtable",
"position": [
1160,
725
],
"parameters": {
"base": {
"__rl": true,
"mode": "list",
"value": "[YOUR_ID]",
"cachedResultUrl": "https://airtable.com/[YOUR_ID]",
"cachedResultName": "n8n Learning"
},
"table": {
"__rl": true,
"mode": "list",
"value": "[YOUR_ID]",
"cachedResultUrl": "https://airtable.com/[YOUR_ID]",
"cachedResultName": "woocommerce"
},
"columns": {
"value": {
"sku": "={{ $json.sku }}",
"resons": "={{ $json.reasons_raw }}",
"cooldown_key": "={{ $json.cooldown_key }}",
"run_date_utc": "={{ $json.run_date_utc }}",
"current_returns": "={{ $json.current_returns }}",
"percent_increase": "={{ $json.percent_increase }}",
"previous_returns": "={{ $json.previous_returns }}"
},
"schema": [
{
"id": "sku",
"type": "string",
"display": true,
"removed": false,
"readOnly": false,
"required": false,
"displayName": "sku",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "current_returns",
"type": "number",
"display": true,
"removed": false,
"readOnly": false,
"required": false,
"displayName": "current_returns",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "previous_returns",
"type": "number",
"display": true,
"removed": false,
"readOnly": false,
"required": false,
"displayName": "previous_returns",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "percent_increase",
"type": "number",
"display": true,
"removed": false,
"readOnly": false,
"required": false,
"displayName": "percent_increase",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "run_date_utc",
"type": "string",
"display": true,
"removed": false,
"readOnly": false,
"required": false,
"displayName": "run_date_utc",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "status",
"type": "options",
"display": true,
"options": [],
"removed": true,
"readOnly": false,
"required": false,
"displayName": "status",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "cooldown_key",
"type": "string",
"display": true,
"removed": false,
"readOnly": false,
"required": false,
"displayName": "cooldown_key",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "resons",
"type": "string",
"display": true,
"removed": false,
"readOnly": false,
"required": false,
"displayName": "resons",
"defaultMatch": false,
"canBeUsedToMatch": true
}
],
"mappingMode": "defineBelow",
"matchingColumns": [],
"attemptToConvertTypes": false,
"convertFieldsToString": false
},
"options": [],
"operation": "create"
},
"credentials": {
"airtableTokenApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 2.1
}
],
"active": false,
"pinData": [],
"settings": {
"executionOrder": "v1"
},
"versionId": null,
"connections": {
"Return Surge Check": {
"main": [
[
{
"node": "Assign Alert Fields",
"type": "main",
"index": 0
}
]
]
},
"Fetch Order API": {
"main": [
[
{
"node": "Retrieve Refund API",
"type": "main",
"index": 0
}
]
]
},
"Compute Time Window": {
"main": [
[
{
"node": "Fetch Order API",
"type": "main",
"index": 0
}
]
]
},
"Assign Alert Fields": {
"main": [
[
{
"node": "Post Slack Alert",
"type": "main",
"index": 0
}
]
]
},
"Retrieve Refund API": {
"main": [
[
{
"node": "Map Orders to Refunds",
"type": "main",
"index": 0
}
]
]
},
"Map Orders to Refunds": {
"main": [
[
{
"node": "Aggregate Return Metrics",
"type": "main",
"index": 0
}
]
]
},
"Aggregate Return Metrics": {
"main": [
[
{
"node": "Return Surge Check",
"type": "main",
"index": 0
}
]
]
},
"Post Slack Alert": {
"main": [
[
{
"node": "Parse Slack Payload",
"type": "main",
"index": 0
}
]
]
},
"Log Alert Record": {
"main": [
[]
]
},
"Scheduled Run Trigger": {
"main": [
[
{
"node": "Compute Time Window",
"type": "main",
"index": 0
}
]
]
},
"Parse Slack Payload": {
"main": [
[
{
"node": "Log Alert Record",
"type": "main",
"index": 0
}
]
]
}
}
}