n8n automation
Webhooks, API integrations and scheduled jobs that do the repetitive work. Self-hosted on your own server when the data has to stay there, on n8n Cloud when it does not.
Most businesses do not need another subscription. They need the tools they already pay for to talk to each other. n8n is the workflow engine I use for that: it connects your forms, inbox, CRM, spreadsheets and database, and runs the steps you now do by hand.
I build the workflow, host it, and hand it over with documentation. If you want it on your own infrastructure, I install n8n in Docker on a VPS, put it behind HTTPS, and set up backups so a year of work does not disappear with the server.
What I build
- Lead intake that routes form submissions, emails and messages to the right person with the right context attached.
- Document and invoice flows that generate the file, store it and send it without anyone opening a template.
- CRM and spreadsheet sync, so two systems stop drifting apart.
- Scheduled reports that land in Slack, Discord or your inbox every morning.
- Error handling that retries, deduplicates and tells you when something actually needs a human.
Self-hosted setups
- n8n in Docker on your VPS, behind a reverse proxy with a real certificate.
- Postgres instead of the default database, so executions survive a restart.
- Backups of workflows and credentials, plus a restore you have seen work.
- Authentication on the editor and a separate entry point for public webhooks.
- Uptime monitoring, so you hear about a failed workflow before your customer does.
Questions
about this
Can you work with my existing n8n instance?
Yes. I can review what is already there and extend it, or rebuild the parts that keep failing. If it is self-hosted I also check the version, the database and whether backups actually exist.
Self-hosted or n8n Cloud?
Cloud is faster to start and fine for most workflows. Self-hosting makes sense when data cannot leave your infrastructure, when you run a high volume of executions, or when you need unrestricted code steps. I build for both and will tell you which one your case needs.
What if an integration does not exist in n8n?
Then it becomes an HTTP request against the API, or a small code node. Anything with a documented API can be connected.
How do I know it keeps working?
Every workflow gets error handling and a failure notification. Self-hosted setups get monitoring on top of that. Silent failure is the one thing an automation must never do.
Do I need to be technical?
No. You describe the process the way you would explain it to a new colleague. I ask the questions that matter and build from there.
Want this for your business?