How to Connect HubSpot to Claude

AdPlug for HubSpot is an app built for the HubSpot platform. It connects the portals you choose to Claude through one connector, so Claude can:

• find and read contacts, companies, deals, leads, tickets and activity, in one portal or across all of them
• run HubSpot's reports: SQL over your CRM data, attribution, campaigns, marketing email, content, AI search (AEO) and buyer intent
• look up pipelines and stages, properties and their dropdown values, owners and portal settings
• prepare changes to records, segments, campaigns, marketing emails, properties and pipelines, which run only after you approve them
• put spend from Google Ads, LinkedIn Ads or Microsoft Ads next to HubSpot leads, deals and revenue, with AdPlug's ad connectors in the same chat

It suits consultants and agencies who work in several client portals, and anyone who wants their ad spend and their CRM in the same conversation.

You connect each HubSpot portal to AdPlug once, and most of it happens on HubSpot's own screens. Then you add one connector to Claude, and it reaches every portal you connect.

1. 1

   Get an AdPlug account on Pro, Max or Agency

   HubSpot is included from AdPlug's Pro plan: 3 portals on Pro, and 10 on Max and Agency. It isn't on the Free plan. New to AdPlug? Sign up at adplug.app/signup with Google or email, follow the short onboarding, then upgrade to Pro from the HubSpot card on the Connections page. You can connect your first portal as soon as the upgrade goes through. The pricing page has the plans side by side.

   

2. 2

   Click Connect HubSpot on the Connections page

   In AdPlug, open the Connections page and scroll down to the HubSpot card. Click Connect HubSpot. AdPlug sends you to HubSpot, where you sign in with the HubSpot login you use for the portal Claude should work in.

   

   Who can connect a portal

   You need Super Admin or the App Marketplace Access permission in that portal. Without it, HubSpot lets you request access, and a Super Admin approves AdPlug once. After that you connect as normal.

3. 3

   Pick the portal in HubSpot's account picker

   HubSpot lists every portal your HubSpot login can open, so if you work in several clients' portals you'll see all of them here. Pick the one to connect and click Choose Account. Each connect adds one portal.

   

4. 4

   Review the permissions and click Connect app

   HubSpot then lists what AdPlug can access. Four permissions are required: viewing contacts, companies and deals, and the portal's own details, such as its domain and user emails. The other 60 are optional. Most come ticked, and you can untick any of them.

   Unticking a permission only switches off what needs it, in that portal. Without the write permissions, for example, Claude can still read contacts, companies and deals but can't change them, and without the SQL permission it can't run SQL reports. Configure below lists which permission each report needs.

   A permission with a lock can't be ticked: either the portal's HubSpot plan doesn't include it, or a Super Admin has switched it off for AdPlug. When the list looks right, click Connect app.

   

5. 5

   Back in AdPlug, your portal is listed

   HubSpot sends you back to AdPlug's Connections page, with the portal on the HubSpot card: its name, Hub ID and region, the HubSpot login that connected it, and how many of the 64 permissions it granted. If some weren't granted, the row says which features aren't available yet.

   

   Under your portals, the card shows the connector to add to Claude, with copy buttons for its name and address.

   

   One connect adds one portal. For the next client, click Add another portal and pick that client's portal in HubSpot's account picker.

Rename a portal

Click Rename on the portal's row and give it the name you use for that client. Claude matches that name as well as HubSpot's own, and the card keeps HubSpot's name next to yours.

Add more portals

Click Add another portal on the HubSpot card for each client. Pro connects 3 portals, and Max and Agency connect 10. When they're all in use, remove one you no longer need, or move from Pro to Max.

Team access

On Max and Agency teams, the team owner can set a teammate to View only for HubSpot on the Team page. Claude can then report and analyse for that teammate, but the change tools are hidden and refused. Each teammate connects the portals they work in with their own HubSpot login.

Permissions and the reports they unlock

Each feature works in a portal once that portal has granted its permission. The HubSpot card keeps track of these five:

• SQL reports: crm.hubsql.execute
• Attribution reports: reporting.full.read plus a campaign revenue permission, which needs Marketing Hub Professional or Enterprise
• Changes to contacts, companies and deals: the three write permissions, crm.objects.contacts.write, crm.objects.companies.write and crm.objects.deals.write
• Campaign reports: marketing.campaigns.read
• Marketing email reports: marketing.email.read

When a feature is locked, the portal's row on the HubSpot card shows its permissions out of 64 and names what isn't available yet. Click Reconnect on that portal and tick the missing permissions in HubSpot. If they show a lock, ask the portal's Super Admin to allow them for AdPlug first. A portal that approved AdPlug earlier keeps only what it granted then, so permissions AdPlug asks for later arrive locked until a Super Admin allows them.

With a portal connected, add AdPlug's HubSpot connector to Claude. You do it once: portals you connect later show up in the same connector.

