Use hs project create for a New HubSpot Marketplace App

This page is for teams creating a new public or Marketplace app, especially after the legacy public app creation path is no longer available for their developer account. HubSpot's create-app documentation points new developer platform apps toward the CLI-based Projects workflow, with `hs project create` as the setup command to review.

This is not the page to use when you only need to maintain an existing legacy public app. It is also not enough for a private app migration decision. In those cases, classify the app first and follow the relevant migration or private app docs.

The output you want before a developer starts is a short creation brief: target developer account, app name, authentication type, OAuth redirect URLs, scopes, feature list, Marketplace intent, and who owns listing/support/privacy materials.

First satisfy the CLI preflight: Node.js and CLI versions recorded, `hs account auth` completed, and the target developer account confirmed. From the parent directory where the project should live, run `hs project create`. The current project-command reference says the interactive flow asks for name, destination, project base, distribution, authentication type, and features; choose App as the project base for the full app-creation guide.

The expected local result is a new project directory containing top-level `hsproject.json` and an `src` folder. Do not continue if those are absent or the generated choices do not match the creation brief. Review the generated app and feature `*-hsmeta.json` files, set stable UIDs before first upload, and configure OAuth redirect URLs and scopes when OAuth applies.

Run `hs project validate` from the project directory before `hs project upload`. Fix validation findings rather than using upload as the first syntax check. A successful upload creates a build; open it with `hs project open`, confirm the build/deploy result, connect OAuth client credentials to the backend when applicable, and complete a test install before calling the task finished.

A complete creation handoff should show the recorded Node and CLI versions, intended account, generated project path, `hsproject.json`, selected distribution and auth model, stable UIDs, validation result, build ID, deploy state, and test-install result. Project creation alone is not a completed app workflow.

If creation stops before the expected directory and files exist, keep the incomplete directory out of the upload path, confirm account/auth and prompt choices, and rerun only after deciding whether to remove or preserve the partial output. If `hs project validate` fails, repair the reported `app-hsmeta.json` or feature configuration before upload. If the build fails, inspect Builds & Deploys through `hs project open`; do not claim installation readiness.

For OAuth apps, an uploaded project is still incomplete until the backend uses the app's HubSpot client ID and client secret and the configured redirect URL matches the tested OAuth callback. Keep credentials out of source control, tickets, and agent prompts.

A Projects CLI app can still fail a launch workflow if Marketplace materials are unfinished. Assign owners for support contact, privacy policy, testing instructions, screenshots or assets, and install-flow evidence.

Keep the product language precise with clients: this checklist helps prepare a reviewable workflow, but it does not guarantee Marketplace approval or certify compliance. Marketplace requirements must be checked against HubSpot's current listing documentation before submission.

If the app includes classic CRM cards, create a separate app-card modernization task. The CRM card deadline is not the same as the May/June legacy public app creation sunset.