Workflow automation
n8n & Make.com Automation Expert
I build n8n and Make.com workflows that connect your CRM, inbox, spreadsheets and apps, so data moves on its own and your team stops doing the same copy-paste tasks every day.
- n8n
- Make.com
- HubSpot
- Google Sheets
- Slack
- Airtable
Sound familiar?
The problems I solve
The same tasks, every single day
Your team copies data between forms, spreadsheets, CRMs and inboxes. It is slow, boring, and one typo can cost you a customer.
Zapier bills keep climbing
Your automations work, but per-task pricing grows with your business. You want more control and more predictable costs.
Automations break quietly
A scenario failed last week and nobody noticed until a client complained. There are no alerts, no logs and no owner.
Nobody knows how it all fits
Workflows were built over time by different people. There is no map of what triggers what, so every change is a gamble.
What I build
What you get with n8n & Make.com
Custom n8n workflows
Workflows with branching, loops, error handling and code steps where needed, connected to the APIs your business runs on, including tools without a ready-made integration.
Make.com scenarios
Clean, well-named Make scenarios with routers, filters and data stores, built to stay readable for your team.
CRM and lead automation
Leads captured from forms, ads and email, enriched, deduplicated and pushed into HubSpot, GoHighLevel, Pipedrive or Airtable.
Self-hosted n8n
n8n installed on your own server with Docker on AWS or DigitalOcean, with backups, updates, SSL and monitoring handled properly.
Migrations from Zapier
Existing Zaps rebuilt in n8n or Make, tested side by side, then switched over without missing a single run. You get a before-and-after list of every automation and what changed.
Monitoring and documentation
Error alerts to Slack or email, run logs, and a simple map of every workflow so anyone can see what runs where and which accounts each one depends on.
See it in action
Lead routing with n8n
Hover, tap or tab through the steps to see what each one does. Press Run to replay the demo.
- Webhook received: A form, ad platform or app sends the new lead to an n8n webhook instantly.
- Enrich lead data: Company, role and location are looked up from an enrichment API to fill the gaps.
- Duplicate check: n8n checks whether this person already exists so the CRM stays clean.
- Upsert in HubSpot: The contact is created or updated in HubSpot with source and enrichment data.
- Notify on Slack: The owner gets a Slack message with the lead summary and a link to the record.
Webhook received: A form, ad platform or app sends the new lead to an n8n webhook instantly.
How we work
From first call to handover
Discovery call
A free call to understand your goals, current tools and constraints. You leave with a clear idea of what is possible, even if we do not work together.
Scope & quote
A written scope with deliverables, milestones and a quote, so you know exactly what you are getting before any work starts.
Build in weekly milestones
Work ships in weekly slices with a preview link and a short update each time, so you see progress and can steer early.
Handover, docs & support
You get the code, accounts, documentation and a walkthrough video. Ongoing support is available if you want it.
FAQ
n8n & Make.com questions
Make is quick to start, fully hosted and easy for non-developers to follow. n8n is more flexible, handles complex logic and code steps well, and can be self-hosted for predictable costs and full control of your data. I recommend one after looking at your volumes, your team and where your data needs to live. If your data needs to stay on your own infrastructure, or volumes are high, self-hosted n8n usually wins on control and cost. If your team wants the simplest possible tool to maintain, Make is often the better choice.
Yes. I set up self-hosted n8n with Docker on AWS or DigitalOcean, with SSL, backups, update procedures and uptime monitoring, and hand over the credentials so the server belongs to you. Self-hosting means your automation data stays on infrastructure you control, and costs stay flat no matter how many workflows run each month.
Yes. I document your existing Zaps, rebuild them in n8n or Make, run both in parallel while we compare results, and switch over once everything matches. This approach means no lost leads or orders during the switch, and you only cancel Zapier once you are confident everything works.
Every workflow gets error handling: retries for temporary problems, alerts to Slack or email for real failures, and logs that show exactly which step failed and why. I also add a simple daily summary so you can see at a glance how many runs succeeded, how many failed, and which ones need attention.
Yes. That is one of the main benefits of n8n and Make. I keep workflows tidy and well-named, and you get a recorded walkthrough of how each one works. For complex workflows, I add notes inside each step explaining what it does and why, so edits do not accidentally break something downstream.
Yes. Both n8n and Make work well with OpenAI and Claude for classifying messages, extracting data and drafting replies. See my AI Automation service for examples. Adding AI to an existing workflow is often a small change, such as one extra step, that removes the most time-consuming manual decision.