[ HubSpot / AI agents ]

HubSpot and your ERP, in one assistant

engini gives Claude, ChatGPT or your own agent a scoped way into HubSpot, and into the ERP and support tools around it. An account manager can ask what a customer bought, owes and opened tickets about, and update the deal in the same conversation. You choose the tools; every call is recorded.

HubSpotNetSuiteClaudeChatGPTMCP
Read the HubSpot guide →
Before a renewal call
  1. "Brief me on Northwind before my call"asked in Claude
  2. HubSpot logo
    HubSpot readdeals, contacts, open tickets
  3. NetSuite logo
    NetSuite readinvoices: 1 overdue, 42 days
  4. HubSpot logo
    Deal updated after the callnext step and close date set
Illustration of the flow on this page, not a product screen.
What it does
Your assistant answers from HubSpot and the ERP, and updates HubSpot
Systems
HubSpot, NetSuite or SAP S/4HANA, Claude, ChatGPT or your code
Built with
An engini MCP server, or a toolset over the SDK, CLI or REST API
Your control
Which tools, which accounts, read or write; every call recorded
[ 01 / The problem ]

Customer context is spread across three systems

Before a renewal call, an account manager checks HubSpot for the deal and contacts, the help desk for open tickets, and asks finance whether the customer is current. After the call, they go back to HubSpot to update the deal. Every step is small; together they are why preparation gets skipped and records go stale.

They already use Claude or ChatGPT for everything else. The question IT asks is how to let the assistant into HubSpot and the ERP without handing it a master key.

What it takes to say yes

  • The assistant gets only the tools it needs: read invoices, read and update deals, no delete.
  • No HubSpot token or ERP password pasted into a prompt.
  • IT can see who uses it and what each call did.
  • The same setup works for Claude, ChatGPT and in-house agents.

How engini makes it work

You create an engini MCP server that exposes only chosen connections and tools, for example read companies, deals and tickets in HubSpot, update deals, and read invoices in NetSuite. People add it to Claude or ChatGPT and sign in through engini over OAuth. engini shows who uses each MCP server and records every run under the user who triggered it.

engini acts with the permissions of the connected account. For each person to act as themselves in HubSpot, each needs their own connection; one shared address where every employee signs in as themselves is not offered. For in-house agents on the SDK, CLI or REST API, a toolset scopes the calls, enforced on the server.

[ 02 / How it works ]

HubSpot in your assistant in four steps

01 / Connect

HubSpot and the ERP

Connect HubSpot with OAuth (engini keeps the token) and connect NetSuite or SAP S/4HANA with an account whose role fits.

02 / Scope

Choose the tools

Create an MCP server with only the tools people need: read companies, deals and tickets; update deals; read invoices. No delete.

03 / Add

Add it to the client

Add the server to Claude or ChatGPT as a custom connector and sign in through engini. There is no key to copy.

04 / Use

Ask and update

Ask for a briefing, then tell the assistant what to update. Each call is recorded under the person who asked.

[ 03 / What the agent reads and writes ]

What the assistant can reach

Only what the MCP server exposes. A typical setup for account managers:

SystemRecordsAccess
HubSpotCompanies, contacts, deals, ticketsRead
HubSpotDeal next step, stage and close dateUpdate
NetSuite or SAP S/4HANAInvoices and open balancesRead
enginiWho uses each MCP server; History and audit logRecorded
[ 04 / Build it with the engini skill ]

Describe it in plain words. The engini skill builds the workflow.

engini skills is engini’s plugin for Claude Code and Codex. Its workflow agent, Flo, turns a plain-language request into an engini workflow: it designs the steps, dry-runs them against your own engini account, shows you a proposal, and creates the workflow only after you approve it, always turned off. You check it in the engini designer and turn it on.

Blurred landscape photo with the HubSpot logo, the engini mark and the NetSuite logo joined by a thin line, labeled one briefing: deals, tickets, invoices

Editorial image: one briefing from three systems.

Claude Code: install once
/plugin marketplace add engini/skills
/plugin install skills@engini
Then ask for this solution
Build a workflow in my engini account that I can call from Claude over MCP: given a company name, read the HubSpot company with its open deals and open tickets, read that customer's open invoices from NetSuite, and return a short briefing with deal stages, ticket subjects and any overdue invoices.
  1. You need an engini account, the engini CLI (npm i -g @engini/cli) and a workspace-scoped API key, ideally a dedicated least-privilege one.
  2. Connect the systems this flow uses in engini first. Flo never creates or changes a connection and never handles your key; it tells you which command to run.
  3. Flo checks your login and workspace, searches the tool catalog, compiles the plan and shows a proposal table with every step. It creates the workflow only when you approve that proposal, and it creates it turned off.
  4. Open it in the engini designer, fill anything it left for you, and turn it on.
engini skills for Claude Code and Codex →
What the skill will never do on its own →
[ 05 / Agent Policy ]

The agent does only what you allow. Every run is on the record.

Agent Policy is how you govern agents in engini: the tools each agent may call, the account each tool uses, and a record of every call.

Toolsets

Scope every call

Hand the agent a toolset: only the tools it needs, each on the connection you choose, for example read only. engini enforces it on the server for CLI, SDK and REST API calls; a call outside the toolset is refused. An MCP server exposes only the connections and tools chosen when you set it up.

Identity

Acts with the account you connect

engini acts with the permissions of the connected account. Connect a person’s own account and it acts as that person; use a shared integration account and it acts as that account. Every run is recorded under the user who triggered it.

Audit

History and audit log

Each tool call and workflow run is recorded in History and the audit log, which supports export and streaming to your SIEM. Your agent never needs your credentials: engini stores them and adds them when it runs each call.

SOC 2 Type IIISO 27001GDPRHIPAA compliant
[ 06 / Try it now ]

Build it on your own data today

Start free, connect HubSpot, and build this flow with the engini skill, in Workflow Studio, or from your own agent.

  • 01Workflow Studio. Build the flow on a visual canvas, with an AI agent step where judgment is needed. Start free →
  • 02Your own agent. Give Claude, ChatGPT or Cursor an engini MCP server with only these tools. MCP client setup →
  • 03The engini skill. Ask Flo in Claude Code or Codex and review its proposal. Install the skill →
[ 07 / Questions ]

Questions buyers ask before they start

Can Claude or ChatGPT read and update HubSpot?

Yes, through an engini MCP server that exposes only the HubSpot tools you choose. The client signs in through engini over OAuth.

Can the same assistant see ERP data?

Yes. Add NetSuite or SAP S/4HANA tools to the same MCP server, for example read-only invoices, and the assistant can combine both in one answer.

Can we stop it from deleting anything?

Yes. Leave delete tools off the MCP server. The assistant only sees and can only call the tools you expose.

Does each person act as themselves in HubSpot?

When each person connects their own account, engini acts as that person, with their permissions. A shared connection acts as that shared account. Either way, every run is recorded under the user who triggered it.

Can IT see who is using it?

Yes. engini shows who uses each of its MCP servers, and the audit log supports export and SIEM streaming.

How is this different from Breeze?

Breeze is HubSpot’s AI inside HubSpot. engini lets the assistants your teams already use, and your own agents, work across HubSpot, your ERP and your other systems under one set of controls.