Back to Guides
Generated on 2026-10-31: Provider OAuth rules and review policies change frequently. Always verify current submission requirements with the official HubSpot documentation before submitting for production approval.

HubSpot

HubSpot requires creating a developer account, configuring app settings, and managing specific scopes. While private apps or standard public apps are straightforward to set up, publishing to the marketplace requires rigorous security reviews.

www.hubspot.comGenerated on 2026-10-31
At a glance
Executive breakdown in plain language
Difficulty
MEDIUM

HubSpot requires creating a developer account, configuring app settings, and managing specific scopes. While private apps or standard public apps are straightforward to set up, publishing to the marketplace requires rigorous security reviews.

Setup Time
30 minutes to 1 hourCommunity reported

Active engineering effort required to register the OAuth app, set redirect URLs, and obtain credentials.

Approval Wait
1 to 5 business days for Marketplace apps; Instant for private developer accountsFrom official docs

Developer test accounts allow instant local testing without waiting for app approval.

Biggest Blocker
Incorrect or missing redirect URL leading to redirect_mismatch errors.

Fix: Ensure the redirect URI registered in the HubSpot app settings matches the URI passed in your authorization request character-for-character.

Required Before Starting
From official docs
• HubSpot Developer Account or Developer Test Account (From official docs)
• Valid Redirect URL for OAuth 2.0 flow (From official docs)
• Selection of appropriate OAuth scopes matching the AI agent's required HubSpot interactions (From official docs)
• Privacy policy and terms of service URLs (required for public apps) (From official docs)

Step-by-Step Setup Guide

4 steps
From official docs

Follow these sequential actions to register your OAuth application and configure endpoints.

1

Create a HubSpot Developer Account

Sign up for a free HubSpot developer account or log into your existing HubSpot portal.

Open in HubSpot Console
2

Create a New App

Navigate to the Apps section in your developer account and click 'Create app'.

Open in HubSpot Console
3

Configure Auth Settings

Set up your Auth settings by adding your redirect URLs and noting your Client ID and Client Secret.

Open in HubSpot Console
4

Select Scopes

Choose the necessary OAuth 2.0 scopes (e.g., crm.objects.contacts.read, crm.objects.deals.write) required by your AI agent.

Open in HubSpot Console

Common Blockers & Fixes

2 blockers
Community reported

Anticipate the pitfalls and approval rejections that catch most agent developers off guard.

Incorrect or missing redirect URL leading to redirect_mismatch errors.
Action Plan: Ensure the redirect URI registered in the HubSpot app settings matches the URI passed in your authorization request character-for-character.
Requesting scopes that require additional permissions or app marketplace review.
Community reported
Action Plan: Use a developer test account to test sensitive or restricted scopes before submitting your app for public review.

What an agent can do vs what you must do

Agent vs Developer
From official docs

A clear division of labor: tasks your autonomous agent can handle vs actions requiring human developer authorization.

What an Agent Can Do
  • Generate PKCE parameters and authorization URL strings
  • Exchange authorization codes for access and refresh tokens
  • Programmatically invoke HubSpot APIs using valid tokens
What You Must Do Yourself
  • Log into the HubSpot developer portal using 2FA
  • Create the app entity and configure redirect URIs manually
  • Accept terms of service and submit app for marketplace review if public

Managed OAuth vs Custom Credentials

From official docs

Evaluate whether using a managed integration platform (like Composio) is sufficient or if you must create your own app.

This tool was built for a Composio assignment, and Composio sells managed OAuth.
When Managed OAuth is Enough
Building standard AI agents that need pre-built connectors to read and write CRM data without publishing a standalone public integration to the HubSpot Marketplace. Note: This tool was built for a Composio assignment, and Composio sells managed OAuth.
When Custom Credentials are Required
Building a commercial product intended to be listed publicly on the HubSpot App Marketplace under your own brand identity and client credentials.

Key Claims & Verification Status

From official docs

Specific factual statements evaluated against sources.

HubSpot apps are managed and registered via the HubSpot Developer Portal.
Developer test accounts allow instant testing without approval waits.

Official Sources & Documentation

1 sources
From official docs

Open Questions & Uncertainties

1 open questions
Unverified estimate

Areas currently subject to policy changes or requiring ongoing real-world verification.

  • Are there specific automated security scanning requirements (like CASA) currently mandated for all public HubSpot Marketplace listings?