HubSpot Intercom Integration: Connect Them for Your AI Agent (2026)

This guide covers both: the native HubSpot app for Intercom (and where it stops), and how to give your AI agent live HubSpot lookups and actions right inside a conversation using a Custom Tool.

Framing first. Macha runs on top of the Intercom you already use — it's an AI-agent layer, not an Intercom or HubSpot replacement. Fin and your Inbox keep working as they do; Macha reads the conversation, reasons, and reaches into HubSpot to answer or act.

Want the broader picture on connecting any app to Intercom? See our pillar on building custom Intercom integrations — this piece focuses on giving your AI agent live HubSpot access.

The native option — and where it stops

Intercom does offer a native HubSpot app in the App Store. It syncs conversations, contacts, companies, and tickets between the two platforms and can surface HubSpot data on a lead in the Inbox, so a human agent can see who they're talking to. If all you need is passive context on the screen and two-way record sync, that may be enough.

Where it stops:

• It's mostly display/sync, not action. It shows fields and logs conversations; it doesn't let an AI agent decide to look something up mid-conversation, pass the right parameters, and reason over the result.
• It's fixed. You get the objects and fields the app maps — not the specific query or write your workflow needs (e.g. "is this contact on an active deal?" or "update the lifecycle stage from this ticket").
• It's sync, not live. Synced data can lag; an AI agent answering a billing or eligibility question wants the current record, not a copy from the last sync.

For a lot of teams, the sidebar sync is fine. For anyone who wants their AI agent to actually use HubSpot, there's a lighter, more flexible path.

What you actually want: the agent using HubSpot live

The high-value version of this integration isn't a synced field — it's the agent doing the work. A customer messages Intercom; the agent recognizes them, looks up their live HubSpot contact by email, and answers "yes, you're on the Pro plan" or "I can see your renewal is next month" — grounded in HubSpot, not a stale synced copy. That's what a Custom Tool enables.

How to connect them with a Custom Tool

A Custom Tool is a single action you define once and point at HubSpot's CRM API. No marketplace app, no code.

1. Point it at the HubSpot API. HubSpot exposes a REST CRM API (with OAuth 2.0 or a private-app token); you give Macha the endpoint and credentials. The built-in Sidekick can scaffold the request from a plain-English description if you'd rather not fill in the form.

2. Define the action. Give it a label and a description the AI uses to decide when to call it — e.g. "Get the HubSpot contact, lifecycle stage, and open deal for a customer by email" — set the method and URL (a query against the HubSpot CRM API, with a {{email}} placeholder), and choose Read or Write. A lookup is a Read; updating a property or logging a note is a Write, which requires confirmation before it runs.

3. The agent uses it live. Once the tool exists, the agent calls it mid-conversation, passes the customer's email, and reasons over the HubSpot record it gets back — answering the question or taking the next step.

Read vs Write, and staying safe

Because a Custom Tool can reach into HubSpot, the guardrails matter: Read tools (lookups) are free to call; Write tools (update a property, log an activity, change lifecycle stage) require confirmation. Each tool is scoped to one action, permissioned per agent, and every call is audited. HubSpot's OAuth or private-app token handles credentials, so secrets never live in the conversation.

Teams usually build a few HubSpot tools and group them — a lookup, an "update contact property," a "log conversation to timeline" — alongside tools for their other systems.

Native app vs Custom Tool — which to use

• Use the native HubSpot app if you just want contacts, companies, and conversations synced between the two platforms and visible in the Inbox for human agents.
• Use a Custom Tool when you want your AI agent to look up live HubSpot data or take an action from the conversation, you need a specific query or write the native app doesn't expose, or you'd rather work from the live record than a synced copy. The two can coexist.

Beyond the lookup

Once the agent can reach HubSpot, the same pattern covers more: check a contact's lifecycle stage or deal before answering, read the account owner to route a VIP, log the conversation to the contact timeline, or update a property from the ticket. And because Custom Tools aren't HubSpot-specific, the same approach connects your billing system, data warehouse, or internal API — see the Custom Tools integration directory for 200+ tools, or the full pillar on building custom Intercom integrations.

The bottom line

Intercom's native HubSpot app puts data on the screen and keeps records in sync. A Custom Tool puts HubSpot in your AI agent's hands — live lookups and actions, decided in context, on any plan, no code. You describe the action, point it at the HubSpot CRM API, and your Intercom agents can use it inside a conversation with Read/Write guardrails and a full audit trail.

Ready to try it? See how Custom Tools work, browse the integration directory, or start a free trial and wire up your first HubSpot tool today.

Frequently asked questions

Does Intercom have a native HubSpot integration? Yes — the HubSpot app in the Intercom App Store syncs conversations, contacts, companies, and tickets between the two and surfaces HubSpot data in the Inbox. It's display/sync-focused; a Custom Tool adds live, agent-driven lookups and actions on any plan.

Do I need an engineer to connect HubSpot to Intercom this way? No. You describe the action in plain English and Macha's Sidekick scaffolds the HubSpot request, auth, and parameters. Technical teams can go deeper with full control over the CRM API query, headers, and response mapping.

Can the agent update HubSpot, or only read it? Both. Reads (lookups) run freely; writes — updating a property, logging a note — require a confirmation step, and you control which agents can use them.

Is it secure? Yes. The tool is scoped to a single action, permissioned per agent, authenticated via HubSpot OAuth or a private-app token, and every call is audited.