n8n Restaurant Automation: 5 Workflows That Run Your Menu While You Cook

Get started free →

n8n restaurant automation means the boring parts of running your menu — the morning stop-list, the "table 7 ordered" shout, the Monday numbers email — happen on their own, on a schedule, without anyone touching the dashboard. Disho ships an official n8n community node, n8n-nodes-disho, so your QR menu becomes something workflows can read and edit like any other system. Here is the 3-step setup and five real n8n use cases, each with the exact node chain and the hours it buys back.

What is n8n, and why would a restaurant automate anything?

n8n is a workflow automation tool — a visual pipeline builder where you snap together triggers ("every day at 10:00", "new row in a spreadsheet") and actions ("send a Telegram message", "update a dish") without writing code. Restaurants use it because hospitality admin is brutally repetitive: the same stop-list ritual every morning, the same numbers every Monday.

Restaurant workflow automation is not about replacing people. It's about the 30–60 minutes a day a chef or manager spends on tasks a machine does better: copying inventory into the menu, watching for orders, formatting a sales summary. n8n is open source, can be self-hosted (a good match if you already run Disho in Docker), and its free tier covers everything in this article.

How do you connect Disho to n8n? (3 steps, ~5 minutes)

Setup is three steps: install the community node, mint an API key in the Disho dashboard, and paste it into an n8n credential. No developer, no OAuth dance — about five minutes on any n8n 1.x instance.

1. Install the node. In n8n go to Settings → Community Nodes → Install and enter n8n-nodes-disho. It's published on npm with provenance, so n8n can verify it came from Disho's build pipeline.
2. Mint an API key. In the Disho dashboard open Team → Connected apps → "+ API key", name it something like n8n-production, and copy the key. It is shown exactly once — store it straight into n8n, not into a note. Owners and managers can create keys; staff accounts cannot.
3. Create the credential. In n8n add a Disho credential, paste the key, save. Every Disho node in every workflow now authenticates with it, acting with your live role.

The node then exposes everything the recipes use: Menu (Get), Dish (Create / Update / Set Availability / Delete / Generate AI Content), Order (Get Many / Update Status), Table (Get Many with QR URLs), Analytics (today / 7d / 30d), and Wallet (Get Balance).

Recipe 1: How do you automate the morning stop-list?

The workflow reads your inventory sheet at 10:00, switches unavailable dishes off in the menu, and messages the chef a summary — so guests never order the sea bass you ran out of yesterday. This is the highest-value automate restaurant menu use case: a stale stop-list always ends in an awkward apology at the table.

