The XOPS Spoke for ServiceNow is an integration that enables streamlined interactions between ServiceNow and the XOPS platform. It abstracts the complexity of API interactions by providing pre-built actions within the ServiceNow Flow Designer, allowing developers to automate and manage processes related to interacting with XOPS. This spoke allows ServiceNow developers to create, retrieve, update, and manage runbooks and employee records without having to write custom scripts or handle raw API requests. It includes automated, custom-built flows that can be dynamically triggered based on customer-specific requirements.
The integration covers key functionalities like creating runbooks, managing employee records, and querying the status of inventory items. The spoke also ensures robust handling of API responses, with clear exception handling and descriptive error messaging. By simplifying complex processes into easy-to-use actions, the XOPS spoke enhances developer productivity, reduces errors, and ensures that processes are aligned with the ServiceNow platform.
This version of the XOPS ServiceNow Spoke enables integration between the XOPS platform and ServiceNow.
The spoke provides:
Deploy Device workflows
Recover Device workflows
Replace Device workflows
Webhook-based synchronization
Inventory synchronization
Runbook lifecycle tracking
Incident creation and resiliency handling
Error code mapping
Heartbeat monitoring
Service request orchestration
New Features
- Spoke keep-alive with XOPS. A scheduled job registers the spoke with XOPS and sends a regular heartbeat, so XOPS can tell when an instance's integration stops responding.
- If XOPS no longer recognizes the instance, the spoke registers again automatically.
- Temporary server errors are retried with backoff.
- Each run is logged so an administrator can confirm it ran.
- Onboarding Runbook Validator. A new catalog item starts XOPS onboarding validation from a requested item (RITM).
- The dispatch rule runs only for that catalog item.
- The provisioning instance is checked before any authentication call.
- A failed dispatch is recorded with its failure code, status and trace ID on the instance, instead of failing silently.
Bug Fixes
- Replace a Device and Recover a Device now wait for the service request to exist before looking it up, and match on its record ID. A fast-arriving event can no longer leave the flow without its request.
- Webhook-delivered device requests create their RITM reliably. The event type is taken from the XOPS event record when the delivery itself doesn't include it.
- Event enrichment no longer acts on an event with an empty event ID.
- Request suspended and closed status updates from XOPS now set the request's current status, so the matching suspended or closed flows run.
- Support API token requests now include the required audience, so Support API calls authenticate.
- Create / Update Support Ticket script-step inputs again match what the flows pass.
- Support ticket write-back only updates incidents linked to that ticket.
- XOPS Webhook DLQ: the two calculated columns (Retryable, Next action) are display-read-only on Australia while staying read-only on Yokohama and Zurich.
- Five leftover log-parameter records from an earlier version are removed on upgrade.
API Keys from the XOPS Experience Center
Other Requirements:XOPS Automation Platform License