Skip to content
  • There are no suggestions because the search field is empty.

HubSpot integrations: choosing native, marketplace and custom connections

Understand when to use HubSpot’s built-in tools, App Marketplace integrations, Data Sync or a custom API connection.

HubSpot integrations connect external platforms and systems with HubSpot so information and actions can move between them.

A well-designed integration can reduce manual work, improve data consistency and help HubSpot operate effectively within your wider technology stack. A poorly planned connection can create duplicate records, conflicting information, security risks and unreliable reporting.

Before connecting another system, determine:

  • Whether HubSpot can meet the requirement without an integration
  • Whether a supported App Marketplace integration is available
  • Whether HubSpot Data Sync meets the data requirement
  • Whether a custom API-based integration is necessary
  • Which system will own each type of information
  • Who will monitor and maintain the connection

Use HubSpot’s built-in capabilities first

Before introducing another platform, consider whether HubSpot’s existing functionality can meet the requirement.

Depending on your HubSpot products and subscription, built-in tools can support areas including:

  • Forms and lead capture
  • Marketing emails
  • Meetings and scheduling
  • Conversations and help desk
  • Calling
  • Quotes, invoices and payments
  • Workflows and automation
  • Reporting and dashboards
  • Content and landing pages

Using native HubSpot functionality can sometimes remove the need for an external system and the integration required to support it.

This does not mean HubSpot should replace every specialist platform. The decision should reflect the required functionality, user experience, reporting, governance and long-term ownership.

HubSpot-built connections

Some commonly used services connect directly through settings provided by HubSpot.

Examples can include:

  • Gmail
  • Google Calendar
  • Microsoft Outlook
  • Microsoft 365 Calendar
  • Advertising accounts
  • Social media accounts
  • Facebook Messenger
  • WhatsApp Business

These connections are closely incorporated into the relevant HubSpot tools. Access is normally managed through the feature’s own settings and permissions.

Even when a connection is built by HubSpot, administrators should still understand:

  • What information the connection can access
  • Which users are connecting accounts
  • How activities and records are created
  • What happens if the connection is removed
  • Which external platform permissions are required

HubSpot App Marketplace integrations

The HubSpot App Marketplace contains integrations built by HubSpot and third-party providers.

Marketplace integrations can connect HubSpot with categories of software such as:

  • Accounting and finance systems
  • Ecommerce platforms
  • Communication tools
  • Video conferencing platforms
  • Advertising and social platforms
  • Customer service tools
  • Data management platforms
  • Analytics and reporting tools
  • Productivity and collaboration applications

Marketplace integrations are generally best suited to requirements that can use the app’s supported configuration and synchronisation behaviour.

Benefits of a Marketplace integration

A supported Marketplace integration can provide:

  • Faster implementation than a custom build
  • Documented functionality and setup requirements
  • An established authentication process
  • Updates maintained by the app provider
  • Standardised synchronisation and automation options

Limitations to review

An available Marketplace listing does not automatically mean that an integration will meet every requirement.

Before installation, check:

  • Which HubSpot objects are supported
  • Which external records can synchronise
  • Which properties or fields are available
  • Whether synchronisation is one-way or bidirectional
  • Whether records can be created, updated and deleted
  • How associations are handled
  • How frequently information synchronises
  • How conflicts and duplicates are managed
  • Which HubSpot subscriptions are required
  • Whether the external provider charges separately
  • Who provides support for the integration

The app developer, rather than HubSpot, may be responsible for the integration’s functionality and support.

HubSpot Data Sync

HubSpot Data Sync is available for supported applications and can provide configurable synchronisation between HubSpot and another platform.

Depending on the connected application, Data Sync can support:

  • One-way or two-way synchronisation
  • Object and field mapping
  • Filters that limit which records synchronise
  • Rules for resolving data conflicts
  • Review of synchronisation health and errors

Data Sync can be suitable where the supported connector covers the required objects and data flow without needing a completely custom integration.

Its functionality varies between applications. A Data Sync connection should therefore be assessed against the requirements for the specific external system rather than treated as a universal synchronisation tool.

Custom integrations

A custom integration is designed for requirements that cannot be met adequately through HubSpot’s built-in tools, a Marketplace integration or Data Sync.

Custom integrations can connect HubSpot with systems such as:

  • Enterprise resource planning platforms
  • Finance or billing systems
  • Data warehouses
  • Industry-specific software
  • Internal databases
  • Bespoke operational platforms

HubSpot’s APIs, webhooks and developer platform can be used to create these connections.

A custom app may use a static access token for one HubSpot account or OAuth for an appropriate private or wider distribution model. The authentication approach should reflect how many accounts will use the app and how access will be managed.

When a custom integration may be appropriate

A custom approach may be required where:

  • The external system has no suitable supported integration
  • Bespoke objects or properties must be synchronised
  • Business-specific transformation logic is required
  • The process depends on complex associations
  • Information must move in near real time
  • A business-critical workflow cannot be supported by an existing connector
  • A custom interface or action is required within HubSpot

Custom integration responsibilities

Custom integrations require ongoing ownership rather than only an initial development project.

