ServiceNow: Incident


Your use of this download is governed by Stonebranch’s Terms of Use, which are available at


ServiceNow aims to deliver digital workflows that create great experiences and unlock productivity for enterprise operations. The company's core business revolves around management of "incident, problem, and change".

This Integration allows customers to create incident tickets in ServiceNow straight from the Universal Controller. A typical Use Case is creating a ticket in ServiceNow in the event of a Task failure within the Universal Controller.

Version Information

Template NameExtension NameExtension Version
ServiceNow Incidentue-servicenow-incident2.1.0

Refer to Changelog for version history information.

Software Requirements

This integration requires a Universal Agent and a Python runtime to execute the Universal Task.

Software Requirements for Universal Template and Universal Task

Tested with Python version 3.7.6 and 3.11.6 and with the Universal Agent bundled Python distribution.

Software Requirements for Universal Agent

Both Windows and Linux agents are supported.

  • Universal Agent for Windows x64 Version and later with Python options installed.
  • Universal Agent for Linux Version and later with Python options installed.

Software Requirements for Universal Controller

Universal Controller Version and later.

Network and Connectivity Requirements

  • Extension's Universal Agent host should be able to reach ServiceNow REST endpoints.
  • When creating attachments from Task Instances, the extension's Universal Agent Host should be able to reach the Universal Controller.
  • The ServiceNow Credentials provided in the ServiceNow Incident Universal Task should have sufficient permissions to invoke ServiceNow APIs and create incidents.

Supported ServiceNow Versions

This integration is tested on ServiceNow Vancouver. It should be compatible with newer versions of ServiceNow as long as ServiceNow backward compatibility is preserved.

Key Features

This Universal Extension provides the following key features:

  • Actions
    • Create a ServiceNow Incident.
  • Authentication
    • Authentication using ServiceNow Credentials.
    • Authentication using OAuth2
  • Input/Output
    • Capability to send the output of any task instance as an incident attachment.

Import Universal Template

To use the Universal Template, you first must perform the following steps.

  1. This Universal Task requires the Resolvable Credentials feature. Check that the Resolvable Credentials Permitted system property has been set to true.

  2. To import the Universal Template into your Controller, follow the instructions here.

  3. When the files have been imported successfully, refresh the Universal Templates list; the Universal Template will appear on the list.

Modifications of this integration, applied by users or customers before or after import, might affect its supportability. For more information, refer to Integration Modifications.

Configure Universal Task

For a new Universal Task, create a new task and enter the required input fields.

Input Fields

The input fields for this Universal Extension are described below.

FieldInput typeDefault valueTypeDescription
ActionRequiredCreate IncidentChoiceAction performed upon the task execution. Available actions.
  • Create Incident
ServiceNow Instance URLRequired-TextURL of the ServiceNow instance.
Authentication TypeRequired

Basic Authentication


Authentication method to use. Available methods,

  • Basic Authentication

  • Oauth2 (ServiceNow API endpoint)

ServiceNow CredentialsRequired-CredentialsCredentials for accessing ServiceNow via API. The Credentials definition should be as follows.
  • ServiceNow username as "Runtime User".
  • ServiceNow password as "Runtime Password".
Client CredentialsOptional-Credentials

Credentials for authenticating using OAuth2 (retrieving access token). The Credentials definition should be as follows.

  • Client ID as "Runtime User"
  • Client Secret as "Runtime Password"

Required when Authentication Type is Oauth2 (ServiceNow API)

