Nagent With HubSpot: AI Agents That Work With HubSpot

Run an AI agent inside HubSpot
Auto-score leads, enrich records, and trigger sequences from a Nagent agent wired into HubSpot.
See the HubSpot agent →Connect Nagent to HubSpot and you keep HubSpot as your CRM while Nagent's sales agents work beside it. You choose which HubSpot actions agents may call and which agents may call each one. Anything that creates or changes a record waits for a person until the agent's level covers it. NORA, the outbound research lead, finds and researches new accounts, and your team approves what she sends.
Nagent is multiplayer AI for growth: people and AI agents in one shared context, delivering the number. HubSpot is one of the tools on the integrations list that those agents can work in.
How do you connect HubSpot to Nagent?
There are two ways, and they behave differently.
1. Sign in to HubSpot. On the Integrations page of your workspace, the Composio card connects the tools you already use, HubSpot among them. You select Connect, approve access on HubSpot's own sign-in page, and return to Nagent. Nothing is available to an agent yet. You tick the actions agents may call, one at a time, then narrow each action to the agents that need it. The steps are in connecting a tool.
2. Add a connector from the HubSpot template (Beta). A connector gives agents only the operations it declares. The HubSpot template signs in with a HubSpot service key, or a legacy private app's access token, and declares five operations: list, get, search, create and update CRM objects. HubSpot's CRM holds records under objects such as contacts, companies, deals and tickets. A connector made from a template starts as Pending review, so nothing reaches an agent until you confirm or disable each operation. Connectors are not on every plan; the Integrations page shows the card either way and says what is missing. See connectors.
One note on the second route. HubSpot no longer lets accounts create new legacy private apps, and says existing ones continue to work. For a new connection, create a service key in HubSpot with only the CRM scopes the connector needs.
What can Nagent agents read and do in HubSpot?
Only what you allowed. An allowed action becomes a tool an agent calls when its work needs it: in a team room conversation, during a run, or after an event starts the work.
What agents can call, Sign-in connection: The HubSpot actions you tick, Connector template: List, get, search, create and update CRM objects
Lookups, Sign-in connection: Run without asking once the action is marked as one that only reads. An action not yet marked waits like a change, and an admin can confirm it as a read on the Integrations page, Connector template: Run without asking, once you confirm them as reads
Creates and updates, Sign-in connection: Run alone at L4 Represent and above, Connector template: Run alone from L3 Operate when confirmed as an internal act
These are examples of work you can ask for. They are not prebuilt automations.
SERA looks up a record. In the Sales room, ask SERA, the AI Sales Chief of Staff, for a contact, company or deal, and she uses the list, get or search action you allowed.
NORA checks HubSpot before she reaches out. Ask NORA to search HubSpot for a company she has found, so your team does not prospect an account it already has.
NORA proposes the HubSpot record after a handoff. NORA writes a qualified account into Nagent's own CRM. Creating the same contact in HubSpot is a separate action, and it queues for approval when her level does not cover it.
LIPI and VANI draft, and do not write to HubSpot. The two email writers, both in Beta, write drafts only. By default they are not offered write actions in a connected CRM.
You bring HubSpot contacts in as a file. HubSpot can export records to a CSV file. Bulk import in Nagent's CRM takes a spreadsheet or CSV of up to 5,000 contacts and can enrol them in a sequence. A person does this, not an agent.
By default, SERA and NORA are the Sales agents offered the actions of a connected CRM. The Tools pane on each agent's page lists every tool that agent is sent, and its Scope switch lets you choose them by hand.
What always waits for a person's approval?
Changes below the agent's level. The action is queued, not dropped. It shows on Actions under Awaiting approval, where a person selects Approve or Dismiss.
Every e-mail NORA sends. She never sends a draft nobody approved, and on a new workspace every send waits for a person, whatever her level shows.
Work started by an event. An event in a connected tool passes the same checks. It cannot make an agent do something it could not do when asked.
An agent's level rises one step at a time, and a person decides each raise. L4 Represent is available from the Business plan. Three controls stay separate throughout: which actions exist, which agents may call each one, and whether a call runs unattended. Widening one never widens the others. The levels are explained in autonomy and governance.
What does Nagent not do with HubSpot?
No automatic sync. Nagent's CRM and HubSpot are separate records. Nothing mirrors your HubSpot pipeline into Nagent, or back, on its own.
No sending through HubSpot. NORA's prospect e-mail leaves from a team member's own mailbox, a connected sending tool or your own sending domain.
Nothing on a schedule just because it is allowed. Allowing an action never makes it fire on a timer. An agent calls it when its work needs it.
No delete in the template. The connector template has the five operations above and nothing else. On the sign-in route, leave destructive actions unticked unless a real task needs them.
No self-healing connection. An expired or failed connection fires nothing until someone connects it again.
Who is Nagent with HubSpot for?
It suits a sales team that wants to keep HubSpot as its CRM and add agents for the work around it: finding accounts, researching them, drafting outreach and proposing record changes for a person to approve.
It is a poor fit if you want a two-way sync with no approvals, or agents that live inside HubSpot's own screens. Nagent's agents work in Nagent and reach HubSpot through the actions you allow.
Frequently Asked Questions
Do Nagent's AI agents replace HubSpot?
No. HubSpot stays your CRM. Nagent adds a Sales team of agents led by SERA, with NORA on outbound research, and they reach HubSpot only through the actions you allowed.
Can I build an AI SDR agent with HubSpot and Gmail?
You do not have to build one. NORA is a prebuilt outbound agent: she finds companies that match your customer profile, researches them and drafts the first e-mail, which VANI writes for her. HubSpot is connected for record lookups and proposed changes. In Beta, NORA's approved e-mail can leave from a team member's own Gmail mailbox.
Is the HubSpot connection in Beta?
A connector made from the HubSpot template carries a Beta badge. The sign-in connection is not labelled Beta.
Can an agent delete HubSpot records?
Not through the connector template, which has no delete operation. On the sign-in route an agent can call a delete only if you ticked that action, and the guidance is to leave it off.
See it on your own stack
Bring your HubSpot set-up and we will show which actions to allow, which agents to give them to, and what your team would approve. See the full integrations list, or book a demo.