HubSpot to ChatGPT in 2026: 4 free ways to connect

Connect HubSpot to ChatGPT with MCP

For this tutorial we’re going with the MCP method. Here’s a quick explainer of what MCP is and why it’s the best path for HubSpot.

MCP (Model Context Protocol) is the open standard that lets AI tools like Claude, ChatGPT, Codex and others access and use external APIs — the things that make tools like HubSpot work under the hood. Instead of building a custom integration for every AI tool you use, you install one MCP and every compatible AI gets access to the same data.

The full setup takes under 5 minutes and breaks into three moves: connect HubSpot to Porter, point ChatGPT at the Porter MCP, and ask your first question.

1. Connect your HubSpot data to Porter

Porter sits between HubSpot’s CRM API and ChatGPT. It handles OAuth, rate limiting, pagination and all the plumbing so ChatGPT only ever sees clean, structured data.

Sign up for Porter. Create a free account at portermetrics.com. The free tier is enough to run this full workflow end-to-end.

Connect your HubSpot. In Porter, click Create → pick ChatGPT as the destination → select HubSpot as the source → sign in with HubSpot to grant access to your accounts.

Select your accounts. Choose the HubSpot accounts you want ChatGPT to query. When you select multiple accounts under a single connection, Porter automatically blends their data together so you can query them as one.

Optional: enable automatic BigQuery storage if you’re connecting multiple accounts with large data volumes. This keeps ChatGPT’s responses fast even at scale.

2. Connect the MCP to ChatGPT

Porter’s MCP URL is what you paste into ChatGPT. Once added, ChatGPT can query HubSpot data on demand in any conversation.

Go to chatgpt.com and click the + icon in the chat input to open the tools menu.

In the menu that opens, hover over Connectors and click Manage connectors.

In the Connectors panel, click the + button at the top of the list to start adding a new connector.

Pick Add custom connector from the dropdown that appears.

A dialog opens with the name and URL fields. Type Porter in the first field to name the connector.

In the second field, paste https://mcp.portermetrics.com/mcp. Leave the advanced settings alone.

Click Add at the bottom right of the dialog. ChatGPT opens a sign-in window — use the same Google account linked to your Porter workspace and approve access.

Once the authorization finishes, you’ll see Porter’s tools appear in the connectors panel. You’re ready to start asking questions.

For a fuller walkthrough with screenshots at every step, see the Porter MCP tutorial.

3. Start building questions and dashboards

With Porter connected, open a new ChatGPT chat and ask anything about your HubSpot in plain English. ChatGPT calls Porter behind the scenes, pulls live data from HubSpot, and answers with tables, charts, or summaries.

Try one of these to verify the setup is working:

For a full catalogue of copy-paste prompts organized by use case (performance, pipeline health, client reporting, agency, B2B, e-commerce, cross-channel), jump to the prompts section below.

Alternative ways to connect HubSpot to ChatGPT

Porter MCP is the path we just walked through and the one we recommend for most marketers. It is not the only way to get HubSpot data in front of ChatGPT, though. The most common alternatives are HubSpot’s official HubSpot MCP, a live Google Sheets bridge or CSV upload, and BigQuery for scale. Each has trade-offs, so pick the one that fits how your team already works.

