Now Advisory · Glossary · 2026 edition
ServiceNow Integration Hub Transactions Definition
A buyer side ServiceNow Integration Hub transactions definition, what a transaction is, how ServiceNow meters it, and why this quiet line moves a renewal.
DefinitionServiceNow Integration Hub transactions definition
The plain ServiceNow Integration Hub transactions definition is this: a transaction is one chargeable execution of an integration action, such as an outbound API call, a data lookup, or a spoke step run by a flow. ServiceNow meters Integration Hub by counting these transactions against an annual allowance, so the cost of automation is driven by how often your flows run, not by how many people are licensed.
On the buyer side this matters because Integration Hub transactions are one of the quietest lines on a renewal. They accumulate in the background as automation scales, and the consumption only becomes visible when the allowance is breached. This page sets out what the unit is, how it is metered, and where the commercial exposure sits, with benchmark data from real enterprise renewals. For the full picture, read our pillar on ServiceNow Integration Hub licensing.
How it is meteredWhat counts as a transaction
A transaction is logged each time a flow executes an integration step that reaches outside the platform or runs a metered spoke. Simple internal flow logic is usually free, but the moment a flow calls a third party system, pushes a record, or triggers a spoke action, the meter increments. High volume integrations, such as a CMDB sync or an HR data feed, can generate hundreds of thousands of transactions a month on their own.
Commercial implicationsWhy the transaction line moves a renewal
Integration Hub allowances are sold in packs, and once consumption passes the included volume the additional transactions are billed as overage or drawn from a top up. Based on benchmark observations, enterprises that automate aggressively routinely exceed their first allowance within twelve to eighteen months, and the top up rate is almost always less favourable than the rate negotiated at the original deal.
The buyer side protections are straightforward. Forecast transaction volume against your automation roadmap before renewal, negotiate the allowance to match realistic growth rather than current usage, and secure a pre priced top up rate so a busy quarter does not convert into an uncapped charge. These mechanics sit alongside the wider commercial model covered in our guide to ServiceNow transaction based licensing and the negotiation playbook in Integration Hub pricing and negotiation.
In contextWhere it sits in your estate
Integration Hub transactions belong to the same family of metered, consumption driven lines that now define a ServiceNow renewal. Treat them the way you would treat any usage based cost: measure, forecast, and cap. For how these units interact with the rest of your subscription, start with the broader view in our ServiceNow licensing guide. Figures here are typical negotiated ranges based on benchmark observations, not official list prices.
FAQFrequently asked questions
What is a ServiceNow Integration Hub transaction?
A transaction is one chargeable execution of an integration action, such as an outbound API call, a data lookup, or a spoke step run by a flow. ServiceNow meters Integration Hub by counting these executions against an annual allowance, so cost is driven by how often flows run rather than by user count.
Do internal flows consume transactions?
Simple internal flow logic is usually free. The meter increments when a flow reaches outside the platform or runs a metered spoke, for example calling a third party system, pushing a record, or triggering a spoke action.
What happens when the transaction allowance is exceeded?
Consumption above the included volume is billed as overage or drawn from a top up, and the top up rate is usually less favourable than the rate set at the original deal. A pre priced top up rate negotiated at renewal is the key buyer side protection.
Are these Integration Hub figures official prices?
No. All ranges are typical negotiated figures based on benchmark observations across real enterprise renewals, used as internal leverage rather than published as official list prices.