Notifications
Clear all
Topic starter
12/06/2026 12:45 am
TL;DR: HubSpot’s app marketplace can expand workflow reach across CRM, support, collaboration, and analytics, but the article also shows how quickly third-party integrations multiply access and oversight burden for IT teams, according to Zluri. The underlying issue is governance drift: more apps mean more credentials, more permissions, and more lifecycle work than most identity programmes are structured to absorb.
NHIMG editorial — based on content published by Zluri: 10 best applications for IT teams in the HubSpot App Store
By the numbers:
- The platform connects directly with 300+ most commonly used SaaS apps across hundreds of categories, and this list keeps increasing monthly.
Questions worth separating out
Q: How should security teams govern third-party SaaS app integrations in CRM platforms?
A: Treat each integration as a delegated identity relationship, not a simple plugin.
Q: Why do SaaS marketplaces create identity governance risk?
A: Because each new app can add credentials, permissions, and data access that sit outside normal account reviews.
Q: What breaks when app offboarding is not part of integration governance?
A: Inactive apps keep their access longer than the business need that justified them, which leaves valid credentials, stale permissions, and unresolved data connections in place.
Practitioner guidance
- Map every HubSpot integration to a named owner Require a business owner and a technical owner for each connected app, including the approval path, purpose, and offboarding trigger.
- Review delegated credentials on a fixed cadence Track OAuth grants, API tokens, and service credentials separately from user accounts, then review them on a scheduled cadence to catch abandoned access and over-scoped permissions.
- Tie app discovery to access review Use SaaS discovery data to reconcile what is installed against what is actually used, then remove integrations that are inactive, redundant, or no longer tied to a business workflow.
What's in the full article
Zluri's full research covers the operational detail this post intentionally leaves for the source:
- Step-by-step descriptions of each HubSpot app option and the specific workflows it supports
- Product-level feature lists for discovery, license management, compliance checks, and integrations
- Practical examples of how the listed apps map to day-to-day IT operations and SaaS administration
- The source article's full app-by-app catalogue for teams evaluating HubSpot ecosystem fit
👉 Read Zluri's guide to the best HubSpot App Store apps for IT teams →
HubSpot app marketplace sprawl: what it means for IAM teams?
Explore further
12/06/2026 10:12 am
Marketplace sprawl is an identity governance problem before it is a productivity problem. The article frames HubSpot integrations as a way to extend platform value, but the governance reality is that every added app creates another access path, another ownership question, and another lifecycle burden. That is classic SaaS governance drift, where the inventory of connected tools grows faster than the organisation’s ability to review them. Practitioners should treat app marketplace growth as an access-management workload, not a feature catalogue.
A few things that frame the scale:
- 80% of identity breaches involved compromised non-human identities such as service accounts and API keys, according to Ultimate Guide to NHIs.
- Only 20% have formal processes for offboarding and revoking API keys, and even fewer have procedures for rotating them.
A question worth separating out:
Q: What should IAM teams measure in a growing app marketplace?
A: They should measure ownership coverage, credential age, unused integration count, and the gap between installed apps and actively used apps. Those signals show whether governance is keeping pace with expansion or whether the environment is accumulating hidden access paths that will be hard to unwind later.
👉 Read our full editorial: HubSpot app marketplace sprawl is a governance problem for IT teams
