ServiceNow IntegrationHub Licensing Guide 2026: Tiers, Spokes & Transaction Limits

What Is ServiceNow IntegrationHub?

ServiceNow IntegrationHub is the native integration capability built into the Now Platform. It enables organisations to create, manage, and execute integrations between ServiceNow and external applications — from cloud services and SaaS platforms to on-premise ERP systems, identity providers, monitoring tools, and HR platforms — without requiring custom scripted integration development for every connection.

IntegrationHub operates through a spoke model. Spokes are pre-built integration modules that handle the authentication, data mapping, and API call structures for specific external applications. A ServiceNow instance with IntegrationHub licensed can deploy spokes to integrate with Jira, Salesforce, Workday, SAP, Microsoft Teams, AWS, Azure Active Directory, ServiceNow HRSD, and hundreds of other platforms, eliminating much of the custom development work that integration would otherwise require.

The platform also integrates with Flow Designer and Orchestration, allowing integrations to be embedded directly within automated workflows. An HRSD lifecycle event that triggers a Workday record update, or an ITSM incident that automatically creates a Jira ticket and pages an engineer via Microsoft Teams, are examples of IntegrationHub-powered automation that many enterprises rely on daily.

However, IntegrationHub is not free. It is a separately licensed component with a transaction-based pricing model, four subscription tiers, and distinct spoke availability at each tier. Understanding this structure — and modelling transaction volume accurately — is essential to avoiding unexpected cost escalations and service disruptions caused by transaction limit overages.

The Four IntegrationHub Subscription Tiers

IntegrationHub is available at four subscription levels. Each tier determines both the volume of transactions available per year and the set of pre-built spoke packs accessible to the organisation. Moving to a higher tier expands both capacity and capability, but also increases cost proportionally.

Starter — 1 Million Transactions Per Year

The Starter tier provides access to 1 million IntegrationHub transactions per year at no additional cost above the base ServiceNow platform subscription. It is included as part of the standard Now Platform licence. The Starter tier provides access to core integration framework capabilities — including the ability to build custom spokes from scratch — and access to a subset of pre-built spoke packs covering fundamental developer and IT operations use cases.

Organisations on Starter can build REST-based and SOAP-based integrations using the spoke development framework, but they do not have access to the full pre-built spoke library. The 1 million annual transaction limit is sufficient for light integration use — simple bi-directional data syncs at moderate frequency, notification workflows, or basic approval chain automations involving external systems — but it is easily exceeded in enterprise environments with multiple active integrations running at high frequency.

Standard — 3 Million Transactions Per Year

The Standard tier provides 3 million annual transactions and opens access to the Standard spoke pack, which covers developer operations and IT automation use cases. Standard includes spokes for key DevOps tools, version control platforms, and IT operations workflows, enabling organisations to automate CI/CD pipeline notifications, infrastructure provisioning workflows, and change management integrations with deployment tools.

The Standard tier is appropriate for organisations whose primary IntegrationHub use cases are confined to IT operations and DevOps automation, where transaction volumes are moderate and the integration landscape is relatively contained. Organisations with active HRSD, CSM, or ERP integrations will typically outgrow Standard's 3 million transaction limit.

Professional — Variable Transaction Pack

The Professional tier unlocks the full Professional spoke pack, which is the tier where most enterprise organisations find their integration requirements adequately covered. Professional includes spokes for IT operations automation, expanded developer toolchains, and core HR and ITSM integrations with platforms including Workday, key HRIS systems, and CMDB data sources.

Transaction volume at Professional is typically negotiated as a custom pack rather than a fixed published tier. Organisations should model their actual integration transaction volumes before entering commercial discussions, as the Professional tier's transaction capacity is a key negotiation variable. IntegrationHub transactions at Professional scale quickly in environments with high-frequency HR data synchronisation, real-time monitoring alert routing, or complex approval workflows involving multiple external system calls.

Enterprise — 6 Million Transactions Per Year