• verified HubSpot’s official MCP — HubSpot operates an official first-party Remote MCP server (endpoint https://mcp.hubspot.com) for CRM data access, plus a separate local Developer MCP server for CLI-based app/CMS development. HubSpot data only: no blends, dashboards, or multi-account setup.
• 📊 Google Sheets — Live Sheet or one-off CSV upload. Auditable, familiar, faster for big exports — but aggregation happens in the Sheet, not the API.
• 🗄️ Google BigQuery — For large accounts or agencies running multi-account analysis. BigQuery aggregates; ChatGPT only queries pre-built summaries.

Via the Porter Metrics app in the ChatGPT marketplace

If you’d rather not paste a connector URL, install Porter straight from ChatGPT’s app gallery — it’s the same Porter connection behind the scenes, published as an approved ChatGPT app:

1. Open the Porter Metrics app page in ChatGPT (or search “Porter Metrics” in the apps gallery).
2. Click Connect and sign in with the same account you use in Porter.
3. Authorize it and ask your first HubSpot question — same live data as the MCP.

The trade-off to know: the marketplace app only updates after each ChatGPT review cycle, while the MCP updates the moment Porter ships. If you want every new tool and data source immediately, use the MCP; if you want the one-click install and don’t mind waiting for new features, the marketplace app is the shortest path — including write actions through your connected Porter account.

Via HubSpot’s official HubSpot MCP

HubSpot operates an official first-party Remote MCP server at https://mcp.hubspot.com for CRM data access, plus a separate local Developer MCP server for CLI-based app/CMS development. Both are documented on developers.hubspot.com. The Remote MCP server is generally available and supports 12 official tools covering read/write access to CRM records (contacts, companies, deals, tickets, line items, products, quotes, subscriptions, segments, carts, invoices, orders), activities (calls, emails, meetings, notes, tasks), and content/marketing objects (blog posts, landing pages, site pages, campaigns, marketing events). Authentication is OAuth 2.0 with PKCE — users must create an MCP auth app in their HubSpot account, obtain a Client ID and Redirect URL, then authenticate through the standard HubSpot OAuth flow. OAuth 2.1 support is planned for later in 2025.

The nuances:

• Sensitive Data lockout: If a HubSpot account has Sensitive Data turned on, activity objects (calls, emails, meetings, notes, tasks) are blocked from MCP access entirely. This is an MCP-specific restriction that does not apply to the standard HubSpot API.
• No vector search: The CRM search tools are based on the standard CRM search API and do not include vector/semantic search capabilities.
• Scope re-installation required: When scopes are updated (e.g., new tools added), users must re-install the MCP server to pick up the new permissions.
• Permission-gated: All actions respect existing HubSpot user permissions; an account admin must connect the MCP server first, and individual users are limited to their own permission levels.
• Single-account, single-source: The official MCP connects to one HubSpot account only. No cross-account or multi-source data blending is supported.

Porter MCP covers this out of the box: multi-source blending with 20+ marketing, sales, and analytics sources in one interface; multi-account aggregation across clients or business units; pre-built dashboards and calculated metrics; centralized auth management without per-user re-installation; and a standardized data view across permission levels for reporting purposes — on top of the same HubSpot data.

When this makes sense: Teams that only need HubSpot data in ChatGPT, already have Super Admin access for OAuth setup, and don’t need cross-source blends or multi-account views.

Via Google Sheets (live Sheet or manual CSV)

If your team already lives in Google Sheets — or you want a paper trail before ChatGPT touches anything — feed HubSpot into a Sheet, then let ChatGPT read the Sheet. You can automate the HubSpot → Sheets pipeline with Porter so it refreshes daily, or do one-off CSV exports from HubSpot’s native UI for static analysis.

The trade-off to know. With the MCP path, ChatGPT calls HubSpot’s API directly and HubSpot does the filtering and aggregation on its side — clean and deterministic. With the Sheets path, ChatGPT aggregates inside the Sheet itself, which can introduce hallucinations on totals, averages, and joins when you have thousands of rows. The upside is speed: for very large date ranges or historical analysis, a pre-built Sheet is dramatically faster than live API calls.

When this makes sense: Finance teams that want to review numbers before ChatGPT acts on them, agencies already delivering client reports in Sheets, historical analysis across years of data, or any case where you care more about speed than real-time freshness.

Read the full Sheets tutorial →

Via Google BigQuery (for scale)

This is the path most people overlook — and it’s the one that saves you when your HubSpot account gets serious. A single large user or an agency managing 10+ accounts will hit API rate limits and latency problems querying ChatGPT directly. ChatGPT will literally tell you it’s taking too long or timing out on big pulls.

BigQuery fixes that. You load HubSpot data into BigQuery tables on a schedule, then connect BigQuery to ChatGPT — either through a BigQuery MCP or via Codex with SQL queries. Instead of asking ChatGPT to pull raw HubSpot data, you let BigQuery aggregate into small, optimized tables, and ChatGPT only queries the summarized output. Scale problem solved.

When this makes sense: enterprise accounts with thousands of contacts/deals, agencies running multi-account analysis across 10+ clients, or any team already using BigQuery as a data warehouse. Porter loads HubSpot (and 25+ other sources) directly into BigQuery so you don’t have to build your own ETL.

Read the full BigQuery tutorial →

Connecting HubSpot to Codex

Most marketers lump ChatGPT and Codex together and miss the biggest advantage of the entire MCP ecosystem. They’re not the same tool — and the difference matters enormously once you start working with HubSpot data seriously.

ChatGPT is a chat interface. You ask a question, ChatGPT pulls live data through the MCP, answers, maybe builds a quick dashboard inside the conversation. Great for one-off analysis. The problem: everything is ephemeral. Want to refresh the dashboard tomorrow? You regenerate it from scratch. Want the same report every Monday? You re-ask the question every Monday.

Codex is ChatGPT running inside your computer’s terminal. Because it has access to your filesystem, runtime, and other developer tools, it doesn’t just answer questions — it can build real software. Persistent scripts, scheduled routines, HTML apps, internal dashboards, integrations that run 24/7 without your input. Once it’s connected to Porter’s MCP for HubSpot, a whole category of work becomes possible.

What Codex unlocks that ChatGPT alone cannot

This is where the MCP ecosystem pays off most. Because Codex can combine Porter’s MCP with other MCPs — Firecrawl for web scraping, Airtable for structured data, Notion for wikis, Vercel for deployment, Slack and Gmail for delivery — you’re no longer querying data. You’re building tools.

Bottom line: ChatGPT is for quick questions and ad-hoc dashboards. Codex is for building apps, live dashboards, alerts, and actual tools — anything you want to run on its own without re-asking. Same Porter MCP URL works in both, so you don’t pick once and lock in.

Use cases: what you can actually do once HubSpot is connected to ChatGPT

Getting the connection right is half the battle. The real value shows up in what you do next. Here are the use cases Porter users build around their HubSpot data — from simple Q&A to full client-facing workflows.

1. Chat and ask questions directly

The simplest use case — and still the one 80% of marketers start with. Open ChatGPT, ask a question, get an answer grounded in live data.

It’s the fastest way to replace a daily HubSpot dashboard check-in. But chat is table stakes — the interesting use cases come next.

2. Blend HubSpot with your revenue data (Meta Ads, Google Ads, LinkedIn Ads)

This is where a 360° view gets real. When you connect HubSpot and your revenue source (Meta Ads for lead generation, Google Ads for attribution, LinkedIn Ads for B2B prospecting), ChatGPT can map deals, contacts, and campaigns to actual closed-won deals — using UTMs, campaign names, and contact IDs — and give you attribution that no platform-side number can.

ChatGPT handles the UTM mapping and joins. You get a client-ready attribution report that no single platform can generate on its own.

3. Automated alerts and notifications on Slack or Gmail

With Codex you can turn HubSpot monitoring into a routine that runs on its own. Hook Porter’s MCP (for the data) together with a Slack or Gmail MCP (for delivery), then write a Codex scheduled task that pulls performance every morning and pings you only when something actually needs attention.

No dashboards, no daily check-ins. The report comes to you — and only when it matters.

4. Client-ready presentations with live data (Gamma, HTML, PDF)

A common agency pain: you send clients a Data Studio link — and you spend an hour explaining a broken dashboard. With ChatGPT you can build the presentation itself — as a Gamma deck, a custom HTML page, or a PDF — populated with live numbers each time.

The presentation becomes a delivery artifact you send to the client, not a dashboard that depends on another tool staying up. No broken iframe, no login prompts, just the content.

HubSpot fields and metrics you can query with ChatGPT

Before you start writing prompts, it helps to know what data is actually available. Porter MCP gives ChatGPT access to 510 HubSpot fields and metrics across every reporting level, plus breakdowns by contact lifecycle stage, deal pipeline, company industry, and owner. And the same MCP URL also unlocks 25+ other sources — so ChatGPT can blend HubSpot with Google Ads, GA4, Shopify, HubSpot and more in a single prompt.

Prompts you can copy-paste today

Organized by job: Performance checks, Pipeline health, Client reporting, Prompts for agencies managing multiple clients, Prompts for e-commerce teams, Cross-channel.

1. Performance checks

When you need a quick pulse on marketing email health, contact engagement, or funnel velocity.

2. Pipeline health

When deals are stalling, forecasts are off, or you need to prioritize rep outreach.

3. Client reporting

When you need to package HubSpot insights into a client-ready narrative.

4. Prompts for agencies managing multiple clients

When you’re running HubSpot across multiple client accounts and need cross-account visibility.

5. Prompts for e-commerce teams

When you’re blending HubSpot CRM data with Shopify or other e-commerce sources.

6. Cross-channel

When you need attribution and blending across HubSpot and your ad, analytics, or e-commerce stack — including B2B pipeline questions against your CRM.

Limits, safety, and best practices for HubSpot via ChatGPT

This is the most common “horror story” pattern for HubSpot API users: not bans, but silent partial failures at scale. Because HubSpot returns HTTP 429 (throttle) errors rather than halting the entire pipeline, ETL jobs and automation scripts often continue with incomplete data. A marketer running a bulk contact enrichment via Claude MCP who doesn’t check response codes can end up with a CRM where 40% of records have updated lifecycle stages and 60% don’t — making segmentation and reporting unreliable. The cost isn’t account suspension; it’s decisions made on dirty data.

HubSpot’s rate-limit enforcement is quota-based and rolling-window, not tool-based. HubSpot doesn’t ban or suspend accounts because you used Claude, an MCP server, or a third-party integration. It throttles requests because of how the API was used: exceeding burst limits (requests per 10-second window), exceeding daily quotas (rolling 24-hour totals), or hitting per-endpoint caps like the Search API’s 4 requests/second limit. Read-only usage within your tier’s quota is safe. Bursty parallel writes, unbatched bulk operations, and unscoped API keys are not. When a limit is hit, HubSpot returns HTTP 429 with a Retry-After header; requests resume automatically once the rolling window refills. There is no permanent “strike” system or account-level penalty.

The two patterns that lead to inaccurate HubSpot reports

After reviewing official docs and community threads, two patterns come up again and again.

1. Parallel API bursts and unbatched bulk writes. Sending concurrent requests or large unbatched payloads violates HubSpot’s token-bucket burst limits (100 requests per 10 seconds on Free/Starter, 190 on Professional, 200 on Enterprise). When exceeded, HubSpot returns HTTP 429 and blocks further requests until the bucket refills. If your Claude MCP tool or automation script doesn’t handle 429s with exponential backoff, the pipeline continues with partial data — creating an inconsistent CRM. Official docs: HubSpot API Usage Limits via Reform.app rate limit guide. What to do instead: batch writes to 100 records per request max and implement exponential backoff starting at 1 second, doubling up to 16 seconds.

2. Exposing API keys or access tokens in shared environments. A 2024 security audit found that 1.6 million HubSpot users’ data was compromised through exposed API keys in public repositories, browser extensions, and shared Claude Desktop configurations. Unlike OAuth-based Native Connectors (which use scoped, rotating tokens), MCP Server setups and Private Apps rely on static access tokens that can be leaked in JSON config files, GitHub gists, or team-shared Claude Desktop settings. Source: BeVigil security research. What to do instead: use the Native OAuth Connector when possible; if using MCP Server, store tokens in environment variables or a secrets manager, never in committed JSON files.

3. Over-privileged scopes and ignoring validation bypasses. The HubSpot Native Connector for Claude requests broad read/write scopes at setup. If configured before November 20, 2025, it may lack write permissions and require a full disconnect/reconnect to enable record creation — a disruption that breaks automated workflows. More critically, custom validation rules configured in HubSpot are NOT applied when creating or updating records via the API or connector, meaning Claude can write data that violates your CRM’s own data-quality rules (e.g., invalid email formats, missing required fields, duplicate company names). Source: HubSpot Knowledge Base — Best Practices and developers.hubspot.com/mcp. What to do instead: audit scopes after setup, reconnect if write permissions are missing, and run validation reports in HubSpot UI after any bulk Claude-initiated update.

Both behaviors trigger quota throttling and data quality degradation. If you want to use ChatGPT for HubSpot safely, use Porter MCP which handles batching, backoff, and token rotation automatically.

The 5-rule best-practice protocol

Based on HubSpot’s documented rate limits and quotas and the behaviors that have actually caused partial syncs and data quality issues — not guesswork:

• Stay under your tier’s burst limit. Free and Starter HubSpot accounts are capped at 100 API requests per 10-second window; Professional at 190; Enterprise at 200. Exceeding this triggers HTTP 429 and pauses your pipeline. Consequence if ignored: mid-sync throttling leaves your CRM in a partially updated state. Porter enforcement: Porter MCP batches all HubSpot requests and enforces per-10-second rate pacing automatically.

• Batch bulk operations to 100 records per request. HubSpot’s bulk endpoints accept up to 100 records per batch. The Native Connector for Claude has a stricter limit of 10 records maximum per create/update operation. Sending larger payloads results in rejected records or split transactions. Source: HubSpot Knowledge Base (Native Connector table) and HubSpot API docs. Consequence if ignored: records silently fail or require manual re-entry. Porter enforcement: Porter splits bulk requests into 100-record chunks and surfaces failed records in the response.

• Implement exponential backoff on 429 errors. When HubSpot throttles, it returns HTTP 429 with a Retry-After header. Best practice is to wait 1 second on the first 429, then double the wait time (2s, 4s, 8s, 16s) up to a maximum of 16 seconds before retrying. Source: HubSpot Developer Docs via Consultevo rate limit guide. Consequence if ignored: retrying immediately extends the throttle window and can compound partial-failure states. Porter enforcement: Porter MCP includes automatic exponential backoff with jitter on all 429 responses.

• Monitor your daily quota, not just burst limits. Free/Starter accounts have a 250,000-request rolling 24-hour quota; Professional 650,000; Enterprise 1,000,000; Public apps 500,000. A large historical sync or backfill can burn the entire daily quota by noon, leaving evening automations stalled. Source: Reform.app rate limit guide and Consultevo guide. Consequence if ignored: scheduled workflows (email sends, lead scoring, reporting refreshes) fail for hours. Porter enforcement: Porter tracks per-account daily quota consumption and warns when 80% is reached.

• Never commit API tokens to shared files or repositories. HubSpot Private App tokens and legacy API keys are static credentials. A 2024 audit found 1.6 million users’ data exposed through leaked keys in public code repositories. If using the MCP Server path with Claude Desktop, store the accessToken in environment variables or a secrets manager — never in claude_desktop_config.json that gets shared via Slack, Notion, or GitHub. Source: BeVigil security research. Consequence if ignored: unauthorized access to your entire CRM, including contacts, deals, revenue data, and engagement history. Porter enforcement: Porter’s managed MCP uses OAuth token rotation and never exposes static credentials to end users.

What Porter MCP does differently: it enforces these limits and safeguards at the platform level. Porter’s HubSpot MCP batches requests into HubSpot-compliant chunks (max 100 records per batch), enforces per-tier burst pacing (100/190/200 per 10s), implements automatic exponential backoff with jitter on 429 responses, and tracks daily quota consumption across all connected accounts. Unlike self-hosted MCP servers where rate-limit logic is the user’s responsibility, Porter handles token rotation via OAuth (no static keys in JSON files), minimizes scopes to read-only by default, and surfaces validation warnings when HubSpot custom rules would be bypassed. That’s the behavior HubSpot’s automated systems handle gracefully — no throttling, no partial syncs, no exposed credentials.

Frequently asked questions

Ready to chat with your HubSpot?

Open ChatGPT, add the Porter connector, and ask your first question. If you don’t have Porter yet, start a free trial and connect your HubSpot account — you’ll be chatting with your campaigns in under five minutes.

rocket_launchStart free Porter trialopen_in_newOpen ChatGPT