Home › Services › n8n automation
// service
n8n automation — self-hosted, no per-task bill
n8n is what I use when a client wants the automation on their own server, needs custom code in the middle of a flow, or runs enough volume that per-operation pricing stops making sense. The contact form on this very site runs through a self-hosted n8n instance: webhook → spam filter → Telegram, Google Sheets and Gmail in parallel.
What I do with n8n
- Install and secure an instance on DigitalOcean, Hetzner or your own VPS — Docker, HTTPS, backups, credential setup for Google, Telegram, your CRM.
- Build the workflows — webhooks from your site or forms, CRM and spreadsheet sync, Telegram and email notifications, scheduled reports.
- AI nodes — OpenAI and Claude steps for classification, drafting and summaries, with a review step for anything customer-facing.
- Code nodes where no-code stops: data reshaping, signatures, pagination, odd APIs.
- Migration from Make.com or Zapier when the per-task bill or a missing feature makes the move worth it.
When n8n is the right call — and when it isn't
| Choose n8n when | Choose Make.com when |
|---|---|
| Data must stay on your server (contracts, EU residency, internal policy) | Nobody on the team wants to look after a server |
| Volume is high enough that per-operation pricing hurts | Volume is modest and a standard plan covers it |
| You need custom code steps or unusual APIs | Every app you use has a native Make.com module |
| Developers will extend the flows later | Operations staff will maintain the flows in a visual editor |
Not sure? That is a ten-minute question on the discovery call, and I will tell you if Make.com is the cheaper answer.
What you get
- Instance and workflows in your account and on your server — credentials under your Google / Telegram / CRM logins.
- Error workflow that alerts you (Telegram or email) when a run fails, with the payload attached.
- Walkthrough video and documentation; 30 days of support after handoff.
How a project runs
- Discovery call (free, 30 min). You walk me through the process; I ask about volumes, tools and who maintains the result.
- Written scope. Every step mapped, tools named, what "done" looks like, timeline and a fixed price. Nothing starts before you approve it.
- Build with test data. Error handling, retries and alerts are part of the build, not an extra.
- Review. You test against the scope checklist; fixes to anything off-scope are included.
- Handoff. Walkthrough video, step-by-step documentation, credentials in your accounts. Then 30 days of support.
Related work
Lead Processing Pipeline
Website form → HubSpot CRM → Telegram alert to sales → personalised email auto-reply. Zero manual steps.
Read the case →AI Report Generator
Google Sheets data → Claude API summary → formatted report in the owner's inbox every Monday at 9:00.
Read the case →
AI Content Machine
Telegram message (photo, text or voice) → Whisper transcript → GPT-4o post copy → DALL·E image → Google Drive + Sheets → finished post back in Telegram.
Read the case →Questions
Make.com or n8n — which should we choose?
We already use a specific CRM or tool — can you work with what we have?
Who owns the automation afterwards?
What happens when something breaks or our tools change? Are we stuck waiting on you every time?
Describe your process
Which tools are involved, what is done by hand today, how often. I reply within 24 hours with a fit/no-fit answer and, if it fits, a fixed quote.