IntegrationHub is ServiceNow's integration platform that lets you connect your ServiceNow instance to external systems like Office 365, Slack, AWS, or custom APIs without writing custom code. IT teams use it to automate tasks that span multiple systems - like creating a Slack channel when a major incident opens, or provisioning AWS resources when someone requests cloud access through the service catalog. Instead of building point-to-point integrations or writing scripts, you drag and drop pre-built connectors called spokes in Flow Designer. Once IntegrationHub is active, your flows can reach beyond ServiceNow to update external databases, send notifications through messaging platforms, sync user data with HR systems, or trigger actions in cloud platforms. The platform handles authentication, error recovery, and logging automatically. This turns ServiceNow into a true automation hub rather than an isolated ticketing system, letting you build end-to-end processes that work across your entire technology stack.
Key Capabilities
Pre-built Spokes for Popular Systems
Over 300 ready-made connectors for systems like Office 365, Slack, Salesforce, AWS, and Jira. Each spoke includes common actions like creating records, sending messages, or retrieving data. This eliminates the need to research APIs or write integration code from scratch.
Visual Flow Building
Build integrations by dragging steps into Flow Designer rather than coding. Add REST calls, handle responses, manage errors, and route data between systems using the same interface you use for internal ServiceNow flows. Non-developers can create and modify integrations with proper training.
Secure Credential Management
Store API keys, certificates, and connection details in encrypted credential records. Connection aliases let you switch between development, test, and production environments without rebuilding flows. Credentials are never exposed in flow logic or logs.
Error Handling and Retry Logic
Built-in error handling catches failed API calls, network timeouts, and authentication issues. Configure automatic retries with exponential backoff, route errors to specific handlers, or fail gracefully with notifications. This prevents small integration hiccups from breaking entire processes.
REST and SOAP Web Services
Generic REST and SOAP steps let you integrate with any system that has a web API, even if there's no pre-built spoke. Import WSDL files for SOAP services or configure REST calls with custom headers, authentication, and payload formatting.
Subflow Reusability
Package common integration patterns into reusable subflows that other flows can call. Build a standard error notification subflow once, then reference it across multiple integrations. This ensures consistency and reduces maintenance when connection details change.
Enterprise Monitoring and Logging
Track integration performance, success rates, and error patterns through dedicated dashboards. Detailed execution logs show exactly what data was sent and received for troubleshooting. Set up alerts when integrations fail or performance degrades.
How It Works
An integration typically starts when a ServiceNow record changes or someone requests something through the service portal, triggering a flow that includes IntegrationHub actions. The flow retrieves stored credentials, makes authenticated calls to external systems using spokes or REST steps, and processes the responses. If an external call fails, error handling logic can retry the operation, log the issue, or route to alternative steps. The flow continues with the received data, updating ServiceNow records or triggering additional external actions until the process completes.
Who Uses It and How
Large hospital network
When a new employee starts, HR creates their record in Workday, which triggers a ServiceNow flow through IntegrationHub. The flow automatically provisions their Active Directory account, adds them to appropriate Office 365 groups, creates their Epic healthcare system access, and generates their ID badge request.
Result: New employee onboarding that previously took 3-4 days now completes in under an hour.
Global manufacturing company
When production equipment generates critical alerts in their IoT platform, IntegrationHub pulls the alert data into ServiceNow, creates a high-priority incident, pages the on-call technician through PagerDuty, and automatically orders replacement parts through their SAP system if the equipment model indicates common failure patterns.
Result: Equipment downtime reduced by 40% through faster response and proactive parts ordering.
Financial services firm
Security incidents detected by their SIEM tool automatically create ServiceNow security incidents through IntegrationHub, which then isolates affected user accounts in Active Directory, revokes their Okta sessions, and creates Jira tickets for the development team if the incident involves application vulnerabilities.
Result: Security response time improved from 45 minutes to under 5 minutes for account isolation.
University IT department
When students register for courses that require software access, IntegrationHub flows automatically provision their accounts in learning management systems, grant access to specialized software through campus licensing servers, and add them to course-specific Slack channels or Microsoft Teams.
Result: Student software access requests that previously required manual processing now complete instantly during registration.
Sourdough: ServiceNow Monitoring and Analytics
A Chrome extension for ServiceNow Admins and Developers with essential tools, analytics, graphs and monitoring features.
Free to install. Pro $5/month after a 14-day no-card trial.
Pro requires the ServiceNow admin role. Upgrade inside the extension.
Implementation: What to Know
Plan for your integration team to include someone who understands the target systems' APIs and authentication requirements, not just ServiceNow developers. A typical rollout takes 2-3 months to establish patterns, build initial integrations, and train the team. Start by identifying your most painful manual processes that cross system boundaries - these usually provide the clearest ROI and help build organizational support. Most implementations stall when teams underestimate the time needed to understand external system APIs and coordinate with other system owners for credential access and testing.
Common Use Cases
Incident Response Across Security Tools
When a security incident is created in ServiceNow, the system automatically pulls additional context from threat intelligence platforms, isolates affected assets through endpoint management tools, and creates communication channels in Slack or Microsoft Teams. Security analysts get a complete picture without manually checking multiple consoles.
Employee Lifecycle Management
HR systems trigger ServiceNow flows for new hires, transfers, and terminations. IntegrationHub handles account provisioning across Active Directory, Office 365, badge systems, and business applications. Terminations automatically revoke access, transfer file ownership, and update distribution lists across all connected systems.
Cloud Resource Provisioning
Developers request AWS or Azure resources through ServiceNow's service catalog. IntegrationHub flows validate the request against company policies, provision the infrastructure through cloud APIs, configure monitoring and backup policies, and update the CMDB with the new resources and their relationships.
Customer Support Escalations
High-priority support tickets in external systems like Salesforce or Zendesk automatically create corresponding incidents in ServiceNow when they meet escalation criteria. IntegrationHub keeps both systems synchronized, so updates in either platform appear in the other, maintaining a single source of truth for internal teams.
Compliance and Audit Reporting
Monthly compliance reports pull data from multiple systems through IntegrationHub - user access from Active Directory, security events from SIEM tools, change records from ServiceNow, and application logs from various business systems. The consolidated report automatically generates and routes to compliance officers.
Key Tables
sys_hub_flow_inputssys_hub_action_instanceconnection_aliassys_auth_profile_basicsys_hub_action_type_baseBest Practices
- ✓Build and test integrations in a sub-production instance first - external system APIs often behave differently than their documentation suggests, and you don't want to discover this in production.
- ✓Create standardized connection aliases for each environment (dev, test, prod) so flows can be promoted without modification - this prevents accidentally calling production APIs from test flows.
- ✓Set up monitoring dashboards for your most critical integrations before you need them - when an integration fails at 2 AM, you want clear visibility into what broke and why.
- ✓Document which external system owners to contact for each integration, including their escalation procedures - API credentials expire and systems get upgraded without warning.
- ✓Use subflows for common patterns like error handling and logging - this ensures consistency across integrations and makes updates much easier when you need to change how errors are handled.
- ✓Test your error handling paths regularly by temporarily breaking connections - integrations that work perfectly for months can fail catastrophically when they encounter their first real error.
Common Pitfalls
Hardcoding external system URLs or credentials directly in flow steps instead of using connection aliases
Always use connection aliases and credential records. This lets you promote flows between instances and update connection details without modifying flow logic.
Not implementing proper error handling for external API calls, assuming they will always succeed
Every external integration step should have error handling that can deal with timeouts, authentication failures, and unexpected responses. Plan for external systems to be unavailable.
Building overly complex flows that try to handle every possible scenario in a single integration
Break complex integrations into smaller, focused flows that handle specific use cases. Use subflows for common operations and chain flows together when needed.
Insufficient testing with the external system's actual API responses and error conditions
Test with real API responses, not just the happy path. Ask external system owners about common error scenarios and rate limiting policies before building your integration.
Not planning for credential rotation and external system maintenance windows
Document credential expiration dates and external system maintenance schedules. Build alerts that warn you before credentials expire and plan alternative workflows for maintenance periods.
Frequently Asked Questions
Is IntegrationHub included in my ServiceNow license?
It depends on your license tier. Standard tier includes basic REST/SOAP steps and a few common spokes. Professional adds more spokes and advanced error handling. Enterprise includes all spokes, advanced monitoring, and higher transaction limits. Check your license details or ask your ServiceNow account manager.
What's the difference between a spoke and a REST step?
Spokes are pre-built connectors with ready-made actions for popular systems like Slack or AWS - you just configure them with your credentials. REST steps are generic and let you call any web API, but you need to configure the URL, headers, authentication, and payload formatting yourself.
How do I handle API rate limits from external systems?
Use the built-in retry logic with exponential backoff to automatically handle temporary rate limiting. For systems with strict limits, consider batching operations, using subflows to queue requests, or implementing custom throttling logic in your flows.
Can I test integrations without affecting production external systems?
Yes, use connection aliases to point your test instance flows at sandbox or development versions of external systems. Most major platforms provide test environments specifically for integration development. Always test credential rotation and error scenarios in non-production first.
What happens if an external system is down when my flow runs?
The flow will fail unless you have error handling configured. Best practice is to add error handling that can retry the operation, log the failure, send notifications, or route to alternative steps. You can also set up flows to retry failed operations when the external system comes back online.
How do I monitor integration performance and failures?
IntegrationHub provides execution logs and performance metrics through the Flow Designer interface. Enterprise licenses include dedicated integration dashboards. Set up email or Slack notifications for integration failures, and regularly review execution logs to identify patterns or performance issues.
Do I need special permissions to build integrations?
Yes, you need the action_designer role to create and modify integrations, plus appropriate permissions on any ServiceNow tables your flows will update. You'll also need API access and credentials for the external systems you're integrating with.
Related Modules
Related Articles
Test Your Knowledge
Quick 3-question quiz — see how your ServiceNow skills stack up.
A list view on a table with millions of records is slow. Best fix?
Select an answer to continue