The Enterprise tier provides 6 million annual transactions and unlocks the full Enterprise spoke pack, which includes HR, CRM, ERP, and supply chain integration spokes. Enterprise spokes cover platforms such as Workday, SAP SuccessFactors, Oracle HCM, Salesforce, and major ERP systems, making Enterprise the necessary tier for organisations with complex multi-system integration landscapes spanning HR, finance, and operations.

For global enterprises with ServiceNow deployed across ITSM, HRSD, CSM, and ITAM, operating with real-time integrations to Workday for HR data, SAP for financial workflows, Salesforce for customer case escalations, and cloud monitoring tools for infrastructure event management, the Enterprise tier's 6 million transaction limit is likely still insufficient and will require supplemental transaction packs. Accurate transaction volume modelling is not optional at this scale.

How IntegrationHub Transactions Are Counted

An IntegrationHub transaction is defined as any outbound call originating from IntegrationHub, Flow Designer, Remote Tables, or Orchestration that results in an external API call. This definition is broader than many organisations initially anticipate, and understanding exactly what counts as a transaction is critical to accurate consumption modelling.

Each outbound API call to an external system counts as one transaction. If a single ServiceNow workflow generates multiple external API calls — for example, a request that authenticates with an external system, retrieves data, updates a record, and sends a notification — each individual outbound call may count as a separate transaction depending on how the spoke and workflow are configured. A complex multi-step workflow involving six external system interactions counts as six transactions, not one.

High-frequency data synchronisation integrations are the most significant source of unexpected transaction consumption. An HR data feed from Workday that syncs employee records every 15 minutes, for an organisation with 20,000 employees, processes approximately 1,900 sync cycles per year. If each sync cycle involves even moderate numbers of individual API calls per employee record change, annual transaction consumption can reach into the tens of millions.

The practical implication is that organisations must model transactions at the individual API call level, not at the integration or workflow level. This requires a detailed technical assessment of each integration in scope — mapping every external system call within each workflow and estimating call frequency against expected data volumes and change rates.

Transaction Overages: The Hidden Cost Driver

When an organisation exceeds its contracted annual transaction limit, ServiceNow can either suspend the integration capability — which may cause significant operational disruption — or charge overage fees for the excess transactions. The overage rate is not published publicly and is subject to negotiation, but market experience indicates overage transactions are charged at a significant premium above the average contracted rate.

The overage risk is asymmetric and unpredictable. Transaction consumption is driven by external factors — business process volumes, frequency of HRIS changes, incident rates, and automation trigger frequency — that do not follow predictable annual patterns. A major restructuring that changes thousands of employee records, a large acquisition that triggers mass HRIS synchronisation, or a significant infrastructure event that generates thousands of monitoring alerts can all cause transaction spikes that breach annual limits within days.

Overage risk mitigation requires three elements. First, accurate transaction volume modelling across all active integrations before tier selection. Second, contractual negotiation of overage terms — specifically, an agreed overage rate below the default list rate and a grace period before overage charges apply. Third, active transaction monitoring through ServiceNow's integration usage dashboards, with alerts configured to notify the team when consumption reaches 75% of the annual limit.

Spoke Packs in Detail: What Each Tier Unlocks

Spokes are the pre-built integration modules that connect ServiceNow to specific external platforms. Each spoke handles authentication, data mapping, and API management for a particular application, reducing the development effort required to establish and maintain that integration. The spoke available at each IntegrationHub tier determines which integrations an organisation can deploy without custom development.

Core Framework Spokes (Starter)

The Starter tier provides access to the core integration framework, which allows development teams to build custom spokes for any REST or SOAP API. Pre-built spokes at this tier cover fundamental capabilities including basic HTTP action functionality, email and notification integrations, and ServiceNow-to-ServiceNow integration for multi-instance deployments.

Standard Spoke Pack