CallerOptional-Dynamic ChoiceUser who reported or is affected by this incident.
CategoryOptional-Dynamic ChoiceThe category for incident creation. If not provided, the default category defined on ServiceNow will be considered.
SubcategoryOptional-Dynamic ChoiceThe subcategory for incident creation. The choice of Subcategory depends on the previous choice of Category.
ImpactOptional-Dynamic ChoiceThe impact of the created incident
UrgencyOptional-Dynamic ChoiceThe urgency of the created incident.
Assigned ToOptional-Dynamic ChoiceThe user is primarily responsible for treating this incident in ServiceNow.
Assignment GroupOptional-Dynamic ChoiceAssignment group that is responsible for working on this incident in ServiceNow.
Short DescriptionRequired-TextShort description of the incident.
DescriptionOptional-Large TextDescription of the incident.
Attach Output SourceRequired-- None --ChoiceParameter controlling whether an attachment will be attached to the incident and the source of it. The following options are available.
  • -- None --
  • Sibling Task Instance
  • Any Task Instance
Output TypeOptionalAllChoiceThe type of output to be used as an attachment. The following options are available.
  • All
  • Standard Output
  • Standard Error
Required when Attach Output Source is “Sibling Task” or “Any Task Instance”.
Number of linesOptional100IntegerThe number of lines to be retrieved from the task instance output. The extension will provide up to the specified number of lines, less if there are not enough lines generated.

Required when Attach Output Source is “Sibling Task” or “Any Task Instance”.

The value must be greater than 0.
Task Instance IDOptional-TextUUID of the task instance, the output of which is attached. UAC Functions can be used to resolve the required Task Instance ID. For more information, the reader can refer to the task examples.

Required when Attach Output Source is “Sibling Task” or “Any Task Instance”.
UC URLOptional-TextBase URL of the target Universal Controller.

Required when Attach Output Source is “Sibling Task” or “Any Task Instance”.
UC CredentialOptional-
Credential for accessing the Controller.

The Credentials definition should be as follows.
  • UA Controller username as "Runtime User".
  • UA Controller password as "Runtime Password".
Required when Attach Output Source is “Sibling Task” or “Any Task Instance”.

Using empty values for dynamic choice fields will result in ServiceNow setting a default value for the field if one exists.

Using non-existing values for dynamic choice fields will result in ServiceNow setting an empty value or a default value for the field if one exists.

Task Examples

Create Incident

Example of creation of an incident.

Create an Incident with an attachment from a Sibling Task

Example of creating an incident with an attachment from a sibling task within a workflow. The workflow is configured to create a ServiceNow incident when a task fails.

An example workflow where a ServiceNow Incident Universal Task follows the Failure transition of a SQL Task is provided below.

An example of a task configured to use the information from the failed Universal Task Instance as an attachment for creating a ServiceNow Incident is provided below.

Create an Incident from any Task Instance

Example of creation of an incident from any Task Instance.

Best practice to configure such a scenario within UAC is shown below.

Step 1: Create a Monitor Task that monitors for the failure of tasks by configuring Monitor Details.

Step 2: Configure the ServiceNow Incident task. The created Incident Task propagates the output of the failed Task Instance as an attachment to ServiceNow. For that, a Task Monitor trigger is required.

Step 3: Create a Task Monitor Trigger linked to the Monitor Task (on Step 1), which controls the action that needs to be taken when the monitor successfully monitors a failure, in this case, the trigger of an incident ticket configured on Step 2.

Create Incident using OAuth2 authentication

Task Output

Exit Codes

The exit codes for this Universal Extension are described below.

Exit CodeStatus Classification CodeStatus Classification DescriptionStatus Description
0SUCCESSSuccessful ExecutionSUCCESS: Ticket Created
1FAILClient Error. The error originated on the client side.FAIL: Client Error: < Error description >
1FAILServer Error. The error originated from the server side.FAIL: Server Error: < Error description >
2AUTHENTICATION_ERRORBad CredentialsAUTHENTICATION_ERROR: The account cannot be authenticated.
3AUTHORIZATION_ERRORInsufficient permissionsAUTHORIZATION_ERROR: The account is not authorized to perform the requested action.
20DATA_VALIDATION_ERRORInput fields validation error.DATA_VALIDATION_ERROR: Some of the input fields cannot be validated. See STDERR for more details.

Extension Output

