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.
The XOPS Spoke v1.7.5 application enables end-to-end automation of device lifecycle processes such as deployment, replacement, and recovery. It includes a set of custom Flow Designer actions that integrate with webhook events received from the XOPS Platform, allowing automated execution of runbooks based on the request type. The application supports dynamic flow triggering from catalog requests and maintains data consistency by mapping webhook and flow actions to backend tables including XOPS Service Requests, XOPS Service Items, and XOPS Inventory.
v1.7.5 : Bug Fixes & Enhancements
As part of version 1.7.5, we’ve delivered key improvements to enhance platform reliability, integration accuracy, and process automation. This update addresses several critical issues across flow actions, task management, event processing, and external integrations.
Flow & Integration Fixes
- Dynamic Action Type Detection: Action type is now derived from command.code for accurate flow behavior.
- UI Page Enhancements: Improved integration instructions within the configuration setup page.
- PATCH Payload Correction: Fixed incomplete payloads during PATCH requests to Observability.
- Restock PATCH 500 Error: Resolved error caused by missing item identifiers.
- 3rd Party DLM PATCH Failure: Addressed failure due to empty or malformed data in outbound calls.
RITM & Task Processing Fixes
- Suspended Status Handling: RITMs now correctly reflect “Suspended” when inventory is not available.
- Closed-Cancelled Sync: RITMs properly update on request_status_changed events.
- Duplicate Task Prevention: Fixed issue causing redundant task creation.
- Action Type Accuracy: Corrected display of action type to match runbook context (e.g., "Recover").
Event Parsing Enhancements
Standardized event processing to consistently extract employee_id and ritm_id across key events. Added schema support for both object and string formats, with field updates applied to the custom event table.
Extended Patching Support
Expanded patching logic to accept serial_number, request_id, and order_id, enabling bulk device resolution. Outbound payloads now support device group patching. Backend support required from Observability API team.
v1.7.1
- Introduced support actions to trigger flows based on webhook events from the XOPS Platform.
- Enabled flow automation to trigger runbooks based on webhook data and request type.
- Flows and actions dynamically triggered from catalog request types.
- Webhook events and automation logic are integrated with backend tables:
XOPS Service Requests, XOPS Service Items, and XOPS Inventory.
New Actions Added:
- Recover device
- Replace device
- Deploy device
- Patch a XOPS Request
- XOPS - Update Inventory
- XOPS - Update Restock Job
- XOPS - Parse Reason to RITM
- XOPS - Parse Runbook Response
- Get Task Custom Fields
- Format XOPS Notes
New Flows Added:
- XOPS Deploy → Status Suspended
- Deploy/Recover device to an Employee
- XOPS – Update Inventory
- XOPS – Restock Patch
- XOPS – Patch Runbook
- Deploy a Device to an Employee
- Replace Device from an Employee
- Recover a device from an Employee
- XOPS Webhook → Catalog Request Flow
- XOPS Webhook → RITM Status Sync
v1.6.3
Updates requested by the Certification Team:
- The flow affecting the Spoke compatibility has been removed.
- Duplicate ACLs with missing roles have been removed.
v1.6.2
- Add Webhook Events (Scripted REST API and table) with extended support/compatibility:
- Webhook Events with OAuth (compatible with Washington release and later).
- Webhook Events with Bearer Token (compatible with releases earlier than Washington, e.g. Xanadu).
v1.5.0
- Add Create a XOPS Runbook with Notes
- Remove Webhook Events (Scripted REST API and table)
v1.4.17
- Add Kits to Create a XOPS Runbook
- Get XOPS Runbook Status
- Get XOPS Runbook Notes
- Get XOPS Runbook Devices & Tracking Information
- Update XOPS Runbook Notes
- Update XOPS Runbook Devices & Tracking Information
- Webhook Events (Scripted REST API and table)
v1.3.0
- Remove unused mobile menu records (requested by Certification Team)
- Remove unnecessary ACL records (requested by Certification Team)
v1.2.0
- Add xops_user role.
- Minor improvements.
v1.0.0:
- Create, Get, Update, Cancel Runbooks.
- Create, Get, Update, Delete Employees.
- Request trigger context.
API Keys from the XOPS Configuration Center