Connecting an app to HubSpot is usually a few clicks. Choosing the right way to connect it — a marketplace app versus a custom integration — is the decision that determines whether your data stays clean and your systems stay in sync, or whether you create a quiet mess between tools. Most teams install an app, click connect, and never check what it's actually syncing. Here's the practitioner's read on connecting apps so they help instead of haunt you.
How do you connect an app from the HubSpot Marketplace?
Find the app in HubSpot's App Marketplace, click Connect or Install, and authorize it to access the data it needs. The App Marketplace lists thousands of pre-built integrations — for email, calendars, ad platforms, support tools, accounting, and more. You reach it from the Marketplace icon in your portal, search for the tool, and install it. During connection, the app asks you to log into the other tool and approve a set of permissions — what it may read and write in your HubSpot data. That permission screen is the part to actually read. It tells you exactly what the integration can touch, and authorizing blindly is how unexpected syncs and surprise data changes begin.
What should you check before installing any integration?
Check what data it syncs, in which direction, and how it matches records — before you connect it to live data. An integration isn't just a connection; it's an ongoing agreement about how two systems share information. Three questions answer most of the risk. First, which objects and properties does it sync — contacts, deals, custom fields? Second, is the sync one-way or two-way, and which system wins when they disagree? Third, how does it match records so it updates the right one instead of creating duplicates? Worked example: a team connected an email tool that synced contacts two-way and matched only loosely; within days it had created hundreds of duplicate contacts because the two systems formatted email addresses differently. Ten minutes reading the sync settings — and testing on a small group first — would have caught it.
When should you build a custom integration instead?
Build custom when no marketplace app does what you need, when you have a proprietary or in-house system, or when you need logic the off-the-shelf app can't express. Marketplace apps are the right default — they're maintained, supported, and fast to set up. Reach for a custom integration, built on HubSpot's APIs, when the tool you need isn't in the marketplace, when you're connecting an internal system or data warehouse, or when your sync rules are too specific for a pre-built app (custom matching logic, conditional field mapping, syncing a custom object a generic app doesn't understand). The trade-off is real: custom integrations are more flexible but need a developer to build and someone to maintain them as both APIs evolve. Choose custom for genuine need, not novelty.
What goes wrong when integrations aren't managed?
Unmanaged integrations create duplicates, overwrite good data with bad, and quietly desync the moment something changes upstream. The damage is rarely loud. A two-way sync silently overwrites a clean HubSpot field with a stale value from another tool. An app keeps running after you stop using the other system, syncing nothing useful but still holding access. A field mapping breaks when someone renames a property, and records stop updating with no error anyone sees. The fix is treating integrations like part of your data infrastructure, not a one-time install: document what's connected and why, review your connected apps every quarter, disconnect what you no longer use, and test any sync change on a small batch before it hits your whole database.
The IV-Lead take
Integrations are where most CRM data quality is quietly won or lost. A clean HubSpot can be polluted in a weekend by one two-way sync nobody configured carefully — and because it happens in the background, no one notices until the reports look wrong. Our rule is simple: prefer a maintained marketplace app over a custom build unless you have a real reason, read the permissions and sync direction before you connect, and test on a small group first. Every connected app is a standing agreement about your data. Treat it like one, and your stack works for you instead of against you.
Not sure what your connected apps are doing to your data? Book a 30-minute portal audit — we'll review your integrations and sync settings and tell you straight where you're at risk. For the bigger picture, see how we approach integrations and custom connections.
Frequently asked questions
Where do I find apps to connect to HubSpot?
In HubSpot's App Marketplace, reachable from the Marketplace icon in your portal. It lists thousands of pre-built integrations you can search, install, and authorize directly.
Is a two-way sync better than a one-way sync?
Not always. Two-way keeps both systems matched but risks overwriting good data with bad if you don't set which system wins. Use one-way when only one tool should be the source of truth for a given field.
Do I need a developer to connect a marketplace app?
No. Marketplace apps are designed to install and authorize without code. You only need a developer for custom integrations built on HubSpot's APIs — for in-house systems or sync logic an off-the-shelf app can't handle.
How do I stop an integration from creating duplicate records?
Check how it matches records before connecting, make sure both systems format unique identifiers (like email) the same way, and test the sync on a small group first. Most duplicate problems trace back to loose matching, not the app itself.
