Connect Salesflare to HubSpot with n8n: Auto-Sync Contacts

If you run Salesflare as your pipeline CRM and HubSpot as your marketing hub, you already know the problem: a contact closes a discovery call in Salesflare and nothing happens on the HubSpot side until someone remembers to copy it over. There is no native Salesflare HubSpot integration. No Zapier template covers it cleanly. The gap is real, and it costs you follow-up lag. This tutorial walks through an n8n workflow that polls the Salesflare API, upserts contacts into HubSpot, and enrolls them in a sequence automatically. I’d recommend this approach over any point-and-click alternative for teams that care about deduplication logic and field-level control.

Why this workflow exists and what it actually does

Salesflare is built around automatic data capture, pulling contact and company data from your email, calendar, and LinkedIn activity without manual CRM entry. Genuinely useful for a leaner sales team. HubSpot, on the other hand, is where most B2B marketing teams run lifecycle nurturing, sequence enrollment, and lead scoring. When those two systems don’t talk, you either duplicate contacts by hand or let warm leads go cold.

The workflow described here runs on a 15-minute Schedule Trigger in n8n. It calls the Salesflare contacts endpoint filtered by modificationDate, maps the response fields to HubSpot contact properties, upserts by email to avoid duplicates, and conditionally enrolls the contact in a HubSpot sequence based on a lifecycle stage field. The whole thing runs in under 30 nodes and costs nothing beyond your n8n instance, since both APIs are accessible on paid tiers of each tool.

Per the Salesflare API docs, the contacts endpoint supports date_from filtering so you page through only recently modified records rather than dumping your entire database on every run. That detail matters at scale.

Build the workflow step by step

The deduplication trap and how to fix it

The most common failure in contact sync workflows is running upserts without understanding how HubSpot resolves identity. HubSpot deduplicates on email by default, but if a contact in HubSpot was created with different email casing or has no email at all, the upsert creates a duplicate instead of updating. The fix: always normalize email to lowercase before the HubSpot node using a Code node or a Set node with a .toLowerCase() expression.

My read is that this single normalization step prevents more re-work than any other part of the build. Don’t skip it.

// Code node: normalize email before HubSpot upsert
const items = $input.all();
return items.map(item => {
  item.json.email = (item.json.email || '').toLowerCase().trim();
  return item;
});

A second gotcha: per the HubSpot Knowledge Base, the Sequences enrollment API requires the contact to have a connected inbox assigned, and it only works for contacts owned by a user with a Sales Hub Seat. If your upserted contact has no owner assigned, the enrollment call returns a 400. Add an owner assignment step in your workflow before the enrollment node, pulling the owner from the Salesflare account owner field.

Alternatives if n8n is not in your stack

If you are not running n8n already, the honest comparison is between Zapier and Clay as the two realistic alternatives.

Which middleware fits your Salesflare to HubSpot sync?

Choose n8n if

• You want full control over dedup logic, field mapping, and conditional enrollment without per-task pricing
• Your team can maintain a self-hosted or cloud n8n instance
• You are already running other n8n workflows and want one platform for orchestration

From $20/mo cloud or self-hosted free Try n8n →

Choose Zapier if

• You want the fastest possible setup and are comfortable with Zapier's Salesflare trigger app
• Your contact volume is low enough that per-task pricing does not hurt
• You do not need custom deduplication or multi-step conditional logic

From $19.99/mo, per-task at scale Try Zapier →

Choose Clay if

• You want to enrich contacts pulled from Salesflare before pushing to HubSpot
• Your use case is prospecting and you need waterfall enrichment baked into the sync
• You are building outbound sequences, not just CRM hygiene

From $149/mo Try Clay →

If you are already running Make for other automations, Make has a Salesflare module in its marketplace, which gets you similar control to n8n with a visual canvas. I covered some of the patterns that apply there in my Make lead generation workflow builds post.

If you are thinking about moving workflow logic out of HubSpot entirely and into n8n, the HubSpot Workflows to n8n migration playbook is worth reading alongside this tutorial. It covers the edge cases around enrollment triggers and contact property history that bite teams who assume the switch is purely structural.

Putting it together

The Salesflare to HubSpot sync via n8n looks more intimidating than it is. You are making two API calls, normalizing one field, and running a conditional branch on a contact property. The polling schedule and the timestamp variable management are the only parts that require real attention. Once it runs clean, your sales team’s Salesflare activity feeds directly into HubSpot nurturing without anyone touching a keyboard. That handoff is where most RevOps setups lose leads. This workflow closes it.