HubSpot

Capped

hubspot.comSourcedUpdated 27 Oct 2026 · yesterday

You can create a HubSpot OAuth app and connect real customer accounts on the same day, but a marketplace-distribution app is capped at 25 installs until it is listed on the HubSpot Marketplace. Listing needs at least 3 active installs from production accounts not affiliated with you, live public URLs, and a review by HubSpot's Ecosystem Quality team. The first review takes up to 10 business days, and the full feedback process can run up to 60 days.

Your work: 1–3 days
Waiting on HubSpot: 2–12 weeks
First user connects: Today, in about 1 hour (in a developer test account or your own HubSpot account)

3 not confirmed 8 sources Why this tier How did it go?

.md JSON

Use with your agent

Set up a HubSpot OAuth app for our integration, as far as you can.
Guide: https://oauth-guide.akshatsethi.com/apps/hubspot.md (updated 27 Oct 2026)

Capped. Hands-on work: 1–3 days. Waiting on HubSpot: 2–12 weeks.

Check these exist first:
- HubSpot developer account [human]
- HubSpot CLI v7.6.0 or later [agent]
- Redirect URI for your OAuth client [agent]

Needed later, not now:
- Signed Acceptable Use Policy (for beta)
- 3 active installs from unaffiliated customers (for launch)
- Live terms, privacy policy, support and pricing pages (for launch)
- Technology Partner Program Agreement (for launch)

Steps, in order:
1. [human] Install and authenticate the HubSpot CLI
2. [agent] Create an app project with OAuth auth. Run `hs project create` and pick App. Choose Marketplace distribution and OAuth authentication, then give the app a unique `uid` in `app-hsmeta.json`. Watch out: If you choose private (allowlist) distribution, you're capped at 10 accounts (100 for Solutions Partners), and the app can't be listed until you switch it to marketplace distribution. Changing a uid after upload creates a new component.
3. [agent] Set redirect URLs and scopes. In `app-hsmeta.json`, set `config.auth.type` to `oauth`, add your redirect URI to `redirectUrls`, and list `requiredScopes`, `optionalScopes` and `conditionallyRequiredScopes`. Also fill in name, description, support and permittedUrls. Watch out: The redirect URI must match your OAuth client exactly, including http vs https. Every required scope must be available in the installing account, or the install fails, so put non-essential scopes in optionalScopes.
4. [agent] Upload the project to HubSpot. Run `hs project upload` to build and deploy the app. Run it again after any scope or redirect change.
5. [human] Copy the client ID and secret
6. [agent] Install the app in a test account. Under Development → Test accounts, create a test account. Then on your app's Distribution tab, click Add test install(s), then Install, tick the unverified-app checkbox and click Connect app. You can also install in your own standard account with Install now.
7. [human] Sign the Acceptable Use Policy
8. [human] Get 3 active installs from real customers
9. [human] Submit your Marketplace listing
10. [provider] Wait for Ecosystem Quality review (wait 2–12 weeks)

Rules:
- Do [agent] steps yourself. Steps in HubSpot's dashboard need a browser I'm signed in to; without one, give me the exact clicks and values instead, then carry on with the code.
- At each [human] or [provider] step, stop and tell me exactly what's needed.
- Never put client secrets in chat, code or commits. I paste them into our OAuth client or secret manager myself.
- Claims marked Inferred or low confidence in the guide are unverified. Check them and tell me what you find.
- If the guide doesn't match what you see (a page, field or requirement), tell me and report it so it gets fixed: POST https://oauth-guide.akshatsethi.com/api/reports with {"app": "hubspot", "step": 2, "message": "what you saw"} (step is optional), or call the report_problem MCP tool. Never put secrets or personal data in a report.
- When setup ends (users can connect, or it's waiting on HubSpot's review) or you can't get past a step, report how it went so the guide improves: POST https://oauth-guide.akshatsethi.com/api/reports with {"app": "hubspot", "outcome": "worked" | "waiting" | "stuck", "step": 3, "message": "what happened"}, or call the report_setup MCP tool. Stopping for me at a [human] step isn't stuck: don't report that.
- Finish with what's done, the redirect URI and scopes used, and what's left before public launch.

Paste into Claude Code, Cursor or any agent.

HubSpot

Plan

SetupBefore you start

BuildDeveloper and test accounts

BetaUnlisted, up to 25 installs

LaunchListed on the Marketplace

Why capped

Scopes

When you get stuck

Not confirmed

Sources

Feedback

HubSpot

Plan

SetupBefore you start

BuildDeveloper and test accounts

BetaUnlisted, up to 25 installs

LaunchListed on the Marketplace

Why capped

Scopes

When you get stuck

Not confirmed

Sources

Feedback