Automation library · E-commerce

Handle order status webhooks with Microsoft SQL Server

Started by another system calling it, and works across Email. 12 steps, 2 branches: a working afternoon to understand properly.

Medium

12 stepsMedium: a working afternoon
2Branches: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 6Logic 4Service 2

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

  1. 1Order Status WebhookWebhookStarts it
  2. 2Validate PayloadIfLogic
  3. 3Format DataSetLogic
  4. 4Error ResponseRespond To WebhookStarts it
  5. 5Route By StatusSwitchLogic
  6. 6Approved ResponseRespond To WebhookStarts it
  7. 7Prepare Rejection EmailSetLogic
  8. 8Pending ResponseRespond To WebhookStarts it
  9. 9Completed ResponseRespond To WebhookStarts it
  10. 10Send Rejection EmailEmail SendService
  11. 11Log RejectionMicrosoft SqlService
  12. 12Rejection ResponseRespond To WebhookStarts it

How it's built

Starts on
Another system calling it
Steps
12, with 2 branches
Size
Medium: a working afternoon
Connects to
Email
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

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

What starts it?

It starts on another system calling it.

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. 12 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 12 steps before you point it at anything that matters.