HubSpot’s own integration marketplace is large, but most sales operations teams only need a handful of integrations configured correctly to see a real shift in pipeline velocity and data quality. The harder problem is not which logos to connect, it is understanding how each integration moves data, where sync conflicts happen, and which integrations create dependencies that are painful to unwind later. This guide covers the integrations that matter for sales operations, grouped by function, with the mechanics, tradeoffs and failure modes that decide whether they help or add noise.
Why Sync Architecture Matters More Than the Integration List
Every integration on this list falls into one of three sync patterns: one-way push, one-way pull, or two-way sync with conflict rules. The pattern matters more than the app you choose. A one-way push (form submissions flowing from a webinar tool into HubSpot as new contacts, for example) is low risk because HubSpot only writes in one direction and nothing in HubSpot can overwrite the source system. Two-way sync, as used by the native Salesforce and Dynamics 365 connectors, is where most sales operations pain starts, because both systems can write to the same field, and unless someone defines which system wins for each field, records begin flip-flopping between values on every sync cycle.
Before switching on any two-way integration, define a system of record for each shared field: deal stage, deal owner, close date, and any custom fields both platforms touch. HubSpot’s own developer documentation covers how field-level sync settings work, and getting this wrong is a frequent cause of a sales team losing trust in CRM data within weeks of a new integration going live.
Dedupe keys deserve the same attention. HubSpot matches contacts primarily on email address, while Salesforce and Dynamics 365 often use their own internal record IDs alongside email. When contact records were created independently in both systems before the integration existed, which is common for any business that has run a CRM for more than a year, the first sync frequently creates duplicate records rather than merging them. Running a manual dedupe pass in each system, matching on a shared field such as email plus company domain, before the first sync avoids a long manual cleanup afterwards.
CRM to CRM Integrations: Dynamics 365 and Salesforce
Dynamics 365 and Salesforce are the two CRM integrations that carry the highest setup cost and the highest payoff, because they are rarely simple connect-and-sync jobs. Many businesses already use one of these platforms for finance, service or legacy sales data, then layer HubSpot on top for marketing and lightweight sales workflows. The integration has to decide, field by field, which platform is authoritative.
The Dynamics 365 connector syncs standard objects (contacts, companies, deals) along with a configurable set of custom fields, but mapping anything outside the default set is manual work. Teams that skip this step end up with HubSpot deal stages that drift out of line with what is actually happening in Dynamics 365, because custom pipeline stages built in Dynamics were never mapped to an equivalent HubSpot stage.
The Salesforce integration works similarly, with one meaningful difference: it supports bidirectional sync at the field level, with per-field conflict rules, documented in Salesforce’s own help centre. That granularity is useful, but someone has to configure conflict rules for every synced field rather than accept the defaults, or the integration falls back to a most recent edit wins rule, which produces exactly the flip-flop behaviour described above when sales and marketing teams both edit the same deal record from their respective platforms.
Marketing Automation Integrations: Mailchimp and Campaign Data
HubSpot has its own marketing automation tools, so the Mailchimp integration mostly earns its place during a migration, or in accounts that keep Mailchimp for one specific list, an events newsletter for example, while running core lead nurture from HubSpot. The integration syncs contacts and list membership one way, from Mailchimp into HubSpot, and does not push HubSpot workflow enrolments back out to Mailchimp.
The detail that catches sales operations teams out is unsubscribe and suppression sync. If a contact unsubscribes in Mailchimp, that status needs to reach HubSpot’s own suppression list quickly, or the same contact can end up receiving a HubSpot workflow email days after opting out elsewhere. UK marketing communications sit under the Privacy and Electronic Communications Regulations alongside UK GDPR, and unsubscribe requests need to be honoured without unreasonable delay, as set out by the ICO’s guidance for organisations; treat suppression sync as a compliance control rather than a data hygiene task.
Lead Capture and Enrichment: Webinars and Sales Navigator
The Zoom integration syncs webinar registrants into HubSpot as contacts and logs attendance as a timeline event on each contact record, which is what makes automated no-show follow-up possible: a workflow can branch on whether the attended property is true or false, sending a recording link to no-shows and a different sequence to attendees. The integration only captures what Zoom passes through its own registration API, so custom registration questions need to be explicitly mapped to HubSpot contact properties, or they are dropped rather than stored.
LinkedIn Sales Navigator’s integration enriches HubSpot contact and company records with LinkedIn profile data and lets reps message from within HubSpot. Enrichment data pulled this way is still personal data under UK GDPR, and the lawful basis a sales team relies on, typically legitimate interests for B2B outreach, needs to be documented, with contacts given a way to object in the same way as any other personal data processing.
Paid Media and Attribution: Facebook Ads and Google Analytics
The Facebook Ads integration syncs HubSpot lists into Facebook as custom audiences for retargeting, and pulls ad spend and campaign data back into HubSpot’s ad reporting tools, so a rep or ops lead can see cost data next to the contacts and deals those campaigns generated. The attribution reporting depends on tracking working correctly end to end (UTM parameters on ad links, HubSpot’s tracking code on the landing pages, and consistent campaign naming), and it breaks quietly whenever a campaign is built without the standard UTM structure the rest of the account uses.
The Google Analytics integration connects GA4 property data into HubSpot’s traffic and attribution reports. HubSpot’s multi-touch attribution reporting sits behind its higher marketing hub tiers, so accounts on lower tiers get traffic data but not the full attribution model. Check which tier a given account sits on before promising a sales leader an attribution report the integration cannot yet produce.
Customer Support Integrations: Zendesk
Zendesk’s integration syncs support tickets onto the HubSpot contact and company timeline, giving sales and account management visibility into open issues ahead of a renewal or upsell conversation. That visibility depends on ticket volume staying manageable inside the HubSpot view: a support-heavy account with dozens of routine tickets can bury the handful that actually indicate churn risk. Building a filtered view, or a custom property such as “has open escalation” that a workflow sets when a ticket crosses a priority threshold in Zendesk, gives reps a single flag to check rather than a scroll through ticket history.
Commerce Integrations: Shopify
The Shopify integration syncs customers, orders and abandoned checkouts into HubSpot, genuinely useful for a B2B or hybrid business using purchase history to trigger renewal or upsell workflows, and just as useful for feeding an abandoned cart recovery sequence. The volume problem shows up fast: every guest checkout can create a new HubSpot contact unless the integration is configured to match against existing records by email first, so a business with repeat buyers can end up with the same person split across several duplicate profiles, each holding a slice of their order history. Matching on email at the point of sync, rather than after the fact, avoids the bulk of this.
The Automation Layer: Zapier, Native Workflows and n8n
Zapier connects HubSpot to thousands of apps through a point-and-click interface and is priced by monthly task volume, which suits lower-volume automations well but becomes expensive once a workflow needs to process large volumes of records or run frequent polling checks. HubSpot’s own native workflows tool covers a large share of what sales operations teams need without leaving the platform: property-based triggers, branching logic, and internal notifications, without a per-task cost on top of the HubSpot subscription.
For automations that move larger data volumes, need custom logic Zapier’s step builder cannot express cleanly, or need to run on infrastructure a business controls directly, n8n is a credible alternative. It is an open-source workflow automation tool that can be self-hosted, with its own HubSpot and CRM node integrations documented at n8n’s documentation site. The tradeoff is that n8n needs someone with the technical capability to host and maintain it, or a managed instance, whereas Zapier and native HubSpot workflows need no infrastructure at all.
Document, Collaboration and Project Management Tools
Google Workspace’s integration logs Gmail messages and calendar events to the relevant contact and deal timeline automatically, which is what makes the sales activity view in HubSpot trustworthy rather than reliant on reps manually logging calls and emails. The setting that needs deliberate configuration is which inbox activity gets logged: turning on automatic logging for a shared team inbox floods every contact record on the list with routine correspondence, so most teams restrict automatic logging to individual reps’ primary mailboxes and handle shared-inbox activity through a separate rule.
Asana’s integration turns HubSpot deals into a trigger point for project work: a deal moving into a closed won stage can create an Asana project with a standard onboarding task template already attached, closing the handoff gap between sales closing a deal and delivery starting work on it. The integration syncs task status back onto the HubSpot deal record too, so an account manager can see onboarding progress without needing an Asana licence of their own, useful for keeping software licence costs down for people who only need visibility rather than edit access.
Communication Tools: Aircall
Aircall’s integration logs calls to the HubSpot contact and deal timeline, supports click-to-dial from within a contact record, and can trigger workflows based on call outcome; a disposition of no answer can enrol a contact into a callback sequence without a rep needing to do anything manually. Call recordings sync into HubSpot alongside the call log entry, useful for coaching, but recording customer calls carries its own UK GDPR and Privacy and Electronic Communications Regulations obligations: callers need to be told that calls may be recorded, and recordings need a defined retention period rather than being kept indefinitely by default. Setting that retention policy inside Aircall, rather than assuming HubSpot’s own data retention settings cover it, is the detail teams most often miss.
A Rollout Sequence That Avoids Integration Sprawl
Connecting every integration on this list in one project is how sales operations teams end up with a HubSpot instance nobody fully trusts. A more reliable rollout follows the dependency chain: the CRM sync, then lead sources, then reporting, then volume systems, then automation.
Stage 1, Core CRM Sync (Salesforce or Dynamics 365). Resolve field ownership, sync direction and dedupe keys before anything else touches the database, because every later integration writes into the same contact and deal records this stage cleans up.
Stage 2, Lead Capture and Enrichment (webinars, LinkedIn Sales Navigator). Once the core records are trustworthy, add new sources of contacts and enrichment data; doing this earlier just feeds bad data into an already messy sync.
Stage 3, Attribution and Paid Media (Facebook Ads, Google Analytics). Reporting integrations depend on clean underlying contact and deal data to mean anything, so layering them in before stages one and two are stable produces attribution numbers nobody should act on.
Stage 4, Support and Commerce (Zendesk, Shopify). These add the highest data volume of any integration on the list, so they land once field mapping and duplicate handling are already proven at a smaller scale.
Stage 5, Automation Consolidation (Zapier, native workflows, n8n). With every other system connected, review what was automated piecemeal at each stage and consolidate it: move what native workflows can handle out of Zapier to cut task costs, and move anything high volume or custom into n8n if the team has the capacity to run it.
Data Governance and Field Ownership
Every integration on this list moves personal data between systems, and each one needs a documented lawful basis and, where the receiving system is hosted outside the UK, adequate safeguards for that transfer under UK GDPR. Assign a named owner for each integration, someone who knows what data flows where, why, and who to contact if a sync starts behaving unexpectedly, rather than leaving that knowledge with whoever happened to set the integration up and has since moved to a different role.
A regular audit of active integrations catches configuration drift before it becomes a data quality problem: check whether every field mapping still matches current pipeline stages, whether any integration is still syncing data nobody uses, and whether dedupe rules still catch the record-matching patterns the business actually has. HubSpot’s own audit logs show every property change and its source, one of the fastest ways to spot an integration writing bad data before it spreads across the CRM.
Related Reading
For more on this, see the full HubSpot archive, including Stripe:HubSpot Integration with N8N: Automate SaaS Billing and CRM Data, HubSpot Data Agent: AI-Powered CRM Assistant for Sales & RevOps, and Master HubSpot Email Automation for RevOps Success.
Frequently Asked Questions
Should a HubSpot two-way sync use HubSpot or the other CRM as the system of record?
There is no universal answer. Decide field by field which platform is authoritative, configure that in the field-level sync settings, and avoid leaving fields on a default “most recent edit wins” rule, since that is what causes deal stages and other shared fields to flip flop between systems.
What is the biggest data risk when turning on the Shopify or Zendesk integration?
Volume. Both integrations can create large numbers of new contact or company records quickly, and without matching new records against existing contacts by email first, the same customer can end up split across several duplicate profiles.
Is Zapier or n8n the better choice for HubSpot automation?
It depends on volume and technical capacity. Zapier suits lower volume automations and needs no infrastructure, while n8n suits higher volume or custom automations but needs someone able to host and maintain it.
Do call recordings synced from Aircall need special data protection handling?
Yes. Recorded calls are personal data under UK GDPR and the Privacy and Electronic Communications Regulations, so callers need to be told calls may be recorded and the business needs a defined retention period for those recordings rather than keeping them indefinitely.
Leave a Reply