n8n automation for HubSpot and the rest of your stack

HubSpot workflows stop at HubSpot. When a process crosses systems, or needs logic a workflow can’t express, I build it in n8n or Zapier and run it where it makes sense for you.

Short answerUse HubSpot workflows for processes that stay inside HubSpot. Use n8n or Zapier when the process touches other systems or needs custom logic. n8n can also be self-hosted, so the data and the server stay under your control.

What I build

  • Webhook-driven flows that react to HubSpot events, such as writing a link or a status back onto every new deal.
  • Syncs between HubSpot and your ERP, accounting or inventory systems.
  • Scheduled jobs for cleanup, enrichment and reporting.
  • Everyday tools wired in: Gmail, Google Calendar and Sheets, Outlook, Teams, Excel and Slack.
  • AI steps inside a flow, such as using Anthropic’s Claude to categorize records that a fixed rule can’t.
  • Zapier flows when that’s what your team already runs and maintains.

Self-hosted n8n

If you’d rather own the automation layer than rent it, I’ll set it up end to end: a cloud server with a static IP, Docker running n8n with Postgres and Redis, nginx on a dedicated subdomain, and automatic restart tested through a full reboot. Read the write-up.

Built to keep running

  • One process writes each shared value, so parallel runs can’t corrupt it. On one ERP build, n8n was the single writer of inventory across 11 workflows.
  • HubSpot webhooks can batch up to 100 events per request; every flow I build processes the whole batch.
  • Logging and alerts, so a failure is noticed by a person instead of discovered weeks later.

Common questions

Should we use n8n or Zapier?
Zapier is quicker to start with and easier for a non-technical team to maintain. n8n suits more complex logic and higher volumes, and it can be self-hosted. The deciding question is usually who will look after the flows once they’re live.
Can n8n run on our own server?
Yes. n8n can be self-hosted, which keeps your data on infrastructure you control. I’ve set it up on Google Cloud with Docker, Postgres and Redis behind nginx, with automatic restart tested through a full reboot.
When should we use HubSpot workflows instead?
When the process starts and ends inside HubSpot and the logic fits what workflows can express. Reach for n8n or Zapier when the process crosses into other systems or needs logic or data that HubSpot workflows don’t have.
What happens when an automation fails?
Flows log what failed, retry where that is safe, and alert a person where it isn’t. Updates are keyed on record IDs, so a retry can’t create duplicates.

Have a system that needs to talk to HubSpot?

Book a free 30-minute call. Bring the messy version and I’ll help you work out what to fix first.

Book a call