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
- Install the current @woodsportal/hubspot-kit package through the approved package workflow.
- Run the WoodsCLI initialization command.
- Choose a HubSpot module or theme project.
- Select build and authentication options.
- Choose the authentication scaffold tier appropriate for the project: none, starter, SSO, or full MFA.
- Generate the project.
- Run the local preview or development workflow.
- 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.]