Hi everyone,
I wanted to share something that started as a very practical n8n problem.
I was building a WhatsApp chatbot + n8n workflow to take online orders for our restaurant.
The automation part worked great: incoming message → parse → create order → send confirmation.
But then I hit a wall: I couldn’t automatically print the order for our kitchen.
What I ran into:
- Cloud workflows don’t naturally “reach” printers behind firewalls.
- Printers / Windows machines disconnect, out of paper, reboot, or go offline.
- Most options either require VPN/local server setup, or aren’t reliable enough for production.
Because I work remotely, I needed a confirmation back (did it print? what happened?).
So I ended up building an “execution layer” (a lightweight agent) that sits between cloud workflows (n8n) and real-world hardware.
No inbound ports needed, the local client runs near the printer and reports outcomes back.
What I built:
- n8n sends a webhook/API call with: printer_id + document/PDF + metadata
- A lightweight local client runs near the printer (Windows) and executes the job
- It reports back status + reason codes (success/fail) so workflows stay auditable
- Built-in retries / queue behavior so it doesn’t break on a single network hiccup
In n8n it’s basically: - Trigger (WhatsApp order / webhook / whatever)
- HTTP Request → send print job
- Use response to notify staff / log / retry / escalate
Why I’m posting
Now I’m at the point where I want practical test feedback from people who run real workflows: - What was your setup (printer type, Windows version, network/firewall situation)?
- Did it “just work” or did you hit issues (install, token, permissions, print driver quirks)?
- What kind of feedback do you expect back in n8n (simple OK/FAIL vs detailed reasons)?
- What would make you trust it enough for production?
If anyone wants to try it, I put a simple page here (Sign in + download + SHA-256): https://ouvitel.com
Any feedback is always useful.