Plan for:

  • Technical design and documentation
  • Authentication and secret management
  • Appropriate API scopes
  • API limits and version changes
  • Monitoring and alerting
  • Error handling and retries
  • Duplicate prevention
  • Test and production environments
  • Security testing
  • Deployment and rollback processes
  • Ongoing maintenance and support
  • Ownership if the original developer is unavailable

HubSpot recommends its current developer platform for new app development. Legacy private and public apps remain supported, but existing integrations should be reviewed against current developer guidance when they are changed or extended.

Common communication integrations

Email, calendar and collaboration connections are core integrations for many sales and service teams.

Email and calendars

HubSpot can connect with supported Google and Microsoft email and calendar services.

Depending on the connection and configuration, this can support:

  • Sending one-to-one emails from HubSpot
  • Email logging and tracking
  • Calendar availability
  • Meeting scheduling
  • Recording supported activities against CRM records

Individual inbox connections should not be confused with shared inbox or help desk channels. They serve different purposes and can expose different information.

Microsoft Teams

The Microsoft Teams integration can support functionality such as HubSpot notifications, meeting-related activity and other connected experiences.

Available functionality depends on how the integration is installed and configured. Administrator-level and user-level installation options may provide different capabilities.

Slack

The Slack integration can bring supported HubSpot notifications and actions into Slack.

Potential uses include:

  • Deal notifications
  • Ticket notifications
  • Workflow alerts
  • Sharing CRM records
  • Supporting internal collaboration

Zoom

The Zoom integration can help users add video-conferencing details to supported HubSpot meetings and record relevant meeting activity in the CRM.

For all communication integrations, test how users, meetings, messages and CRM records are matched before wider rollout.

Planning your data flow

Connecting two systems is not only a technical decision. Each integration needs a defined data model and operating process.

For every object or type of information, determine:

  • Which system is the source of truth
  • Which system can create the record
  • Which system can update it
  • Whether information moves one way or in both directions
  • How frequently synchronisation should occur
  • Which fields are included
  • How records are matched
  • How duplicates will be prevented
  • How deletions will be handled
  • Which system wins when values conflict
  • How errors will be identified and resolved
  • How the integration will affect reporting and automation

These rules should be documented before implementation.

Source of truth

The source of truth is the system that owns the definitive version of particular information.

An organisation may have different sources of truth for different data. For example:

  • HubSpot may own sales lifecycle information
  • An accounting platform may own invoice balances
  • An ERP may own product or fulfilment information
  • A support platform may own specialist service data

Avoid describing an entire system as the source of truth without identifying the specific objects and properties it owns.

When ownership is unclear, two-way synchronisation can create repeated overwrites and unreliable data.

Testing an integration

Test integrations with a controlled set of records before enabling wider synchronisation.

Testing should cover:

  • Creating records in each relevant system
  • Updating mapped fields
  • Matching existing records
  • Associations between records
  • Duplicate prevention
  • Empty or invalid values
  • Deletions and archived records
  • Permission failures
  • Synchronisation errors
  • Automation triggered by synchronised changes
  • Reporting results
  • Disconnection and recovery behaviour

The test should confirm both the technical data flow and the operational process for resolving problems.

Security, permissions and app governance

Connected applications may be able to read, create, update or delete HubSpot information.

Super Admins can manage approved applications, control who can install them and review required and optional data permissions for supported apps.

Apply least-privilege principles by:

  • Limiting who can approve or install applications
  • Reviewing every requested permission and API scope
  • Granting optional access only where it is required
  • Restricting custom apps to the minimum necessary scopes
  • Protecting access tokens, client secrets and other credentials
  • Removing access when an integration is no longer required
  • Rotating credentials where appropriate
  • Reviewing connected applications regularly

Approving an application is a governance decision. Its availability in the App Marketplace does not determine whether it is appropriate for your organisation or its data.

Privacy and organisational responsibility

An integration may transfer personal, confidential or commercially sensitive information to another organisation or platform.

Before approval, your organisation should consider:

  • The purpose of the data transfer
  • The information being shared
  • Data protection roles and responsibilities
  • Supplier security and due diligence
  • International data transfers
  • Retention and deletion
  • Contractual requirements
  • Data subject rights
  • Incident response
  • Regulatory requirements

HubSpot controls its platform and provides integration permissions. The external provider controls its service, while your organisation remains responsible for approving the connection and deciding whether the resulting data flow is appropriate.

Ongoing monitoring and maintenance

Integrations should be reviewed throughout their lifecycle.

Monitor:

  • Synchronisation errors
  • Failed authentication
  • Changes to permissions
  • API limits
  • Unexpected record creation
  • Duplicate records
  • Integration or API updates
  • Changes to external systems
  • Departed owners or administrators
  • Connections that are no longer used

Each business-critical integration should have a named operational owner and a clear process for responding to failures.

What can Forbidden help with?

Forbidden can help you:

  • Assess whether HubSpot can meet a requirement natively
  • Review suitable App Marketplace and Data Sync options
  • Define sources of truth and data ownership
  • Design field mappings and synchronisation rules
  • Plan and support custom HubSpot integrations
  • Configure and test supported connections
  • Review permissions and API scopes
  • Investigate errors and data-quality issues
  • Document monitoring and support requirements

Your organisation remains responsible for supplier approval, legal and security assessment, data protection decisions and its wider technology strategy.

Further information