Control HubSpot credential retrieval for AI agents
HubSpot reporting and CRM automation need different provider permissions. Create appropriately scoped private app tokens in HubSpot, then use Gazebo to decide which agents may retrieve each stored token. The runtime receives the token with its existing HubSpot permissions.
Why should AI agents use scoped HubSpot credentials?
Agents sharing a HubSpot token share its CRM scopes. Gazebo adds named agent identities, retrieval policies and retrieval logs, not object-level enforcement after delivery. Use HubSpot scopes for provider access and HubSpot records for actual changes. A copied token requires provider-side revocation or rotation.
How it works
- 1
Connect your HubSpot account to Gazebo using a private app token scoped to the objects your agents actually need.
- 2
Create separate HubSpot tokens for reporting and write automation where supported, then grant each Gazebo profile retrieval of the appropriate token.
- 3
Each agent calls get_credential via MCP. Gazebo checks the retrieval policy and returns the configured HubSpot token.
- 4
Every access is logged: which agent, which timestamp, approved or denied.
- 5
Revoke future HubSpot token retrieval per agent. Revoke or rotate the provider token if a retrieved value may have leaked.
Common use cases
Lead qualification without full CRM access
Use a HubSpot token with the required read scopes for contacts and deals, then grant retrieval to the qualification agent. A Gazebo GET policy cannot make a write-capable token read-only.
Pipeline reporting with an audit trail
Gazebo records which reporting agent retrieved a HubSpot token and when. Use HubSpot activity records to investigate the pipeline data subsequently accessed.
Revoke future CRM credential retrieval
Disable the Gazebo grant to stop new retrieval. Revoke or rotate a retained token in HubSpot if needed and update other workflows sharing that token.
Connect HubSpot to Gazebo
Control agent credential retrieval for HubSpot. Record retrieval attempts and revoke future access.
Connect HubSpotAgents that commonly use HubSpot
Further reading
HIPAA for AI Agents: Technical Safeguards for PHI
Assess ePHI workflows, required and addressable safeguards, vendor agreements and evidence without confusing retrieval features with HIPAA compliance.
GDPR for AI Agents: Data Protection and Breach Response
Assess agent data flows, organisational roles, risk-based security, recordkeeping and breach duties without treating retrieval controls as proof of GDPR compliance.