ServiceNow Incident Bridge

Enterprise IT runs incidents in ServiceNow while engineering runs them in its own tracker and alerting stack. Copying between the two by hand loses timestamps, breaks SLA clocks, and produces two conflicting narratives of the same outage during the exact window when clarity matters most.

• A ServiceNow integration over the Table API and Scripted REST endpoints, mapping incident, task, and CMDB records with explicit state machines rather than free-text status.
• SLA-aware state translation so a pause on the engineering side maps to the correct ServiceNow on-hold reason and the SLA clock stays defensible.
• Comment and attachment relay with author attribution preserved, plus loop suppression so a relayed comment never re-triggers the opposite direction.
• A correlation layer that attaches alert payloads and runbook links to the ServiceNow record, so first responders see engineering context without leaving their tool.

Across 1,200 simulated incidents including state flapping and concurrent edits on both sides, the bridge held state parity on every record with no comment loops, and relayed updates within a median of 1.8 seconds.