Skip to content
Book a build

How do I audit connected apps and private apps in HubSpot?

To audit connected apps and private apps in HubSpot, list every installed app from Connected Apps and every legacy private app, then record each one's owner, the access it holds and what it writes. Check the apps flagged as needing attention, review private app call logs, and confirm each integration still has a business owner before you disconnect anything.

On this page

What HubSpot supports natively

WhereWhat it showsLimit
Settings > Integrations > Connected AppsInstalled apps; each app’s owner, installer, install date and the features it’s authorized forNo list of which fields an app writes
“Needs your attention”Expired, disconnected and erroring appsStatus shows for some HubSpot-built apps only
Connections insightsActivity, record and automation insights, API call usage across private appsUsage isn’t clearly split per app
Development > Legacy apps (private apps)Each app’s scopes and a Logs tab of API callsLogs export covers the past 30 days; successful call bodies aren’t stored
Security activity exportIntegration installs, among other security eventsLast year; Super Admins only

How to audit connected apps and private apps

  1. Build the inventory. Every connected app and legacy private app, with owner, install date and what it’s for.
  2. Find a business owner for each. Not just who installed it, but who would notice if it stopped.
  3. Record access. For connected apps, the features authorized on the overview page. For private apps, the scopes on the app’s details page.
  4. Check health. Apps under “Needs your attention”, and recent error responses in private app logs.
  5. Record what each one writes. Which objects and properties an integration creates or updates. This is the part HubSpot doesn’t show; ask the owner or check property history sources on a few records.
  6. Look for overlap. Two apps syncing the same data is a common source of values flipping back and forth.
  7. Retire carefully. Disconnect only after the owner confirms, and note the date in case something breaks.

Common mistakes

  • Disconnecting an app because nobody on the current team recognizes it.
  • Leaving apps owned by people who have left.
  • Granting broad private app scopes “for now”.

When to run it

Run an integration audit when values change for no visible reason, after an admin or agency leaves, and before a migration. It also belongs in every annual portal audit.

Where Jetstack AI fits

Jetstack AI’s Portal Audit does the inventory and health checks for you in minutes. Its Integration Health block in the General section measures daily API usage against your limit across private apps and, with the Chrome extension, reads the full connected apps list, flags every app reporting errors or not reporting status at all, calculates the error rate, and shows which legacy apps still need migrating. It also scores import success rates and the most common import errors, counts the sources creating your contacts (API, import, form, integration and manual), and checks how close each object is to its record limit. For overlap on the automation side, the Workflow Health block flags properties written by two or more active workflows. The audit only reads the portal, so which properties each app writes stays the step 5 conversation with the app’s owner, and you retire apps with the evidence in front of you. See the General data points.

Sources

Checked October 30, 2026. HubSpot changes its products often; tell us at team@jetstack.ai if something here is out of date.

Portal audits

See what needs work before you change it.

A read-only Portal Audit and Workflow Audit score the portal, trace dependencies and turn findings into a branded report.

Explore Portal Audit

Portal audits

Related questions.

How do I audit connected apps and private apps in HubSpot?

To audit connected apps and private apps in HubSpot, list every installed app from Connected Apps and every legacy private app, then record each one's owner, the access it holds and what it writes. Check the apps flagged as needing attention, review private app call logs, and confirm each integration still has a business owner before you disconnect anything.

Who becomes the owner of a connected app?

The person who installs it, by default. Super Admins or users with App Marketplace access can reassign the owner, which matters when the installer leaves.

Do private apps each get their own API limit?

No. Private apps draw on the account's subscription API limits and share one daily pool, so one busy app can affect the others.