HubSpot

Each member connects their own HubSpot account. Through HubSpot's MCP server, their OpenCode can then:

• Find and read contacts, companies, deals, tickets and other CRM records.
• Create and update records, and log calls, emails, meetings, notes and tasks.
• Read campaigns and their metrics, and your account's users, teams and owners.

OpenCode works as the HubSpot user who connected.

• An OpenCode Console workspace with Integrations. Integrations is in early access: if your workspace doesn't have an Integrations tab yet, email help@anoma.ly.
• An owner or admin of the workspace to add HubSpot. Members can't add integrations.
• A HubSpot account for each member who connects. A Super Admin, or a user with App Marketplace access, may need to install the connector in your HubSpot account before anyone else can connect.
• Each member's OpenCode signed in to Console, as Connect OpenCode in Console shows.

If you're an owner or admin and your workspace doesn't show Integrations yet, email help@anoma.ly to have it turned on.

1. An owner or admin opens Integrations in Console and clicks Connect on HubSpot, or uses Connect HubSpot at the top of this page.
2. They don't choose whose accounts it uses: each member connects their own HubSpot account, and there's no shared workspace account.
3. They sign in to HubSpot and approve the access OpenCode asks for.
4. Each member then opens HubSpot in Integrations and clicks Connect to sign in. If their OpenCode tries HubSpot before they have, it tells them where to connect.

Once a member connects, HubSpot appears in their OpenCode. Anyone can leave it out of their own OpenCode with Include in your OpenCode config on its page.

Console stores each sign-in's access and refresh tokens, encrypted, and sends them only to HubSpot. It doesn't look up your HubSpot profile. It also records the tools HubSpot lists (their names, descriptions and inputs) and its instructions for agents, so admins can review them.

Ask OpenCode in your own words. For example:

• Summarize the deals in the Decision maker bought in stage worth more than $10,000.
• What's the latest with Acme Inc.? Include any open tickets.
• Log a note on the Acme deal with a summary of today's call.

OpenCode reaches HubSpot through Console, which adds your credentials on the way, so your OpenCode never holds them. Results go back to your OpenCode, which passes them to the model it's using. Console logs each call (the integration, the tool, whether it was allowed and whose account it used) but never what was sent or returned.

Owners and admins review HubSpot's tools on its page in Integrations and can turn any of them off. By default, a tool HubSpot adds or changes stays hidden from OpenCode until an owner or admin approves it. Rules in Controls decide who can use HubSpot, and can limit it to tools that only read.

Disconnect your account

Open HubSpot in Integrations and click Disconnect. Console deletes its copy of your HubSpot tokens and any sign-in you had started. When someone leaves the workspace or is removed from it, Console deletes the accounts they connected for themselves the same way.

Remove HubSpot from the workspace

An owner or admin opens HubSpot in Integrations and chooses Remove… from the … menu. Console deletes HubSpot from the workspace with every account connected to it, the tools it recorded, its settings and members' choices. Disable… in the same menu turns it off for everyone instead and keeps all of that until it's turned back on.

Remove the app in HubSpot

Disconnecting only removes what Console holds. To end OpenCode's access on HubSpot's side too: In HubSpot, click the settings icon, go to Integrations, then Connected Apps, and uninstall OpenCode.

If you remove the app there first, Console shows your account as needing reconnecting once it's next used, and keeps the encrypted tokens until you disconnect or an admin removes HubSpot.

• Console keeps each HubSpot sign-in's tokens encrypted and sends them only to HubSpot, never to OpenCode.
• It records the tools and instructions HubSpot lists, so admins can review them. It doesn't look up your profile.
• It logs each tool call (who made it, the integration, the tool, the outcome and timing) for 30 days, never what was sent or returned, and doesn't keep tool results.
• Results reach your OpenCode and the model it's using.

The privacy policy explains how Anomaly handles personal data, and the terms of service cover using OpenCode. To ask for a copy of your data or for it to be deleted, email help@anoma.ly.

Email help@anoma.ly. We reply within two business days (Monday to Friday, excluding US holidays), and you don't need an account. The support page covers data requests, security reports and more.