In the context of a workflow, subsequent tasks can rely on the information provided by this integration as Extension Output.

Attribute changed is populated as follows

  • true, in case a ServiceNow incident is successfully created.
  • false, in case a ServiceNow incident is not successfully created.

The Extension output contains the attribute result. Attribute result contains the following sub-attributes:

codenumberThe HTTP Response Code from ServiceNow.
ticket_numberstringThe ticket number is given to the created incident.
sys_idstringThe UID of the incident, generated by ServiceNow.

An example of the Extension Output for creating a ServiceNow Incident using Oauth the output of a Task Instance ID as an attachment is presented below.

Extension Output
    "exit_code": 0,
    "status_description": "SUCCESS: ServiceNow Incident Create Incident executed successfully!",
    "changed": true,
    "invocation": {
        "extension": "ue-servicenow-incident",
        "version": "2.1.0",
        "fields": {
            "action": "Create Incident",
            "authentication_type": "Oauth2 (ServiceNow API endpoint)",
            "servicenow_instance_url": "",
            "servicenow_credentials_username": "****",
            "servicenow_credentials_password": "****",
            "caller": null,
            "category": "Software",
            "subcategory": "Operating System",
            "impact": "2 - Medium",
            "urgency": "2 - Medium",
            "assigned_to": "Jewel Agresta",
            "assignment_group": "RMA Approvers",
            "short_description": "Short Decription",
            "description": "Long description",
            "attach_output_source": null,
            "output_type": null,
            "number_of_lines": null,
            "task_instance_id": null,
            "uc_url": null,
            "uc_credentials_username": null,
            "uc_credentials_password": null,
            "client_credentials_id": "f7338f849cad4fffbc4dd2fd9976a32b",
            "client_credentials_secret": "****"
    "result": {
        "code": 201,
        "ticket_number": "INC0010056",
        "sys_id": "5115d027a30f383f6df5209c5e27a117"


STDOUT and STDERR provide additional information to the User. The populated content can be changed in future versions of this extension without notice. Backward compatibility is not guaranteed.

Integration Modifications

Modifications applied by users or customers before or after import might affect the supportability of this integration. The following modifications are discouraged to retain the support level for this integration.

  • Python code modifications should not be done.
  • Template Modifications
    • General Section
      • "Name", "Extension", "Variable Prefix", and "Icon" should not be changed.
    • Universal Template Details Section
      • "Template Type", "Agent Type", "Send Extension Variables", and "Always Cancel on Force Finish" should not be changed.
    • Result Processing Defaults Section
      • Success and Failure Exit codes should not be changed.
      • Success and Failure Output processing should not be changed.
    • Fields Restriction Section
      • Default configured values should not be changed.

Users and customers are encouraged to report defects or feature requests at Stonebranch Support Desk.

Document References

This document references the following documents.

Document LinkDescription
Universal TemplatesUser documentation for creating, working with, and understanding Universal Templates and Integrations.
Universal TasksUser documentation for creating Universal Tasks in the Universal Controller user interface.
CredentialsUser documentation for creating and working with credentials.
Resolvable Credentials Permitted PropertyUser documentation for Resolvable Credentials Permitted Property.
ServiceNow DocumentationUser documentation for ServiceNow.


ue-servicenow-incident-2.1.0 (2024-02-15)

  • Enhancements: Added support for OAuth2 authentication method
  • Breaking Changes: This integration is no longer importable on Universal Controller 7.1 or runnable on Agent version 7.1.

ue-servicenow-incident-2.0.0 (2023-09-14)

Deprecations and Breaking Changes

  • breaking changes: This integration is no longer importable on Universal Controller 7.0 or runnable on Agent version 7.0. (#34222)


  • Fixed: Remove value validation for the "Urgency" and "Impact" Dynamic Choice Fields. (#34232)

ue-servicenow-incident-1.0.0 (2022-07-29)

  • Initial Release: Basic Functionality for ServiceNow Incidents (#29442)