Automation library · E-commerce

Restaurant Menu Ordering System

Started by another system calling it, and works across n8n data table. 13 steps: a working afternoon to understand properly.

Medium

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

The flow

Starts it 9Logic 1Service 3

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

  1. 1MenuWebhookStarts it
  2. 2Restaurant ScreenWebhookStarts it
  3. 3Finish WebhookStarts it
  4. 4Order receivingWebhookStarts it
  5. 5Check for order updatesWebhookStarts it
  6. 6Respond to WebhookRespond To WebhookStarts it
  7. 7Code in JavaScriptCodeLogic
  8. 8Delete row(s)Data TableService
  9. 9Insert rowData TableService
  10. 10Get row(s)1Data TableService
  11. 11Respond to Webhook1Respond To WebhookStarts it
  12. 12Respond to Webhook3Respond To WebhookStarts it
  13. 13Respond to Webhook2Respond To WebhookStarts it

How it's built

Starts on
Another system calling it
Steps
13
Size
Medium: a working afternoon
Connects to
n8n data table
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

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