Standard unlocks spokes focused on developer and IT operations toolchains. This includes integrations with GitHub and GitLab for source code management and CI/CD pipeline notifications, Jenkins for build automation, Jira for incident and defect management, and basic cloud monitoring platforms. Standard is sufficient for organisations whose integration landscape is centred on IT operations and software delivery workflows.

Professional Spoke Pack

Professional extends the spoke library to include more sophisticated IT operations integrations and introduces HR and enterprise application connectors. Professional spokes typically include integrations with infrastructure monitoring platforms such as Dynatrace, PagerDuty, and SolarWinds, identity providers such as Okta and Azure Active Directory, and foundational connectors for major cloud platforms.

Professional also typically includes connectors for Workday and key HRIS platforms for basic employee data synchronisation — though the depth of these connectors is more limited than what Enterprise provides. Organisations with complex HR data integration requirements, bidirectional workflows, or real-time HR event triggers will need Enterprise.

Enterprise Spoke Pack

The Enterprise spoke pack is comprehensive and covers the integration landscape of most large enterprises. Enterprise spokes include full Workday HCM integration with real-time event support, SAP SuccessFactors and other major HRIS connectors, Salesforce for CRM and customer service integrations, ServiceNow Customer Service Management connectors, Oracle ERP and HCM integrations, major supply chain platforms, and expanded cloud infrastructure connectors for AWS, Azure, and GCP.

Enterprise is also the tier at which Orchestration-based integrations — complex multi-step automations involving sequential external system interactions — receive full spoke support. Organisations implementing end-to-end digital workflows that span multiple enterprise systems require Enterprise to deploy these workflows using native spoke functionality.

Relationship Between IntegrationHub and HRSD Licensing

One of the most common integration complexity scenarios arises at the intersection of IntegrationHub and HRSD licensing. HRSD's value depends on accurate, real-time employee data from the authoritative HRIS — typically Workday, SAP SuccessFactors, or Oracle HCM. Maintaining this data feed requires IntegrationHub transactions for every outbound API call that synchronises employee records, triggers lifecycle events, or confirms HR workflow completions in the external system.

A busy HRSD deployment at a 15,000-employee organisation with continuous Workday synchronisation, lifecycle event triggers, and bidirectional HR case data flows can consume 3–8 million IntegrationHub transactions annually. This consumption alone requires at least Professional tier, potentially Enterprise, and must be factored into the HRSD total cost of ownership model from the outset.

Organisations that discover mid-deployment that their HRSD integration architecture requires more IntegrationHub transactions than their contracted tier provides face a difficult commercial position: either accept service interruption when the transaction limit is breached, or purchase an emergency transaction top-up at an unfavourable price. Neither outcome is acceptable for a business-critical HR service delivery platform. The solution is to model integration transactions alongside HRSD licence requirements at the design stage, before any commercial agreements are signed.

Negotiation Strategies for IntegrationHub

IntegrationHub commercial negotiations have several characteristics that distinguish them from core platform licence negotiations.

Model Before You Negotiate

The most important preparation for an IntegrationHub negotiation is a detailed transaction volume model. This model should enumerate every integration in scope, estimate the API calls per workflow execution, estimate execution frequency, and sum to an annual transaction forecast with a 30% buffer for growth and unexpected spikes. This model is your anchor for negotiating the right tier and protecting against overage.

Negotiate Transaction Capacity Separately from Tier

IntegrationHub tier selection is not purely binary. ServiceNow will negotiate custom transaction packs above and below standard tier thresholds for organisations with accurately modelled needs. An organisation that needs Professional spokes but projects 5 million annual transactions can negotiate a custom 5 million transaction pack at Professional rather than upgrading to Enterprise. This approach avoids paying for Enterprise spoke capabilities that are not needed.

Include Overage Protection in the Contract

Negotiate explicit overage terms: a stated overage rate as a percentage premium above your average contracted rate (not an uncapped list price), a 30-day grace period before overage charges apply, and notification rights requiring ServiceNow to alert the organisation when consumption reaches 80% of the annual limit. These provisions are achievable in Q4 negotiations when ServiceNow sales teams are under fiscal year-end closing pressure.

