Shopify
Stripe
Slack
Notion
Google Workspace
Confluence
How Do You Connect HubSpot to Intercom for an AI Agent? (2026)
Intercom's own HubSpot app sends leads and conversation transcripts one way into HubSpot and shows a fixed six-field card in the Inbox. An AI agent that needs live contacts, deals and tickets mid-conversation needs a HubSpot connector or a Custom Tool instead.
Key takeaways
- Intercom's native HubSpot app sends data one way, from Intercom to HubSpot, creating contacts from leads and logging conversations to the HubSpot timeline.
- The HubSpot card in the Intercom Inbox shows six fixed fields: name, email, company name, lifecycle stage, lead status and owner, with no custom properties.
- Two-way record sync between Intercom and HubSpot needs the separate Data Sync by HubSpot app, according to Intercom's help center.
- Macha's HubSpot connector lets an AI agent search contacts and deals, update properties, move deal stages and add notes from inside an Intercom conversation, and Custom Tools cover any HubSpot call it lacks, with Write tools requiring confirmation first.
- On the trial and every Macha plan, the Macha team builds and tests the HubSpot tools and the agent for you, at about $0.40 a ticket including setup and a dedicated success manager who handles your changes.
You can connect HubSpot to Intercom in three ways: Intercom's own HubSpot app, which sends leads and conversation transcripts one way from Intercom to HubSpot; HubSpot's Data Sync app for two-way record sync; or an AI agent layer such as Macha, which reads and updates live HubSpot contacts, deals and tickets from inside an Intercom conversation. The first two keep records in step for human agents. The third lets an AI agent look something up or take an action while it answers.
| Option | Direction | What it does | Best for |
|---|---|---|---|
| Intercom's HubSpot app | Intercom to HubSpot only | Creates HubSpot contacts from leads, logs conversations to the contact timeline, shows a fixed six-field card in the Inbox | Human agents who want CRM context on screen |
| Data Sync by HubSpot | Both ways | Syncs records between the two systems on a schedule | Keeping fields aligned in both tools |
| Macha HubSpot connector | Live read and write | An agent searches contacts and deals, updates properties, moves pipeline stages and adds notes during the conversation | AI agents answering or acting on live CRM data |
| Macha Custom Tool | Live, any endpoint | One action you define against the HubSpot API | A query or write the connector does not cover |
Framing first. Macha runs on top of the Intercom you already use. It is 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.
What does Intercom's native HubSpot app do, and where does it stop?
Intercom offers a native HubSpot app in the App Store. According to Intercom's help article (checked 24 September 2026), it creates new Intercom leads as HubSpot contacts with the lifecycle stage set to Lead, syncs their name, email and phone number, and logs conversation transcripts as activities on the contact's HubSpot timeline. End-user replies sync in real time; teammate replies sync once the conversation closes. The app is available on Intercom's Essential, Advanced and Expert plans.
Where it stops:
- It only sends data one way. Intercom's own article says the app "cannot sync data from HubSpot to Intercom." For two-way sync, Intercom points you to the separate Data Sync by HubSpot app.
- The Inbox card is fixed. It shows six fields: name, email, company name, lifecycle stage, lead status and owner. Custom properties, deals and other HubSpot-only fields cannot be added.
- It is display and logging, not action. Nothing in the app lets an AI agent decide to look something up mid-conversation, pass the right parameters, and reason over the result (for example, "is this contact on an active deal?").
- Synced is not live. A synced copy can lag. An agent answering a billing or eligibility question wants the current record.
For many teams, the sidebar card and timeline logging are enough. For anyone who wants their AI agent to use HubSpot, there is a more direct path.
What does an AI agent need from HubSpot?
The high-value version of this integration is 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 rather than a stale copy. Macha offers two ways to give an agent that access.
How do you connect HubSpot to an Intercom AI agent?
The native connectors. Macha has a live Intercom connector (read conversations, reply, add internal notes, assign, tag and close) and a live HubSpot connector, both connected by OAuth. The HubSpot connector's tools cover Search Contacts, Get Contact, Update Contact, Search Deals, Get Deal, Update Deal Stage, Search Tickets, Get Ticket, Update Ticket, Add Note and List Pipelines. Connect both and the agent can move between an Intercom conversation and the customer's CRM record with no API work.
A Custom Tool, for anything the connector does not cover. A Custom Tool is a single action you define once and point at HubSpot's API. No marketplace app, no code.
1. Point it at the HubSpot API. HubSpot's REST CRM API accepts OAuth 2.0 or a private-app access token (HubSpot now lists private apps under its legacy apps, which it still supports). 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, such as "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 an {{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, then answers the question or takes the next step.
How do you keep HubSpot writes safe?
Because the agent can reach into HubSpot, the guardrails matter. Custom Tools set as Read (lookups) run freely; Write tools (update a property, log an activity, change lifecycle stage) require confirmation. Each tool is scoped to one action and permissioned per agent, and every call is logged. 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.
Should you use the native app, the connector, or a Custom Tool?
- Use Intercom's HubSpot app if you want Intercom leads created in HubSpot, conversations logged to the contact timeline, and a six-field card in the Inbox for human agents. Add Data Sync by HubSpot if you need fields flowing back into Intercom.
- Use Macha's HubSpot connector when you want your AI agent to read live contacts, deals and tickets, update properties, or add notes from the conversation. Macha is the done-for-you option: the Macha team builds and tests the HubSpot tools and the agent on your Intercom, then runs it in safe mode, with drafts as internal notes, until the drafts are right. That's included on the trial and every plan at about $0.40 a ticket, which covers setup and a dedicated success manager who handles your changes.
- Add a Custom Tool when you need a specific query or write the connector does not expose. All of these can coexist.
What else can the agent do once it reaches 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.
Ready to try it? See how Custom Tools work, browse the integration directory, or start a free trial ($50 of free usage, no credit card) and connect HubSpot to your first agent.
Frequently asked questions
Does Intercom have a native HubSpot integration? Yes. The HubSpot app in the Intercom App Store creates HubSpot contacts from Intercom leads, logs conversations to the HubSpot timeline, and shows a six-field HubSpot card in the Inbox. It sends data one way, from Intercom to HubSpot; two-way sync needs the Data Sync by HubSpot app.
Do I need an engineer to connect HubSpot to Intercom this way? No. On the trial and every plan, the Macha team sets up the connectors and builds any Custom Tools for you. Macha's HubSpot and Intercom connectors connect by OAuth. To build a Custom Tool yourself, 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. The HubSpot connector can update contacts and tickets, move deal stages and add notes. Custom Tools set as Read run freely; Write tools require a confirmation step, and you control which agents can use them.
Is it secure? Each tool is scoped to a single action, permissioned per agent, authenticated via HubSpot OAuth or a private-app token, and every call is logged.
Which Intercom plans can use the native HubSpot app? Intercom lists the app as available on its Essential, Advanced and Expert plans. Some features may need a paid HubSpot account.