1. 6

   Add the connector to Claude

   In Claude, open Customize → Connectors (or go straight to claude.ai/customize/connectors), click + Add and choose Add custom connector. Name it AdPlug - HubSpot, paste the address below and click Continue.

   https://api.adplug.app/mcp/hubspot

   Copy

   

   Claude then shows the sign-in settings it found for AdPlug. Leave them as they are and click Add. Your AdPlug dashboard shows the same name and address with copy buttons on its Claude card, once you pick HubSpot only in the scope picker.

   

   Already use AdPlug for your ads?

   Keep that connector and add this one next to it. The all-platforms address carries the ad platforms only, so HubSpot always gets its own connector.

2. 7

   Approve AdPlug's sign-in

   Claude opens AdPlug's sign-in, either straight away or when you click Connect on the new connector. Use the same email as your AdPlug account and click Approve. The connector turns Connected, and its nine tools are ready in any new chat.

   

3. 8

   Ask your first question

   Start a new chat, switch the connector on in the + menu of the message box, and ask:

   “List my HubSpot portals.”

   Claude calls the hubspot_list_accounts tool and lists every portal you connected, with its Hub ID, region and status. If your portals are there, the connection works end to end.

   

First prompts to try

Swap [portal] for a portal's name. Claude asks when it needs more, like the period or the pipeline. More copy-paste prompts live in the prompt playbooks.

How Claude picks the portal

Claude starts by listing your connected portals, then names the portal in every answer. Say which portal you mean in the prompt, by HubSpot's name or the name you gave it. Ask about all of them at once and it searches every portal, keeping each portal's currency apart. A change always goes to one portal.

Changes are previewed first

Ask for a change and Claude first shows a preview: the portal, each record, its current values and the new ones. Nothing changes in HubSpot until you approve it. HubSpot takes at most 10 records per change, so a bigger job comes back as several previews. Each change that runs counts as one AI edit on your AdPlug plan.

Changes cover contacts, companies, deals, leads, notes, tasks, segments (lists), campaigns, marketing emails including A/B tests, custom properties, pipelines, and AEO prompts and recommendations. Records are never deleted or merged: HubSpot's MCP server has no delete or merge for records. A segment can be deleted, after you approve it like any other change. Forms and form submissions, workflow edits, files and HubSpot Ads data aren't reachable at all.

HubSpot and your ads in one chat

The HubSpot connector carries HubSpot only. To put ad spend next to HubSpot leads, deals and revenue, add an AdPlug ad connector next to it in Claude: Google Ads, LinkedIn Ads or Microsoft Ads, or the all-platforms ad address https://api.adplug.app/mcp. Claude's Free plan allows one custom connector, so HubSpot and ads together in Claude need a paid Claude plan.

Disconnect one portal at a time, in AdPlug:

1. Open the Connections page and scroll to the HubSpot card.
2. Click Remove on the portal's row.
3. Click Confirm remove.

AdPlug deletes that portal's stored HubSpot login and asks HubSpot to revoke it, so Claude can't reach the portal any more. Your other portals keep working. Nothing in HubSpot is deleted or changed: the portal's records stay exactly as they are, including any change you approved earlier.

To stop using HubSpot in Claude altogether, remove the connector there too: open Customize → Connectors and click Remove, or the three dots, next to AdPlug - HubSpot.

You can also remove AdPlug from the HubSpot side, on the portal's Connected Apps page. HubSpot documents it in its guide to uninstalling an app:

1. In your HubSpot account, click the settings icon in the top navigation bar.
2. In the left sidebar menu, go to Integrations, then Connected Apps.
3. Click Actions on AdPlug, then Uninstall.
4. In the dialog box, type uninstall and click Uninstall.

That ends AdPlug's access to the portal, and Claude can't reach it any more. The next time AdPlug tries, HubSpot refuses and the portal's row on the HubSpot card asks you to reconnect it. Click Remove there to delete the stored login as well. Records in HubSpot stay as they are.

• Records pass straight through. AdPlug keeps no copy of your CRM records. Records and reports go straight to Claude.
• What AdPlug stores for each portal. Its Hub ID, its name and the name you gave it, its domain and region, the HubSpot user ID and email that connected it, the permissions granted, and encrypted tokens.
• Change previews. The change you asked for and, once it runs, HubSpot's answer, kept until the daily clean-up after about a day. The current values a preview shows come straight from HubSpot and aren't stored.
• Usage log. Each tool's name and the portal's Hub ID, never record data.
• Disconnecting and uninstalling. Removing a portal deletes its stored login, drops its previews that never ran and asks HubSpot to revoke the login. Deleting your AdPlug account revokes every portal's login and deletes their rows. Neither touches the records in HubSpot.

The privacy policy has the full detail.

Click any item to expand the answer.

Using ChatGPT instead? The HubSpot to ChatGPT guide covers Developer mode and the same install. The same AdPlug account connects other platforms and assistants too.

Email support@adplug.app with setup questions or bug reports. Most replies come back the same business day.