Annual Escalation Cap

IntegrationHub subscriptions carry the same annual escalation provisions as other ServiceNow products. Without negotiation, escalation typically runs at 5–10% annually. Negotiate a 3–4% cap, documented as a hard limit in the order form. On an IntegrationHub subscription of $100,000 annually, a 3% cap versus a 7% default saves approximately $80,000 in avoidable escalation cost over a three-year term.

Align Renewal Timing with ServiceNow's Fiscal Year

ServiceNow's fiscal year ends December 31. Deals negotiated in October–December, when sales teams face maximum pressure to hit annual quota, consistently achieve better transaction pack pricing, more favourable overage terms, and deeper discounts than deals renewed in other quarters. Where IntegrationHub renewal dates do not fall in Q4, consider negotiating a short extension to align the renewal with the fiscal year-end closing window.

IntegrationHub and the Broader ServiceNow Licensing Ecosystem

IntegrationHub does not exist in isolation. It is deeply embedded in the commercial relationship between IntegrationHub transactions, Flow Designer automation, HRSD lifecycle events, ITSM orchestration, and ITAM discovery workflows. Understanding these interdependencies is essential to building an accurate total cost model for any enterprise ServiceNow deployment.

For organisations using ServiceNow ITSM with Orchestration, every orchestration action that calls an external system generates IntegrationHub transactions. For organisations using HRSD with Workday lifecycle events, every lifecycle trigger that communicates with an external HR platform generates transactions. For organisations using ITAM with automated discovery-to-CMDB workflows, discovery data enrichment calls to external CMDBs generate transactions. None of these transaction sources are always apparent from the integration design documentation — they emerge from detailed technical review of the workflow configurations.

A comprehensive IntegrationHub cost model requires engagement from both the platform architecture team (who can map all external API calls in all active workflows) and the enterprise data team (who can estimate call frequency and data volume). Organisations that complete this analysis before negotiating their IntegrationHub tier consistently avoid the overage exposure that affects those who rely on simple integration counts rather than transaction-level analysis.

One cost area that sits adjacent to IntegrationHub but is frequently conflated with it is Now Assist — ServiceNow's generative-AI capability layer. Now Assist is a premium add-on and is not included in any IntegrationHub tier, nor in any core ITSM, HRSD, CSM, or ITAM edition. It is licensed and priced separately, typically in the range of $50–$100 per fulfiller per month depending on module and negotiated volume commitment. When HRSD or ITSM modules that rely on IntegrationHub for data exchange are also licensed with Now Assist, the total cost impact includes three distinct line items: the underlying module edition, the IntegrationHub transaction tier, and the Now Assist premium add-on. Buyers who model only the module edition and overlook the IntegrationHub transaction cost and the Now Assist add-on cost routinely underestimate the total platform spend by 30–50%. True-up exposure compounds this: true-up obligations under IntegrationHub are calculated on peak transaction usage during the contract period, not average usage — meaning a single high-volume month can anchor the renewal baseline at a level significantly above the annual average. Organisations should budget all three cost layers together and negotiate Now Assist pricing in the same commercial conversation as the IntegrationHub tier to maximise bundling leverage.

Conclusion

ServiceNow IntegrationHub is a powerful integration platform, but its transaction-based licensing model introduces commercial risk that requires careful management. The four-tier structure — Starter, Standard, Professional, Enterprise — determines both spoke availability and transaction capacity, and selecting the wrong tier creates either capability gaps or unnecessary cost. Transaction counting at the individual API call level, not the workflow level, means consumption is consistently higher than initial estimates.

Overage protection, accurate transaction volume modelling, custom transaction pack negotiations, and annual escalation caps are the four commercial levers that define a well-structured IntegrationHub agreement. Organisations that invest in transaction volume analysis before tier selection, and negotiate overage protections alongside their core IntegrationHub subscription, avoid the unexpected charges that affect those who rely on initial sales estimates for volume guidance.