Operator by Fibric · Reference · built on request
Uptime Response
When an uptime check fails, proposes the page to whoever is on call, the public incident, and the rollback of the deploy before it.
Reference · built on requestConnectorWork & ticket management
Incident, problem, change, and request records from a ServiceNow instance through the Table API and other inbound REST APIs.
ServiceNow is a platform for IT and enterprise service management. Each customer runs its own instance, and records such as incidents are rows in tables that the inbound REST APIs expose by name: the Table API, Aggregate API, Import Set API, Attachment API, and any Scripted REST API the instance defines. Access is governed by the caller's roles and by REST API ACLs.
Through Fibric, an operator reads records from the tables you name, applies an encoded query, and proposes a field update, a reassignment, or a new record for your approval. Each approved change is written down with what changed, why, and how to reverse it.
This is a reference listing. It documents what Fibric would read from ServiceNow and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.
Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.
When monitoring fires, the operator drafts an incident record with the alert context, proposes it through POST on the incident table, and adds the incident number to the paging channel.
With Uptime Response
During a freeze, the operator reads change records scheduled in the window and proposes a hold and a note before the change proceeds.
With Change Freeze
Change records for patching get their planned dates checked against the maintenance calendar. The operator proposes date moves and assignments for approval.
With Patch Window
Requests logged in a request table are read by category and location. The operator proposes the assignment group and priority and leaves the reason in the record.
With Request Routing
Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.
Request ServiceNow ↗Ask about the capabilities and requirements in this listing.
For project-specific requirements, contact Fibric.
This connector listing is developed, published, and supported by Fibric. It describes integration with ServiceNow through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy