Connect your tools

A CRM that lives in isolation is a CRM that dies slowly. The whole point of HubSpot is to be the central system where your customer data lives. But that only works if the tools your team uses every day are feeding data into it.

The average B2B company I work with uses between eight and twelve different tools: calendar apps, email platforms, video conferencing, billing systems, project management, ad platforms, Slack. Each one holds a piece of the customer picture. A prospect books a meeting in Calendly, discusses pricing on a Zoom call, gets a proposal in PandaDoc, signs a contract in DocuSign, and starts onboarding in Asana. If those tools aren't connected to HubSpot, your sales rep opens a contact record and sees nothing. They have to switch between six tabs to piece together what happened.

Connecting your tools isn't about making HubSpot look impressive. It's about making sure that when anyone on your team opens a record, they see the full picture: every email, every meeting, every form submission, every ad click. That's the difference between a CRM people use and a CRM people resent.

Four ways to connect tools to HubSpot

There are four integration methods. They form an escalation path: start with the simplest and only move to the next when the first one doesn't work.

1. Native integrations (App Marketplace). Hundreds of pre-built integrations: Zoom, Slack, Google Workspace, Microsoft 365, Stripe, Asana. Install in a few clicks. Always check the App Marketplace first (house icon > App Marketplace, or Settings > Integrations > Connected Apps > Visit App Marketplace).
2. iPaaS (integration platform as a service). Tools like Zapier or Make act as a bridge. You define a trigger in one app and an action in another: "When a form is submitted in Typeform, create a contact in HubSpot." HubSpot's Operations Hub works similarly for two-way data sync.
3. Google search. Type "HubSpot [tool name] integration" into Google. If a native integration exists, it appears on the first page. If not, you know to try the iPaaS route. Ten seconds, saves scrolling through the entire marketplace.
4. Custom API integration. The last resort. Requires a developer, API keys, and knowledge of HTTP requests. If you don't have a developer, a HubSpot Solutions Partner can build this for you.

The HubSpot tracking code

The tracking code is a small piece of JavaScript that unlocks three things at once:

• Website analytics in HubSpot (page views, traffic sources, time on page)
• HubSpot forms on external websites
• Live chat and chatbots on your pages

If your website is built in HubSpot, the tracking code is already there. If it's on WordPress, Webflow, Shopify, or another platform, install it manually. Copy the code from Settings > Tracking and Analytics > Tracking Code and paste it in your site's header. Not comfortable with code? Email it to your developer.

After installing, exclude your team's IP addresses (Advanced Tracking > Exclude Traffic). Without this, your marketers and developers testing pages inflate your traffic numbers and every report is wrong by whatever percentage of traffic is internal. Static IP (typical for offices): one-minute fix. Dynamic IP (home Wi-Fi): ask your provider for a static one.

Built-in integrations: ads and social

Ads. Connect Google, Facebook/Meta, and LinkedIn ad accounts (Starter subscription or above). The real value isn't clicks and impressions (you already see those in the ad platforms). It's closed-loop reporting: which ads generate contacts, which generate deals, which generate revenue. The ad platform can't make that connection on its own because it doesn't know what happens after the click.

Combine with the tracking code for a powerful loop:

1. Tracking code identifies which contacts visited your pricing page.
2. You build a list of those contacts in HubSpot.
3. You sync that list to your ad platform as a custom audience.
4. You retarget those contacts with relevant offers.

Now your CRM and ad platform talk to each other. Ads target people based on what they've done, not just demographics.

Social media. Connect Facebook, Instagram, LinkedIn, and X (Marketing Hub Professional or Content Hub). Publish posts from HubSpot, bulk-schedule content, see engagement tied to CRM data.

One habit to build: always publish from HubSpot, not natively in the social platform. When HubSpot publishes for you, it adds an invisible tracking pixel. That pixel captures click data. Post natively and you lose that tracking.

What to connect first

You don't need everything on day one. Prioritise by where your team spends the most time:

Week one:

• Email (Gmail or Outlook)
• Calendar (Google Calendar or Office 365)
• Video conferencing (Zoom or Teams)

These three cover 80% of daily sales and service activity.

Week two:

• Ad accounts (Google Ads, Meta, LinkedIn)
• Website tracking code

These enable closed-loop reporting.

Month one:

• Billing (Stripe, Chargebee)
• Project management (Asana, Monday)
• Communication (Slack)

These close the gap between sales, delivery, and finance.

As needed: custom integrations for industry-specific tools, iPaaS connections for niche platforms.

Common integration mistakes

1. Connecting before configuring. Don't connect your ad accounts before you've set up lifecycle stages and the deal pipeline. Closed-loop reporting only works if HubSpot knows what a lead, an opportunity, and a customer looks like.
2. Ignoring sync direction. Some integrations sync bidirectionally, others are one-way. Understand the direction before turning on a sync, or you risk overwriting data in one system with stale data from the other.
3. Forgetting permissions. Most integrations require specific permissions in both HubSpot and the connected platform. The most common support ticket: "my integration won't connect". The answer is almost always a missing permission.

Integrations turn HubSpot from a standalone database into a connected operating system. The more tools that feed into and pull from your CRM, the more complete the picture becomes for every person on your team.

Start with the tools your team uses daily, expand as your processes mature, and always check the App Marketplace before building something custom.