1 Accepted solution
Hi @JerikaNguyen , you’re right that the new HubSpot Projects feature only supports Node.js/JavaScript today. There’s no official option to initialize a Python-based project.
The SDKs for Python, Ruby, PHP, etc. remain fully usable with private apps (now labeled “legacy apps”), but the “projects” environment is a different execution layer that HubSpot manages, so it enforces JavaScript runtimes only (https://knowledge.hubspot.com/help-and-resources/how-to-use-the-hubspot-projects-tool )
If your flow is just syncing Contacts, Companies, and Associations, a private app access token is still valid and supported. HubSpot hasn’t published a sunset date for private apps, and they remain the recommended path when you need SDK flexibility or a language other than Node
(https://developers.hubspot.com/docs/apps/legacy-apps/private-apps/overview )
Subscribing to the changelog is the best way to catch deprecation notices before they impact you.
If the only reason to migrate is concern over long-term support, I’d suggest monitoring HubSpot’s updates but keeping your Python integration running under the private app for now.
Projects will likely gain features over time, but at present they’re focused on hosted JS extensions, not general-purpose SDK use. If your real challenge is keeping those objects consistent across HubSpot and another system, Stacksync handles the two-way mapping automatically in real time, so you don’t have to recode workflows when HubSpot shifts its developer platform.
Did my answer help? Please mark it as a solution to help others find it too.
 | Ruben Burdin HubSpot Advisor Founder @ Stacksync Real-Time Data Sync between any CRM and Database |
 | |
Hi @JerikaNguyen , you’re right that the new HubSpot Projects feature only supports Node.js/JavaScript today. There’s no official option to initialize a Python-based project.
The SDKs for Python, Ruby, PHP, etc. remain fully usable with private apps (now labeled “legacy apps”), but the “projects” environment is a different execution layer that HubSpot manages, so it enforces JavaScript runtimes only (https://knowledge.hubspot.com/help-and-resources/how-to-use-the-hubspot-projects-tool )
If your flow is just syncing Contacts, Companies, and Associations, a private app access token is still valid and supported. HubSpot hasn’t published a sunset date for private apps, and they remain the recommended path when you need SDK flexibility or a language other than Node
(https://developers.hubspot.com/docs/apps/legacy-apps/private-apps/overview )
Subscribing to the changelog is the best way to catch deprecation notices before they impact you.
If the only reason to migrate is concern over long-term support, I’d suggest monitoring HubSpot’s updates but keeping your Python integration running under the private app for now.
Projects will likely gain features over time, but at present they’re focused on hosted JS extensions, not general-purpose SDK use. If your real challenge is keeping those objects consistent across HubSpot and another system, Stacksync handles the two-way mapping automatically in real time, so you don’t have to recode workflows when HubSpot shifts its developer platform.
Did my answer help? Please mark it as a solution to help others find it too.
| | Ruben Burdin HubSpot Advisor Founder @ Stacksync Real-Time Data Sync between any CRM and Database |
| | |
Hi, @JerikaNguyen 👋 I don't think you are missing an option. As you noted, the documentation only offers JS options — Create an App. If you are using a different document, let me know, and I'll dig a bit more for us. — Jaycee
Hey, @JerikaNguyen the best place to stay on top of changes is to subscribe to the changelog. Upcoming features, as well as breaking changes and sunsets, are all announced there first. — Jaycee
