Understanding IntegrationHub Usage and Best Practices for OptimizationSummary<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } This article explains how IntegrationHub transaction usage is calculated within ServiceNow, where to find relevant data, and outlines best practices for tracking and optimizing transaction consumption. It also covers how to interpret usage when flows are built in the global scope and provides links to relevant dashboards and documentation. Overview of IntegrationHub Usage Calculation IntegrationHub usage can be monitored using the IntegrationHub Usage Dashboard, which draws data from the ua_ih_usage table. Each transaction is logged with key details such as: Spoke ID and NameProtocol Used (e.g., REST)Scope/Application from where the flow was executed When flows or actions are created under the global scope, the spoke ID and name are recorded as “global”. In such cases, it becomes difficult to determine the originating application, which complicates tracking and optimization efforts. Best Practices for Managing IH Usage To effectively track and manage IntegrationHub transaction consumption: Avoid using the global scope for flows. Always build flows and actions within a specific scoped application to enable accurate attribution and easier tracking of usage by spoke.Leverage filters on the IntegrationHub Usage Dashboard to identify which spokes or flows are generating the highest number of transactions.For transactions listed under the "global" spoke, click the info (i) icon on individual records to view the artifact name. This helps trace the associated action in Flow Designer and understand its contribution to the transaction count. Optimization Tips To reduce transaction volume and avoid unnecessary usage: Identify and revise jobs that run too frequently (e.g., every few seconds/minutes).Ensure flows only trigger when specific, relevant conditions are met.Check for actions or business rules that may cause redundant updates, indirectly leading to excessive integration calls.Where possible, delay non-urgent integration tasks to low-usage periods. Additional Resources IntegrationHub Subscription UsageIntegrationHub Usage DashboardUnderstanding IH Transaction ReportsVideo: What Is Consuming My IntegrationHub Transactions? Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } N/A