ServiceNow Integration

This guide explains how to connect ServiceNow to Supervity, what data is available after connection, how operators can use ServiceNow data and actions within workflows, and how to remove the integration when needed.

---

Overview

The Supervity ServiceNow integration allows your workspace to securely connect ServiceNow as a governed platform capability.

Once connected, operators and workflows can use ServiceNow data and actions to automate IT service management (ITSM) processes, handle incidents, manage custom and standard table records, and coordinate service operations across enterprise systems.

With the ServiceNow integration, Supervity can:

• Manage incidents: List, retrieve, create, update, and delete incident records
• Query records across any standard or custom ServiceNow table (e.g., Change Requests, Service Catalog requests, Problem records)
• Retrieve specific table records by unique identifier
• Create new records in any accessible ServiceNow table
• Update existing table records with new statuses, notes, and field values
• Delete obsolete or transient table records when required
• Use ServiceNow ITSM records and operational context in AI operators
• Trigger workflows based on ServiceNow incident and ticket activity

All ServiceNow access is governed through Supervity's security, permissions, and audit controls.

---

Prerequisites

Before connecting ServiceNow, ensure you have:

• An active Supervity workspace
• A ServiceNow instance (Production, Sub-production, or Developer instance)
• Your ServiceNow instance URL (e.g., https://your-instance.service-now.com)
• Permission to authorize OAuth applications on your ServiceNow account
• An active user account with appropriate roles and Access Control Lists (ACLs) for the tables and records you want to manage

Depending on your organization's ServiceNow security policies, an administrator may need to configure an OAuth API endpoint / Connected App in ServiceNow before users can connect.

---

Adding the ServiceNow Integration

Follow these steps to connect ServiceNow to Supervity. If you encounter any issues during setup, refer to the Troubleshooting section of this guide.

Step 1: Open Integrations

1. Log in to Supervity.
2. From the left navigation bar, click the Integrations icon.

This opens the Integrations page, where all available integrations are listed. Connected integrations and available integrations can both be managed from this page.

Step 2: Select ServiceNow

1. Locate ServiceNow in the available integrations list.
2. Click Connect.

Step 3: Configure Instance URL and Authorize Access

You will be prompted to enter your ServiceNow instance base URL.

1. Enter your full ServiceNow instance URL (for example, https://your-instance.service-now.com).
2. Click Proceed to be redirected to your ServiceNow instance's secure login and authorization page.
3. Sign in with your ServiceNow credentials if prompted.
4. Review the requested access permissions and click Allow (or Authorize) to grant Supervity access to your ServiceNow account.

• Supervity uses ServiceNow's standard OAuth 2.0 authorization flow.
• Your ServiceNow password is never shared with or stored by Supervity.

Step 4: Complete Connection

After authorization, you will be redirected back to Supervity.

The ServiceNow integration will appear as Connected on the Integrations page. Your workspace can now securely access ServiceNow capabilities according to the permissions and roles of the authorized user account.

Having trouble? See the Troubleshooting section for step-by-step help with common setup issues.

---

How ServiceNow Works in Supervity

After connection, ServiceNow becomes available as a governed platform tool.

Operators can use ServiceNow capabilities when planning and executing tasks, while workflows can automate actions using ServiceNow records and ITSM data.

Common use cases include:

• Automatically creating incident tickets from monitoring alerts, error logs, or user bug reports
• Updating incident status, impact, urgency, and resolution work notes during troubleshooting
• Assigning incidents to specific support or engineering assignment groups
• Querying and retrieving Change Requests, Problems, or Service Catalog items
• Creating and modifying custom table records to sync data with external business systems
• Automating ticket triage, escalation, and SLA tracking workflows
• Synchronizing ITSM updates with communication channels such as Slack or Microsoft Teams

---

Using ServiceNow in Operators

Connected ServiceNow capabilities become available to operators automatically. Operators determine when ServiceNow data or actions are required to complete a task and execute accordingly, while remaining governed by workspace permissions, security controls, and approval policies.

What Operators Can Do with ServiceNow

Operators can perform the following actions using ServiceNow:

• Manage incidents (list incidents with filters, get incident details, create new incidents, update incident fields/comments, and delete incidents)
• Manage any ServiceNow table record (list records from any table, get record details, create records, update fields, and delete records)
• Apply filtering queries to search and retrieve targeted records
• Correlate ServiceNow ticket data with monitoring tools, source control, CRM, and communication platforms
• Generate summaries, post-mortem notes, and operational status reports from incident data
• Combine ITSM actions with other applications for automated end-to-end IT workflows

Typical Operator Use Cases

---

Features & Prerequisites

For each ServiceNow capability available in Supervity, the following describes the use case and the prerequisites required before use.

List Incidents

Use Case: Retrieve a list of incident records from ServiceNow, with support for filtering by status, priority, assignment group, or creation date. Useful for monitoring active issues and ticket backlog auditing.

Prerequisites:

• ServiceNow account connected to Supervity
• Read permissions for the incident table in your ServiceNow instance

---

Get Incident

Use Case: Retrieve full details of a specific incident using its unique record identifier (sys_id), including short description, comments, urgency, impact, state, and assigned personnel.

Prerequisites:

• ServiceNow account connected to Supervity
• Target incident identifier (sys_id) must exist and be accessible

---

Create Incident

Use Case: Automatically create a new incident record with short description, caller details, comments, urgency, and impact ratings.

Prerequisites:

• ServiceNow account connected to Supervity
• Incident short description and relevant details must be provided
• Create permissions for the incident table in your ServiceNow instance

---

Update Incident

Use Case: Modify an existing incident by updating its state, assignment group, urgency, impact, resolution notes, or customer work notes.

Prerequisites:

• ServiceNow account connected to Supervity
• Target incident identifier (sys_id) must exist
• Write permissions for the incident table in your ServiceNow instance

---

Delete Incident

Use Case: Remove an incident record from ServiceNow when created in error or during test clean-up.

Prerequisites:

• ServiceNow account connected to Supervity
• Target incident identifier (sys_id) must exist
• Delete permissions for the incident table in your ServiceNow instance

---

List Table Records

Use Case: Retrieve and query records from any accessible ServiceNow standard or custom table (such as change_request, problem, sc_req_item, or custom application tables) with optional query filtering and pagination.

Prerequisites:

• ServiceNow account connected to Supervity
• Valid target table name must be specified
• Read permissions for the target table

---

Get Table Record

Use Case: Fetch all field values and metadata for a specific record in any ServiceNow table using its unique record identifier (sys_id).

Prerequisites:

• ServiceNow account connected to Supervity
• Target table name and record identifier (sys_id) must exist and be accessible

---

Create Table Record

Use Case: Programmatically insert a new record with specified field values into any standard or custom ServiceNow table.

Prerequisites:

• ServiceNow account connected to Supervity
• Target table name and required record fields must be provided
• Create permissions for the target table in your ServiceNow instance

---

Update Table Record

Use Case: Update one or more field values on an existing record in any ServiceNow table using its unique record identifier (sys_id).

Prerequisites:

• ServiceNow account connected to Supervity
• Target table name and record identifier (sys_id) must exist
• Write permissions for the target table in your ServiceNow instance

---

Delete Table Record

Use Case: Delete an existing record from any ServiceNow table by its unique record identifier (sys_id).

Prerequisites:

• ServiceNow account connected to Supervity
• Target table name and record identifier (sys_id) must exist
• Delete permissions for the target table in your ServiceNow instance

---

Permissions Requested

Supervity operates within the security boundary of the authenticated ServiceNow user account, inheriting the user's assigned roles, groups, and Access Control Lists (ACLs).

Supervity follows least-privilege principles and only accesses data necessary to provide requested functionality.

---

Authentication & Security

The ServiceNow integration uses OAuth 2.0 authentication.

Security controls include:

• Encrypted credential storage (AES-256)
• Dedicated instance base URL routing to connect directly to your organization's ServiceNow instance
• Token refresh and rotation support
• Immediate revocation capabilities
• Workspace-level governance controls
• Complete audit logging
• TLS 1.3 for all API and UI connections

All ServiceNow access remains subject to Supervity security policies, instance ACLs, and role-based permissions.

---

Managing the Integration

View Connection Status

From the left navigation bar, click the Integrations icon.

For ServiceNow you can view:

• Connection status
• Connected instance base URL
• Last usage information
• Associated workflows and operators

Reconnect ServiceNow

If ServiceNow authorization expires, user roles change, or instance URLs are updated:

1. Open the Integrations page from the left navigation bar.
2. Select ServiceNow.
3. Click Reconnect.
4. Complete authorization again through your ServiceNow instance portal.

Existing workflows and operators do not need to be recreated.

Removing the ServiceNow Integration

You can remove the ServiceNow connection from your Supervity workspace at any time directly from within the Supervity platform.

Steps to Remove

1. Log in to Supervity.
2. From the left navigation bar, click the Integrations icon.
3. Locate and select ServiceNow from the integrations list.
4. Click Disconnect.
5. Confirm the action when prompted.

Implications of Removal

Once removed:

• Supervity immediately loses all access to your ServiceNow instance and associated data
• No new ServiceNow data will be retrieved or modified after removal
• All active ServiceNow connections within your Supervity workspace are terminated
• Scheduled or active workflows that depend on ServiceNow will stop executing
• ServiceNow-dependent workflow steps will fail safely with clear error messages
• Existing workflow definitions within Supervity are not deleted — only the active connection is terminated
• Historical execution logs remain available for auditing purposes

Disconnecting ServiceNow does not delete workflow definitions, operators, or previously generated outputs.

How Your Data Is Handled After Removal

Data Handling on Removal:

• Supervity immediately loses access to your ServiceNow instance upon removal
• No new ServiceNow records or data will be collected or processed after disconnection
• Temporary files processed during workflow execution are deleted after execution completes
• ServiceNow access tokens and all account-related data are permanently deleted from Supervity's platform within 15 minutes of disconnection — no background access continues after removal

---

Auditing & Observability

All ServiceNow activity performed through Supervity is logged.

Audit records include:

• Which operator requested access
• Which workflow executed the action
• Timestamp of execution
• Success or failure status
• Relevant inputs and outputs (sensitive values are redacted)

This supports compliance, troubleshooting, governance, and operational visibility.

---

Troubleshooting

If you encounter issues at any stage, refer to the steps below. For issues not covered here, contact the Supervity support team.

Authorization Failed During Setup

Likely Cause: Invalid instance URL, missing OAuth Connected App endpoint in ServiceNow, or insufficient user privileges.

Resolution:

1. Ensure the entered instance base URL is correct (e.g., https://your-instance.service-now.com) and reachable.
2. Verify that OAuth is enabled on your ServiceNow instance and that a client application is configured.
3. Confirm that your user account has permission to log in and authorize third-party applications.
4. Return to Supervity → Integrations → ServiceNow and click Connect to retry.

---

ServiceNow Shows Connected but Records Are Missing

Likely Cause: Access Control List (ACL) restrictions, missing roles (e.g., itil role for incidents), or incorrect filter query.

Resolution:

1. Check that the authorized ServiceNow user account has appropriate roles (such as itil or table-specific roles) to view the requested records.
2. Review any query parameters or filters to ensure they are formatted correctly according to ServiceNow query syntax.
3. Reconnect the integration via Integrations → ServiceNow → Reconnect if user roles were recently updated in ServiceNow.

---

Connection Expired or Token Invalid

Likely Cause: OAuth token expired or was revoked in ServiceNow instance settings.

Resolution:

1. Go to Integrations → ServiceNow → Reconnect.
2. Complete the ServiceNow authorization flow again.
3. Existing workflows do not need to be reconfigured after reconnection.

---

Workflow Cannot Access ServiceNow

Likely Cause: ServiceNow may have been disconnected, or workspace governance policies may restrict access.

Resolution:

1. Confirm ServiceNow is still connected under the Integrations page.
2. Verify the workflow has permission to use ServiceNow within your workspace governance settings.
3. Check that workspace policies allow ServiceNow execution for the relevant operators or workflows.

---

Incident Creation or Update Fails

Likely Cause: Missing mandatory fields (e.g., caller, short description), invalid state transitions, or lack of write ACLs.

Resolution:

1. Verify that all mandatory fields configured on your ServiceNow incident table are provided.
2. Check that the record identifier (sys_id) is valid when updating an existing incident.
3. Ensure the authorized account has write permissions on the incident table.

---

Generic Table Operations Fail

Likely Cause: Invalid table name, non-existent record identifier (sys_id), or cross-scope table access restrictions.

Resolution:

1. Verify that the table name is spelled correctly (e.g., change_request, problem, sc_req_item).
2. Ensure the ServiceNow table allows web service access and that the user's ACLs permit read/write/create/delete operations on that table.
3. Check that the record identifier (sys_id) exists in the specified table.

---

Frequently Asked Questions

Q: Is my ServiceNow password shared with or stored by Supervity?

No. Supervity uses ServiceNow's standard OAuth 2.0 authorization flow. Your ServiceNow password is never shared with or stored by Supervity. Only scoped access tokens are stored, and these are encrypted at rest using AES-256.

---

Q: Can Supervity interact with custom ServiceNow tables?

Yes. The integration includes generic table operations that allow operators and workflows to list, retrieve, create, update, and delete records in any standard or custom ServiceNow table that your authenticated user account has permissions to access.

---

Q: Will I need to reconfigure my workflows after reconnecting ServiceNow?

No. If you reconnect ServiceNow due to token expiry or permission updates, existing workflow definitions and operators do not need to be recreated or reconfigured.

---

Q: What happens to my workflows if I disconnect or remove ServiceNow?

Workflow definitions are not deleted when ServiceNow is disconnected or removed. However, any workflow steps that depend on ServiceNow will fail safely with clear error messages until ServiceNow is reconnected.

---

Q: How do I authorize the Supervity ServiceNow integration?

Log in to Supervity at Supervity, navigate to the Integrations page from the left navigation bar, locate ServiceNow, and click Connect. Enter your ServiceNow instance URL, and you will be redirected to your instance's authorization page to approve the connection. After authorization, you will be redirected back to Supervity automatically. See the Adding the ServiceNow Integration section above for full step-by-step instructions.

---

Q: Who do I contact if I have an issue with the integration?

Contact the Supervity support team. See the Support section below for full contact details, support hours, and SLA information.

---

Support

If you need assistance with the ServiceNow integration, visit the Support page.

Support Hours

• Monday to Friday, 9:00 AM – 6:00 PM IST
• Requests submitted outside business hours will be addressed on the next business day

First Response SLA

• All support requests receive an initial response within 24 business hours

Contact Information

When Contacting Support, Please Provide

• Workspace name
• ServiceNow instance URL used for authorization
• Relevant workflow or operator information
• Error messages or screenshots when available

This helps the support team investigate and resolve issues more quickly.

---

Related Documentation

• Integrations Overview
• OAuth2
• Security & Privacy
• Supervity Website