Developers can build supported custom WoodsPortal experiences with the ESM JavaScript SDK and use WoodsCLI to scaffold, preview, build, and upload HubSpot modules or themes.

Use the JavaScript SDK

  • The SDK exposes WoodsPortal authentication, CRM, files, notes, email, uploads, pipelines, and navigation APIs.
  • The documented runtime is JavaScript or TypeScript with Node 18 or later and ESM.
  • A custom experience still requires supported API configuration, authentication, permissions, and developer implementation.

Initialize a project with WoodsCLI

  1. Install the current @woodsportal/hubspot-kit package through the approved package workflow.
  2. Run the WoodsCLI initialization command.
  3. Choose a HubSpot module or theme project.
  4. Select build and authentication options.
  5. Choose the authentication scaffold tier appropriate for the project: none, starter, SSO, or full MFA.
  6. Generate the project.
  7. Run the local preview or development workflow.
  8. Build the bundle and use the HubSpot CLI integration to upload or watch supported assets.

Rules and limits

  • WoodsCLI is intended for HubSpot modules and themes, not HubSpot UI extensions.
  • The full authentication scaffold is the appropriate baseline for a full production portal, but it still requires implementation and configuration.
  • Do not treat generated scaffolding as a finished security review or production deployment.
  • Do not direct users to the developer portal until its production availability is verified.

[Visual placeholder: SDK example and WoodsCLI | Safe development project | Initialize with an authentication tier, preview, build, and upload | The generated module uses the intended SDK and no unsupported production host is introduced.]