AI agent for HubSpot: tie ad spend to pipeline and closed-won revenue
HubSpot connects per person: each teammate signs in with their own HubSpot user, and everything the agent reads or changes for them runs with that person's HubSpot permissions — it sees only the records they can see in HubSpot. The agent counts your deals, won revenue and new contacts by the source HubSpot recorded for them, and compares that with the conversions your ad platforms claim. It works in counts and totals — contact emails, phone numbers and names are withheld from its answers — and by default every change to a record goes through the approval step first. The two permissions HubSpot requires are read permissions; the write permissions are optional, and a portal that grants none of them stays read-only.
Connecting it, and what it asks for
- 1Install from the HubSpot App Marketplace listing, or open Integrations in Agent Planners and click Connect HubSpot as you on the HubSpot card.
- 2Sign in to HubSpot with your own user, pick the portal, and approve. Every read and write the agent makes for you runs with your own HubSpot permissions — it sees only the records you can see in HubSpot. Each teammate connects as themselves.
- 3An install started from the Marketplace finishes in Agent Planners: sign in (or create a free account), check the workspace it will join, and press Connect HubSpot as you.
- 4Write the goal.
crm.objects.contacts.read and crm.objects.deals.read (required — count contacts and deals by source, stage and lifecycle); optional crm.objects.companies.read and crm.objects.companies.write (read, create and update companies), crm.objects.deals.write (create and update deals), and crm.objects.contacts.write (create and update contacts — a person approves each one). If HubSpot leaves out an optional permission, the connection still succeeds and those changes stay off. The HubSpot card shows which requested permissions your own connection lacks, and Check my permissions re-reads your own connection's permissions (it reads only). A first goal worth typing: Which ad channels produced the deals we actually won last quarter, and what did each won deal cost?Every person connects with their own HubSpot permissions
- HubSpot requires an AI app to run every read and write with the permissions of the individual person it acts for, so HubSpot is connected per person: each teammate presses Connect HubSpot as you once.
- A task acts as the person who started it (a scheduled task as the schedule's creator), an alert rule or dashboard as its creator, an API key or MCP connection as the person who created it, and an approved change as the person who approved it. Another person's connection is never used — when that person has not connected, the step is refused and says who must connect.
- A portal connected the older, workspace-wide way is paused until an admin or editor switches it: Switch to per-person connection keeps the same portal, with its tasks, schedules, alert rules, dashboards and memory; after that each person connects as themselves.
- HubSpot does not open owners, lists, marketing campaigns, forms, marketing email, files, landing pages, custom events or its pipelines API to per-person apps, so those tools say they are not available instead of failing, and a deal can be attributed by traffic source but not by marketing campaign.
- Disconnecting removes only your own connection; leaving the workspace removes yours automatically.
What the agent reads
- Deals and closed-won revenue by original or latest traffic source, deal stage or pipeline — with win rates.
- New contacts by original or latest source and lifecycle stage, counted exactly — never listed.
- Counts and searches of contacts, companies and deals, your portal's own property definitions, and the records linked to a deal or company.
- Deal stages: because HubSpot keeps its pipelines API closed to per-person apps, the agent learns the stages from the deals you can see (and HubSpot's default stages), and says when a stage name is inferred.
- Daily new contacts, deals created, deals won and won amount, with anomaly detection against a weekday-aware baseline — and alert rules on the same four series.
- Leads per channel: the contacts that became leads in a period, counted by their original or latest source from the contact records (HubSpot's lead lifecycle date) — never listed.
What the agent can change — through the approval step
- With the write permissions your portal grants: create and update companies, deals and contacts, link two records, and archive a record.
- By default every change goes through the approval step. Creating or editing a contact, changing a deal's stage or owner, and archiving anything always wait for a person — also on a task or schedule set to auto-approve; a workspace's own OAuth app is the one exception.
- A new deal is created in an open stage. Adding notes or tasks is not available on every per-person connection — do not rely on it.
- It never emails your contacts, never changes a contact's marketing or consent status, and never moves money.
Why HubSpot and your ad platforms disagree
- Ad platforms count their own conversions inside their own attribution windows; HubSpot records where each lead first came from.
- A deal's source is copied from its earliest contact, so it tells you which channel brought the lead in — not which ad closed it.
- The agent shows both side by side, with cost per lead, per deal and per won deal, instead of adding them together.
Things worth knowing
- Deal amounts are reported in your portal's company currency; deals in other currencies are listed separately, never added in.
- HubSpot limits how fast one portal can be read (and everyone using it shares that budget), so the agent counts and aggregates rather than paging through records.
- A contact's email, phone or name is returned only when a person's own request asks for those fields on specific people — never on a schedule, an API task, an autonomous run or over MCP, and never more than 20 rows.
- Removing your connection here does not uninstall the app from HubSpot; you can remove it under Settings → Integrations → Connected apps in HubSpot.
What Agent Planners keeps
- Your connection: your HubSpot access and refresh tokens (encrypted, bound to you and that portal), the portal's id and name, your HubSpot user id, the permissions HubSpot granted and when you connected.
- Task results: the counts, totals and record ids a task read, kept with the task until your workspace's task-history retention deletes it (90 days by default) or someone deletes the task. Contact details appear there only when your own request asked for them.
- Memory: what the agent learns from a HubSpot run is saved with email addresses and phone numbers masked.
- Disconnecting deletes your tokens. When an admin removes the portal, every person's connection to it is deleted by our daily sweep.
Frequently asked questions
- Does Agent Planners support HubSpot?
- Yes, through a per-person connection: deal and contact attribution by traffic source, record counts, properties and associations, deal stages, daily anomaly detection and leads per source (the contacts that became leads). HubSpot's own saved reports and dashboards are not read.
- Can the agent change my CRM or email my contacts?
- It can create and update companies, deals and contacts and archive records, with the write permissions your portal grants — each through the approval step by default, and contact changes, stage or owner changes and archives always wait for a person, except from a workspace's own OAuth app. It never emails your contacts.
- Does the agent see my contacts' personal details?
- It sees only the contacts you can see in HubSpot, and it works in counts and totals: contact emails, phone numbers and names are withheld from its results unless a person's own request asks for them on specific people.
- Who can connect it?
- Every person connects as themselves (Connect HubSpot as you), so the agent sees only what that person can see in HubSpot. Adding a new portal to the workspace, or switching a workspace-wide connection over, is done by an admin or editor; HubSpot may ask for a Super Admin or a user with the Marketplace access permission to install the app.
- Whose HubSpot permissions does the agent use?
- The acting person's own: the person who started the task, created the schedule, alert rule, dashboard or API key, or approved the change. Another teammate's connection is never used — without a connection of their own, the step is refused.