flowstate-connector-hubspot Package Skill

Package: @epicdm/flowstate-connector-hubspot Repository: epic-flowstate-community Path: packages/flowstate-connector-hubspot Version: 1.0.0

Use this published Dojo skill as the package-level entrypoint. For detailed workflows, use the package-local skills listed below.

Primary Package Workflow

FlowState Connector HubSpot Auth

Status: Active Purpose: Configure and troubleshoot HubSpot OAuth for the manifest-only connector. Scope: packages/flowstate-connector-hubspot/connector.yaml, README, HubSpot app settings. Trigger: Auth setup, token exchange failures, missing scopes, redirect URI changes, permission reviews. Input: HubSpot app credentials, redirect URI, connector manifest. Output: OAuth configuration that connector-core can exchange for HubSpot API access.

Required Env Vars

HUBSPOT_CLIENT_ID=...
HUBSPOT_CLIENT_SECRET=...
HUBSPOT_REDIRECT_URI=...

These are declared as required manifest env vars. Do not rename them in docs or deployment config unless the manifest changes with matching tests.

OAuth Contract

kind: oauth2
authorizationUrl: https://app.hubspot.com/oauth/authorize
tokenUrl: https://api.hubapi.com/oauth/v3/token
pkce: false

PKCE is false for this connector. If HubSpot app policy changes require PKCE, update the manifest and add connector-core validation coverage before telling operators to enable it.

Scope Checklist

The manifest requests read-only CRM and schema scopes:

• crm.objects.contacts.read
• crm.objects.companies.read
• crm.objects.deals.read
• crm.objects.quotes.read
• crm.objects.invoices.read
• crm.objects.line_items.read
• crm.objects.owners.read
• crm.schemas.contacts.read
• crm.schemas.companies.read
• crm.schemas.deals.read
• crm.schemas.quotes.read
• crm.schemas.line_items.read

When adding endpoint coverage, add the matching HubSpot scope first, then update tests so the manifest parse and scope expectations protect it.

Troubleshooting

• Redirect mismatches usually mean HUBSPOT_REDIRECT_URI differs from the HubSpot app callback URL.
• Missing object data usually means the connected HubSpot account granted fewer scopes than the manifest expects.
• This connector is pull-only; OAuth success does not imply write-back support.

Verification

yarn workspace @epicdm/flowstate-connector-hubspot jest --config jest.config.cjs --runInBand

Created: 2026-06-30

Package Skill Inventory

@epicdm/flowstate-connector-hubspot Skill Inventory

Group skills by CRM workflows, not by the two YAML files listed in the generated feature matrix.

Review Gate

@epicdm/flowstate-connector-hubspot Skill Review

Created manifest-oriented package-local skills for HubSpot under packages/flowstate-connector-hubspot/.flowstate/skills.

Evidence Reviewed

• package.json
• README.md
• connector.yaml
• flowstate.plugin.json
• __tests__/connector.test.ts
• .flowstate/feature-matrix/inventory.md
• .flowstate/dojo/agent-skillset.md
• repository plan docs mentioning HubSpot connector/Jest config duplication

Known Drift Preserved

• No JS/TS public exports exist.
• V1 connector performs complete paged scans, not delta sync.
• Endpoint order matters for CRM relations.
• There is no connector-core bundled hubspot.yaml copy at review time.
• Duplicate Jest configs exist; the default package test script can fail unless Jest is pointed at jest.config.cjs.
• Generated Dojo material is generic and not publish-ready.
• Dojo publisher metadata currently drifts between generated artifacts.

Verification Status

• ASCII scan passed: no non-ASCII characters in .flowstate/skills.
• Skill frontmatter scan passed for all 6 SKILL.md files.
• yarn workspace @epicdm/flowstate-connector-hubspot jest --config jest.config.cjs --runInBand passed: 1 suite, 6 tests.
• yarn workspace @epicdm/flowstate-connector-hubspot build passed; build is a no-op by design.
• yarn nx build @epicdm/flowstate-connector-hubspot passed; Nx Cloud reported the existing unconnected-workspace 401 notice.

Start with this skill to understand the package purpose, then use the package-local focused skills for specific workflows. Keep this Dojo version aligned with packages/flowstate-connector-hubspot/package.json. Do not treat generated feature lists as lessons; use workflow evidence from CODE-REVIEW.md, SKILL-INVENTORY.md, and REVIEW.md.