By MD Jehad H.·September 8, 2026·4 min read·Operator playbook

HubSpot is phasing out private apps: what to do

Drafted through my n8n + AI pipeline, edited by me.

Private apps are the two-minute shortcut most small businesses use to connect HubSpot to n8n, Zapier, or a custom script: open Settings, click create, copy an API key, and start building. HubSpot is closing that shortcut. Starting September 28, 2026, new HubSpot accounts lose the ability to create a legacy private app at all, and every existing account loses it on October 26.

Nothing breaks today. HubSpot has said plainly that private apps already in use keep working with no changes required. The change only blocks new ones from being created through the account UI. If you have never touched HubSpot's API and never plan to, this is a non-event. If you run automations, or you're about to add one, it's worth five minutes now.

What's changing with HubSpot private apps

The path getting shut down is the one-click route: Settings, Integrations, Private Apps, Create. HubSpot is pushing that traffic toward two replacements. Service Keys, a scoped credential you generate from Settings in a few minutes, built for simple system-to-system connections with audit logging and admin-controlled visibility, and project-based apps, built and deployed through the HubSpot CLI as part of the Developer Platform Projects framework, version 2026.09 or later.

Why the fine print matters: webhooks and setup effort

The catch is webhooks. Service Keys don't support them. If your n8n or Zapier workflow fires off a HubSpot webhook, a new deal stage, a form submission, a ticket update, a Service Key alone won't carry that connection. You'd need the full project-based app instead, which means installing the HubSpot CLI, structuring a project folder, and deploying it, a real step up from pasting a key into a settings field.

	Creatable after Oct 26, 2026	Supports webhooks	Setup effort
Legacy private app	No	Yes	One click in Settings
Service Key	Yes	No	A few minutes in Settings
Project-based app (CLI)	Yes	Yes	Requires HubSpot CLI and a deploy step

Service Keys are the fast replacement, but only a project-based app keeps webhook triggers alive.

Not sure if you use webhooks

Open the trigger step in your n8n or Zapier workflow. A trigger set to watch for a new record or fire instantly is a webhook. A trigger that polls on a schedule is not, and a Service Key will cover it fine.

Who actually needs to act now

Three groups should pay attention. Anyone opening a new HubSpot account after September 28 loses the old shortcut immediately. Anyone with an existing account who hasn't built their integration yet has until October 26. And anyone who outsources the automation build, an agency, a freelancer, a hosted n8n instance someone else manages, should ask now whether that build will use a Service Key or a full project app, because the answer changes what happens if a webhook-based workflow is part of the plan.

Will my current HubSpot integration stop working?

No. Existing legacy private apps keep running with no changes. The shutdown only affects creating new ones.

What if I need webhooks and don't want to touch the CLI?

There isn't a no-code webhook alternative yet. A project-based app built through the HubSpot CLI is currently the only path that supports both authentication and webhooks together.

If you've got a HubSpot integration in the works, or you're not sure which of these paths your automation actually needs, send me what you're connecting and I'll help you figure out whether a Service Key covers it or you need the full project build.

Building something this should run inside?

Book a systems call

Keep reading