Docs · Docs
ServiceNow + Closure
Complement ServiceNow — keep Now authoritative; run governed Experiences and hybrid journeys on Closure.
Value on top
| Closure | ServiceNow |
|---|---|
| Branded Experiences for requesters / partners / citizens | Tables, catalog, CMDB remain SoR |
| Hybrid workflows (form → agent → HITL) | Seal writes records back |
| Import catalog → Workflow Graph | Operators keep Now as system of record |
| IDE authoring via Platform MCP | App Engine / Flow stay Now-native |
| Pre-SoR governance loops | Otto + AI Control Tower govern in-Now AI |
Otto adjacency (important)
ServiceNow Otto is the unified AI experience for work on the Now Platform. Closure sits beside Otto and AI Control Tower: Experiences and hybrid journeys that complete into Now — especially branded partner/customer surfaces and multi-SoR paths — so Now receives better structured work.
Typical pattern
- Connect ServiceNow in Closure Integrations (vaulted credentials).
- Import a catalog item → Closure workflow (depth varies by connector status).
- Run Experience journeys; seal outcomes into SN records.
- Optional: triggers start Closure runs from SN events (roadmap per adapter).
Pitch governed Experiences and agents that land where work already lives — ServiceNow stays the system of record; Otto stays the in-Now AI surface.