Automation library · E-commerce

Detect WooCommerce return surges in real-time with Slack

Started by a clock, and works across Airtable and Slack. 11 steps, 1 branch: a working afternoon to understand properly.

Medium

11 stepsMedium: a working afternoon
1Branch: places the flow splits
0Loops or waits
2Services it connects to

The flow

Starts it 1Logic 6Service 4

The steps in the order they run, from what starts it.

  1. 1Schedule TriggerSchedule triggerStarts it
  2. 2Time_windowCodeLogic
  3. 3HTTP OrdersHttp RequestService
  4. 4HTTP RefundsHttp RequestService
  5. 5Orders_FetchCodeLogic
  6. 6Refund_detailsCodeLogic
  7. 7IfIfLogic
  8. 8Edit Fields1SetLogic
  9. 9Send a messageSlackService
  10. 10Code in JavaScriptCodeLogic
  11. 11Create a recordAirtableService

How it's built

Starts on
A clock
Steps
11, with 1 branch
Size
Medium: a working afternoon
Connects to
Airtable, Slack
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Airtable and Slack accounts. You connect your own accounts after importing it; none are included.

What starts it?

It starts on a clock.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Plan an afternoon. 11 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 11 steps before you point it at anything that matters.