Individual skill
hubspot-auth
Authenticate production HubSpot integrations and survive the auth-side failures — 30-min token expiry storms, 500K daily rate-limit burnout, scope drift, token leakage in commits, multi-portal credential routing, OAuth refresh-token decay. Use when hardening token caching, rotating private app credentials, building a multi-portal credential router, or recovering from 429/403 auth cascades. Trigger with "hubspot auth", "hubspot token cache", "hubspot rate limit", "hubspot scope drift", "hubspot multi-portal", "hubspot OAuth refresh".
plugins/saas-packs/hubspot-pack/skills/hubspot-auth/SKILL.md
Source commit 0500b275e963c027f6b410e8c49c0446945c574e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 12, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 2,915
- Repository last updated
- Nov 12, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai Repository topic
- automation Repository topic
- claude-code Repository topic
- devops Repository topic
- mcp Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- claude-code-plugins Repository topic
- developer-tools Repository topic
- llm Repository topic
- hubspot Declared skill tag
- oauth2 Declared skill tag
- authentication Declared skill tag
- token-management Declared skill tag
- rate-limits Declared skill tag
- multi-portal Declared skill tag
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 13,596 bytesSKILL.mdcore · 13,596 bytesSKILL.mdcore · 13,596 bytesSKILL.mdcore · 13,596 bytesreferences/API_REFERENCE.mddoc · 5,174 bytesreferences/implementation-guide.mddoc · 8,386 bytes
Read excerpt
# HubSpot Auth
## Overview
Authenticate a service to HubSpot and operate the auth layer in production. This is not a setup walkthrough — it is the auth code your integration runs at 3am when an OAuth token expires mid-batch, when a portal admin removes a scope, when an agency credential router sends a request to the wrong portal, and when on-call needs to rotate a leaked private-app token without dropping in-flight requests.
The six production failures this skill prevents:
1. **Token expiry storms** — OAuth access tokens expire in 1800 seconds. Every concurrent request notices expiry simultaneously, races to refresh, the token endpoint rate-limits at 10 auth calls/10s, the integration cascades to red.
2. **Daily rate-limit burnout** — retry storms on auth failures burn through the 500K daily API call quota before noon. Exponential backoff with jitter is non-optional.
3. **Scope drift** — a portal admin edits the private app's scopes or a connected OAuth app loses authorization. Cached tokens start returning `403`. Retrying does not help.
4. **Token leakage in commits** — `pat-na1-*` private-app tokens are wide-scope and not auto-expiring. A single leaked commit exposes the entire portal.
5. **Multi-portal credential routing** — agencies managing 50+ portals cannot use a single `HUBSPOT_ACCESS_TOKEN`. Requests sent to the wrong portal silently operate on the wrong data.
6. **OAuth refresh-token decay** — HubSpot refresh tokens expire after one year of non-use. Integrations that go idle (seasonal products, paused automations) silently lose access and require user reconnection.