I will build documented n8n workflows with error handling


About this gig
Documented n8n automation, built so you can still change it in six months. I build one n8n workflow that runs by itself - Google Sheets, email, Telegram, webhooks, HTTP APIs - and hand over the documentation with it.
WHAT YOU GET
The workflow built and tested in n8n, exported as JSON that is yours
A written run-book: what every node does, what to change to adapt it, how to test it
A flow diagram of the whole automation
Error handling and a failure alert on the step that can break - standard, not an extra
Named nodes and notes on the canvas, so the next person can read it
FIXED SCOPE, FIXED PRICE
One workflow = one trigger, one outcome, and the apps in your package. If your idea needs more than that, I tell you the price before you order, not halfway through.
WHY ME
he same building blocks run on my own self-hosted n8n today, in 20 active workflows: scheduled runs, IMAP reply detection, Google Sheets as the database, Telegram alerts.
Tell me the trigger, the apps and the outcome, and I will tell you whether it fits one workflow before you order.
Get to know Sam T.
n8n Automation for Small Businesses: Orders, Leads, Reports
- FromGermany
- Member sinceDec 2019
Languages
German, English, French
My Portfolio
FAQ
What happens when it breaks, and do I own the workflow?
You own it: it runs in your n8n under your accounts, and you get the JSON file. If it breaks because I built it wrong, I fix it free (7, 14 or 30 days by package). If an app changes its API, that is a small paid job, and the failure alert tells you right away.
What exactly counts as "one workflow"?
One trigger, one outcome, and the apps in your package. A trigger is a schedule, a webhook or form, an incoming email, or a new sheet row. A second trigger or a second unrelated outcome is a second workflow, and I quote it before you order, never mid-delivery.
Do I need my own n8n, and what will it cost me to run?
Yes, it runs in your n8n, not mine. n8n Cloud is a paid plan with a free trial; self-hosting costs a small server. I build the same way for both. You pay only for services you already use. No n8n yet? Ask before you order and I tell you which option fits.
Do you need my passwords?
No, and please don't send them in chat. Invite me to your n8n as a member and connect the accounts yourself, or I build with empty credentials and you add your keys at the end. The run-book shows which node needs what. The file I deliver contains no keys.
My app isn't a standard n8n integration. Can you still do it?
Usually yes. Anything with a documented REST API connects through an HTTP request step. Send me the link to your app's API docs before you order and I tell you honestly whether it works, needs a bigger package, or can't be done. German or English, both fine.

