Platform & Integration
Integration Hub
Zero-code spoke generation. Connect ServiceNow to any system in minutes, not months.
What Integration Hub covers.
Out-of-the-Box Spokes
Prebuilt connectors for SAP, Salesforce, Oracle, Workday — instant enterprise integration.
- Instant setup
- Enterprise apps
Spoke Generator
No-code spoke creation from OpenAPI specs. GenAI-powered development. Custom connectors in hours.
- No-code creation
- GenAI-powered
- OpenAPI support
Flow Templates
Starter flows with built-in integrations. Accelerated automation development with pre-configured workflows.
- Pre-built flows
- Accelerated dev
- Ready to use
Stream Connect
Apache Kafka integration at scale. Real-time event streaming and enterprise messaging.
- Kafka integration
- Real-time streaming
- Scalable messaging
Remote Tables
Zero-copy data integration. Access external data without importing or storing it.
- Zero-copy
- Real-time access
- No storage needed
Four phases. You see working configuration in every one.
We don't publish a week count here — the honest answer depends on your instance, your data, and how many systems are in scope. You get a specific timeline in the written plan after scoping.
Discover
- Integration audit & system inventory
- Priority mapping & dependency analysis
- Security & auth requirements
Connect
- Spoke configuration & activation
- Flow template setup & customization
- Core integration deployment
Automate
- Custom spoke development
- Advanced workflow automation
- End-to-end testing & validation
Scale
- Performance tuning & optimization
- Team training & documentation
- Expansion roadmap & governance
Nobody owns the failure path.
Integrations are straightforward to build and hard to operate. The build gets attention; what happens when the downstream system is down, returns a partial response, or rejects a payload usually does not. The result is a flow that works in testing and, in production, silently drops records or retries into a duplicate. The other surprise is commercial: IntegrationHub is licensed by transaction volume, and a chatty integration designed without that in mind produces a bill nobody forecast.
Tell us where you are- What happens when the other system is unavailable?
- Retry with backoff, queue for later, or fail loudly to a human — per integration, decided deliberately. The default of retrying forever is how duplicates get created.
- IntegrationHub spoke or custom REST?
- Spokes are faster to build and consume licensed transactions. Custom scripted integrations cost engineering time and do not. For high-volume flows the arithmetic often favours custom, and it is worth doing that arithmetic before building.
- Who gets paged when an integration breaks at 2am?
- If the answer is nobody, the integration is not production-ready regardless of how well it works. Monitoring and ownership are part of the build, not a follow-up phase.
- Configuration documentationWhat was built, why, and where the decisions are recorded.
- Admin and runbook trainingFor the people who will own it after go-live.
- Update-set and repo historyA traceable record rather than an undocumented instance.
- A named escalation pathThe same engineers, not a ticket queue.
A library of pre-built connectors plus tooling to build your own, so integrations are configured rather than hand-coded. Two things to settle before building: what happens when the far system is down — retry, queue, or fail to a human — and the commercial shape, because IntegrationHub is licensed by transaction volume and a chatty integration designed without that in mind produces a bill nobody forecast.
Want this on your instance?
Tell us where you are today — greenfield, mid-implementation, or inheriting someone else's build. You'll have a written plan inside two working days.