• Trigger: Schedule Trigger, daily at 10:00 (before doors open).
• Chain: Google Sheets (read the inventory tab, or your inventory system's node) → a small Filter for rows marked out-of-stock → Disho Dish → Set Availability per dish → Telegram message to the kitchen chat: "Off today: sea bass, tartare. Everything else on."
• Payoff: 15–20 minutes of manual toggling every morning, gone — roughly 2 hours a week — plus zero "sorry, we're out of that" moments after a guest has already chosen.

Recipe 2: How do you get instant new-order alerts in Telegram or Slack?

A one-minute polling workflow fetches orders with status new and posts anything unseen to your kitchen channel, so the line hears about orders even when nobody is watching the dashboard. Disho already pushes orders to the kitchen screen in real time with a sound alert; this recipe is for teams who live in a chat app or want a second device covered.

• Trigger: Schedule Trigger, every minute.
• Chain: Disho Order → Get Many (status = new, limit 20) → Filter out already-announced order IDs (n8n's static data works) → Telegram/Slack message with table number and items → optionally Disho Order → Update Status to move orders along New → Accepted → Ready → Served from chat reactions.
• Payoff: the 2–3 minutes an unnoticed ticket sits idle on a packed Friday disappear. Across 40 orders a night, that's real minutes off average serve time.

Recipe 3: How do you automate the weekly owner report?

Every Monday at 9:00, a workflow pulls 7-day analytics — revenue, average ticket, top dishes, busiest hours — formats them into a short digest, and emails it to the owner. No more logging in just to check the week.

• Trigger: Cron, Mondays 09:00.
• Chain: Disho Analytics → Get (period = 7d) → a Set/Code node to format the numbers into readable lines ("Revenue €8,340, avg ticket €31.20, top dish: burrata — 84 sold") → Gmail or Slack.
• Payoff: an hour of copy-pasting per week, and a habit most owners never keep manually. Watching average ticket weekly shows whether menu changes work — pair it with how to increase your restaurant's average ticket.

Recipe 4: How do you turn a spreadsheet row into a finished menu item?

Add a row to a Google Sheet — name, price, ingredients — and the workflow creates the dish in Disho and generates an appetizing description with AI. A new special goes from idea to live menu without opening the dashboard.

• Trigger: Google Sheets Trigger, on new row.
• Chain: Disho Dish → Create (name, price) → Disho Dish → Generate AI Content (description, ≈ €0.03 per language — the model sticks to the ingredients you gave it and doesn't invent any) → done. Generate an AI photo (≈ €0.15) on demand for dishes worth showcasing; video generation stays dashboard-only for now.
• Payoff: a 15-dish seasonal menu swap compresses from ~3 hours of typing and wordsmithing into 10 minutes of filling a spreadsheet. See the finished result live on the demo menu.

Recipe 5: How do you run one workflow across multiple venues?

Build the workflow once, create one API key per venue, and loop over the credentials — a three-location group runs the same stop-list or Monday report everywhere with zero copy-paste. Each key is minted in its own restaurant's dashboard, so venues stay cleanly separated.

• Trigger: whatever the underlying recipe uses (Schedule, Cron, Sheet).
• Chain: a list of venues → Loop Over Items → the same Disho nodes, switching credentials per venue → one combined summary message to the ops chat.
• Payoff: every recipe above multiplies by your venue count for free. For five venues, the weekly report alone saves five owner-hours, and menu changes roll out chain-wide in one run.

Is it safe to give n8n a key to your restaurant?

Yes, within deliberate limits: the key is displayed exactly once at creation, inherits the creator's live role rather than god-mode, and dies instantly on one-click revoke. n8n and the Claude/ChatGPT MCP connector share one audited API surface and one permission model.

Concretely: a key minted by a manager can do what a manager can do — nothing more. Demote or remove that person and their keys narrow or die with them. Every connection is listed in Team → Connected apps with last-activity time, so a forgotten test key is visible, not lurking. And nothing related to Stripe, payouts, or guest personal data is exposed through the API at all — the worst case for a leaked key is menu and order mischief, not money movement. The one paid operation, Generate AI Content, states its price and draws from your pay-per-use wallet (failed generations are auto-refunded).

Frequently asked questions

Do I need to code to use n8n with Disho? No. Installing the node, creating the credential, and assembling the recipes above is all point-and-click in n8n's visual editor. A Code node helps with fancy report formatting, but every workflow here runs on standard no-code nodes.

Is the API key safe to store in n8n? As safe as your n8n instance. The key is shown once, acts only with its creator's role, is listed with last-activity time in Team → Connected apps, and one-click revoke kills it instantly. Money and guest data aren't reachable through it at all.

Can n8n AI Agents use Disho? Yes — the node is marked usableAsTool, so an n8n AI Agent can call Disho operations as tools: check today's analytics, stop-list a dish, or draft a description from a plain-language instruction.

Does automation replace the Disho dashboard? No. The kitchen still gets real-time orders with sound alerts, and staff still work in the dashboard during service. n8n handles the scheduled, repetitive work around it.

What does running this cost? The node and API keys are free, as is n8n's self-hosted community edition. Only AI generation is paid: ≈ €0.15 per photo and ≈ €0.03 per description language, from your Disho wallet.

→ QR Menu for Restaurants: How It Works and Why Use One