Someone in this category wrote that “I know n8n” can mean anything from dragging a few nodes
around to building sub-workflow architectures with proper error handling. Fair. So here is
what I actually built, and you can judge which one I am.
WHAT IS RUNNING RIGHT NOW
A 61-node LLM sales agent for a uniform and medical-supply distributor. Telegram today,
WhatsApp Cloud API tested and ready. It takes orders, confirms every customization item by
item, and sends the ticket to fulfillment.
The part that matters: the model never touches a price. Prices and stock come from a separate
sub-workflow that reads the live catalog. The agent asks, the sub-workflow answers. A model
that invents a price is the fastest way to lose a client, so it simply cannot.
Other guardrails in that build: per-user spend and rate limits on the LLM, idempotency on the
message trigger (Telegram resends when n8n is slow — without it, one order becomes two),
HTML escaping on every reply, and a human handoff path.
THE ERROR HANDLING PART
I wrote a flow that runs at 6:00 every morning and tests the four things the bot depends on:
the data source, the database, the LLM, and the messaging channel. Not “is there an error” —
does it actually work.
It earned its keep the first week. A delivery was failing while returning success codes.
n8n logged green, the tool said SENT, the bot repeated it to the customer. An error alert
would never have caught that, because nothing was erroring.
INFRASTRUCTURE
My own n8n, self-hosted: Ubuntu, Docker, Caddy with automatic TLS, key-only SSH, daily
volume backups with rotation, and an uptime watcher running outside the server — because a
monitor that lives on the box it monitors is decoration.
I mention it because if you self-host, I have already hit the walls you are about to hit.
BACKGROUND
Seven years running US healthcare operations from Colombia: insurance eligibility, DME
billing, ICD-10, HIPAA. I built and ran a BPO to $100K+/month with a 10-person team. That
matters here for one reason: I am used to workflows where a mistake has a cost, and I build
like it.
WHERE I AM NOT YOUR GUY
I am not a software engineer by trade. If you need a custom node in TypeScript, a React
frontend, or someone to own a codebase, hire a developer. What I do is make n8n behave in
production and stay boring after handoff.
HOW I WORK
I am in Colombia (UTC-5), so I overlap with US hours all day. English C1, Spanish native —
useful if your users write in Spanish and your team does not.
Tell me the trigger, the destination, what the output should look like, and what should
happen when it fails. If I cannot answer those four, I will say so instead of quoting.
Contact: andresjmnz92@gmail.com