# ServiceNow

ServiceNow is a cloud-based enterprise platform that helps organizations automate and manage digital workflows across IT, HR, customer service, and operations.

- **Category:** it operations
- **Auth:** BASIC
- **Composio Managed App Available?** N/A
- **Tools:** 5
- **Triggers:** 0
- **Slug:** `SERVICENOW`
- **Version:** 20260316_00

## Tools

### Attach file to record

**Slug:** `SERVICENOW_ATTACH_FILE_TO_RECORD`

Attaches a file to a specified record in a ServiceNow table. This action uploads a file and associates it with a specific record (e.g., incident, problem, change request). The file will be visible in the ServiceNow UI under the record's attachments section. Common use cases: - Attach screenshots to incident reports - Upload documents to change requests - Add log files to problem records - Store evidence files for security incidents The action returns complete attachment metadata including download link, file size, and creation details. Note: This action permanently modifies a live ServiceNow instance — attachments cannot be bulk-removed once added.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `file_name` | string | Yes | Name to give the attachment (e.g., 'report.pdf', 'screenshot.png'). This will be the visible filename in ServiceNow. |
| `table_name` | string | Yes | Name of the ServiceNow table to attach the file to (e.g., 'incident', 'problem', 'change_request'). |
| `creation_time` | string | No | Creation date and time of the attachment. Use this parameter to capture attachment creation times when the Now Mobile app is offline and the attachment is uploaded to a record at a later time. |
| `record_sys_id` | string | Yes | Sys_id of the specific record in the table to attach the file to. This is the unique identifier of the record (e.g., incident sys_id). |
| `file_to_upload` | object | Yes | File to upload. |
| `encryption_context` | string | No | Sys_id of an encryption context record. Specify this parameter to allow only users with the specified encryption context to access the attachment. For additional information on encryption context records, see https://www.servicenow.com/docs/csh?topicname=column-level-encryption-landing&version=yokohama&pubname=yokohama-platform-security. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Cancel change conflict check

**Slug:** `SERVICENOW_CANCEL_CHANGE_CONFLICT_CHECK`

Cancels the running conflict checking process for a specified ServiceNow change request. Use this action when a conflict check is taking too long or needs to be aborted, and you want to stop the process without waiting for it to complete naturally. This is commonly used when automated change management workflows need to be expedited or when conflict checks are blocking other operations. This action is idempotent — calling it on a change request that has no active conflict check running will still return a success response. However, if the change request doesn't exist, a 404 error will be returned.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the change request whose conflict checking process should be cancelled. This is a 32-character hexadecimal string that uniquely identifies the change request record. Example: '1766f1de47410200e90d87e8dee490f6'. The change request must exist and have an active conflict checking process running. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create a record

**Slug:** `SERVICENOW_CREATE_A_RECORD`

Creates a new record in a specified ServiceNow table with the provided field values. Common tables include: 'incident', 'problem', 'change_request', 'task', 'sys_user'. The created record is returned with its sys_id and auto-generated number.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `table_name` | string | Yes | The name of the table where the record will be created (e.g., 'incident', 'problem', 'change_request', 'sys_user'). |
| `record_data` | object | No | Field-value pairs for the new record. Available fields depend on the table schema. For 'incident' table, common fields include: 'short_description', 'description', 'urgency' (1-3), 'impact' (1-3), 'priority', 'assignment_group', 'assigned_to', 'category', 'state'. For reference fields (like 'assignment_group' or 'assigned_to'), use the sys_id of the referenced record, or set sysparm_input_display_value=true to use display values. Example: {'short_description': 'Network outage', 'urgency': '1', 'impact': '1', 'description': 'Unable to access network'} |
| `sysparm_view` | string ("desktop" | "mobile" | "both") | No | UI view to determine which fields are returned in the response. If not specified, returns fields from the default view. |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response (e.g., 'number,short_description,state'). Invalid fields are ignored. If not specified, all fields are returned. |
| `sysparm_display_value` | string ("true" | "false" | "all") | No | Determines the type of data returned in the response. 'false': Returns actual database values (sys_ids for references, numeric values for choices). 'true': Returns display values (names for references, text labels for choices). 'all': Returns both display and actual values. |
| `sysparm_input_display_value` | boolean | No | Set to true if providing display values (e.g., user names) instead of sys_ids in record_data for reference fields. When false (default), reference fields must contain sys_ids. |
| `sysparm_exclude_reference_link` | boolean | No | Set to true to exclude Table API links for reference fields in the response. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create attachment upload

**Slug:** `SERVICENOW_CREATE_ATTACHMENT_UPLOAD`

Uploads a file as a multipart form-data attachment to a specified record in ServiceNow. Use this action when you need to attach files to ServiceNow records (e.g., incidents, problems, change requests) using the multipart form-data upload endpoint. This action sends the file as a multipart/form-data request with the table name, table sys_id, and file content. Common use cases: - Attach documents or screenshots to incident reports - Upload evidence files to problem records - Add files to change requests for documentation The action returns complete attachment metadata including the sys_id, download link, file size, and creation details. This action permanently modifies a live ServiceNow instance — the attachment cannot be recovered once deleted.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `table_name` | string | Yes | Name of the ServiceNow table to attach the file to (e.g., 'incident', 'problem', 'change_request'). |
| `table_sys_id` | string | Yes | Sys_id of the record to attach the file to. This is the unique identifier of the record. |
| `file_to_upload` | string | Yes | File to upload. Can be either a FileUploadable object (with s3key) or a FileContent object with direct content. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create CI Lifecycle Management Action

**Slug:** `SERVICENOW_CREATE_CILIFECYCLEMGMT_ACTION`

Adds a specified configuration item (CI) action using the ServiceNow CI Lifecycle Management API. Use this action when you need to create or execute a CI lifecycle action for a Configuration Item in ServiceNow's CMDB. This endpoint allows you to trigger specific lifecycle actions (such as activate, retire, or custom actions) on CIs programmatically. The action requires the CI identifier and the action name to be executed. Ensure the action is valid for the specified CI class.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `ci` | string | Yes | The unique identifier of the Configuration Item (CI) to associate with the action. This can be the sys_id (32-character hexadecimal string) or other CI identifier. Example: '00a96c0d3790200044e0bfc8bcbe5db4' |
| `action` | string | Yes | The name or identifier of the action to execute on the CI. This corresponds to a valid CI lifecycle action defined in the ci_lifecycle_action table. Example: 'test_action', 'activate', 'retire' |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create ci lifecycle mgmt operators

**Slug:** `SERVICENOW_CREATE_CI_LIFECYCLE_MGMT_OPERATORS`

Registers a new operator for a non-workflow user in the ServiceNow CI Lifecycle Management system. Use this action when you need to create or register an operator identity for CI lifecycle management purposes. The operator must be associated with a non-workflow user account. The returned req_id can be used to manage the operator (e.g., delete it later).

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `email` | string | Yes | The email address of the operator. Must be a valid email format. Example: 'test@example.com' |
| `last_name` | string | Yes | The last name (surname) of the operator. Example: 'Operator' |
| `user_name` | string | Yes | The unique username for the operator being registered. This must be a non-workflow user account. Example: 'test_operator' |
| `first_name` | string | Yes | The first name of the operator. Example: 'Test' |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Set CI Operational State

**Slug:** `SERVICENOW_CREATE_CI_LIFECYCLE_MGMT_STATUSES`

Sets the operational state for one or more configuration items (CIs) using the ServiceNow CI Lifecycle Management API. Use this action when you need to update the operational status of CIs in ServiceNow's CMDB. This endpoint allows you to programmatically set the operational state (operational, non-operational, on order, inventory, etc.) for a batch of configuration items. The action requires a list of CI identifiers and the operational state value to apply.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_ids` | array | Yes | List of Configuration Item (CI) identifiers to set the operational state for. Each identifier should be the sys_id (32-character hexadecimal string) of the CI. Example: ['73aa7167c42'] or ['00a96c0d3790200044e0bfc8bcbe5db4'] |
| `requestor` | string | No | The user ID or sys_id of the requestor who is setting the operational state. This is required for authorization purposes. Example: 'admin' or '681ccaf9c0a8016400b98a06818d6e1a' |
| `operational_state` | string | Yes | The operational state to set for the specified CIs. Common values: '1' = Operational, '2' = Non-Operational, '3' = On Order, '4' = Inventory. The valid values depend on your ServiceNow configuration. Example: '1' |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create CMDB Application Service

**Slug:** `SERVICENOW_CREATE_CMDB_APP_SERVICE`

Creates an application service in ServiceNow CMDB or updates an existing one if a service with the same name already exists. Use this action when you need to register a new application service in the Configuration Management Database (CMDB). This endpoint performs a create-or-update operation: if an application service with the specified name already exists, it will be updated with the provided values rather than creating a duplicate.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | Yes | Name of the application service to create. If an application service with the same name already exists, it will be updated with the provided values. |
| `order` | integer | No | Display order for the application service. Used when ordering or sorting application services in lists or UIs. |
| `tenant_id` | string | No | Tenant identifier for the application service. Used in multi-tenant deployments to scope the application service to a specific tenant. |
| `description` | string | No | Description of the application service providing details about its purpose and functionality. |
| `owning_segment` | string | No | Business owning segment for the application service. Defines the organizational segment that owns and is responsible for this application service. |
| `operational_status` | string | No | Operational status of the application service (e.g., 'Production', 'Development', 'Retired'). |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create CMDB Linux Server

**Slug:** `SERVICENOW_CREATE_CMDB_CI_LINUX_SERVER`

Creates a new Linux server configuration item (CI) in the ServiceNow CMDB. Use this action when you need to register a new Linux server in the Configuration Management Database (CMDB). This endpoint creates a record in the cmdb_ci_linux_server table with the specified attributes including hostname, IP address, OS details, and operational information. The created record is returned with its sys_id and auto-generated details.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `os` | string | No | Operating system name and version for the Linux server. Common values include: 'Linux Red Hat', 'Linux Ubuntu', 'Linux CentOS', 'Linux SUSE', 'Linux Debian', 'Red Hat Enterprise Linux 7', 'Ubuntu Server 22.04 LTS'. Example: 'Linux Red Hat', 'Linux Ubuntu', 'Red Hat Enterprise Linux 8' |
| `ram` | integer | No | Total RAM in megabytes (MB) installed on the Linux server. Example: 16384 (for 16GB), 32768 (for 32GB) |
| `fqdn` | string | No | Fully Qualified Domain Name (FQDN) of the Linux server. Example: 'web-server-01.example.com' |
| `name` | string | Yes | Name of the Linux server configuration item. This is the primary display name used to identify the server in the CMDB and ServiceNow UI. Example: 'prod-web-server-01', 'test-linux-final' |
| `vendor` | string | No | Vendor or reseller from whom the server or software was purchased. Example: 'Dell', 'HP', 'Lenovo', 'AWS' |
| `location` | string | No | Physical or logical location of the Linux server. Can be a data center name, building, rack location, or cloud region. Example: 'US-East-1', 'DC1-Rack-A12', 'Building A - Floor 3' |
| `model_id` | string | No | Hardware or virtual machine model identifier. Example: 'PowerEdge R740', 'VMware Virtual Platform', 'm5.large' |
| `cpu_count` | integer | No | Number of CPU cores or processors installed on the Linux server. Example: 4, 8, 16 |
| `host_name` | string | No | Fully qualified or short hostname of the Linux server as reported by the OS. This is typically the value returned by the 'hostname' command. Example: 'web-server-01', 'test-final.example.com' |
| `disk_space` | integer | No | Total disk space in megabytes (MB) allocated to the Linux server. Example: 512000 (for 500GB) |
| `ip_address` | string | No | Primary IP address of the Linux server. Supports both IPv4 and IPv6 formats. Example: '192.168.1.200', '10.0.0.1', '2001:db8::1' |
| `managed_by` | string | No | Name or sys_id of the person or group responsible for managing this server. Set sysparm_input_display_value=true to use display names instead of sys_ids. |
| `assigned_to` | string | No | sys_id or display name of the user assigned primary responsibility for this server. Set sysparm_input_display_value=true to use display names instead of sys_ids. |
| `cost_center` | string | No | Cost center identifier or name responsible for the financial aspects of this server. Example: 'CC-00123', 'IT Operations' |
| `description` | string | No | Detailed description of the Linux server providing context about its purpose, configuration, or any relevant notes. Example: 'Production web server running RHEL 8 with Apache' |
| `environment` | string | No | Environment classification for the Linux server. Common values: 'Development', 'Test', 'Production', 'Staging'. Example: 'Production', 'Development' |
| `mac_address` | string | No | Primary MAC (Media Access Control) address of the server's network interface. Format: six pairs of hexadecimal digits separated by colons or hyphens. Example: '00:50:56:C0:00:08', '00-50-56-c0-00-08' |
| `manufacturer` | string | No | Manufacturer or vendor of the Linux server hardware or virtualization platform. Example: 'VMware Inc.', 'Dell Inc.', 'HP', 'Amazon Web Services' |
| `purchase_date` | string | No | Date when the server hardware or license was purchased. Format: YYYY-MM-DD. Example: '2023-01-15' |
| `serial_number` | string | No | Hardware serial number of the Linux server as assigned by the manufacturer. Example: 'SN-12345ABCDE', 'VMware-42 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00' |
| `support_group` | string | No | Name of the group responsible for providing support for this server. Example: 'L2 Linux Support', 'NOC' |
| `cpu_core_count` | integer | No | Total number of CPU cores (sockets times cores per socket) on the server. Example: 32, 64 |
| `install_status` | string | No | Installation status of the Linux server. Common values: '1' = Installed, '2' = On Order, '3' = In Maintenance, '4' = Pending Installation, '5' = Pending Return, '7' = Absent. Example: '1' (Installed) |
| `kernel_version` | string | No | Linux kernel version running on the server. Example: '5.4.0-150-generic', '3.10.0-1160.el7.x86_64' |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response (e.g., 'sys_id,name,ip_address'). Invalid fields are ignored. If not specified, all fields are returned. |
| `assignment_group` | string | No | sys_id or display name of the group assigned to manage this server. Set sysparm_input_display_value=true to use display names instead of sys_ids. |
| `discovery_source` | string | No | Source of the discovery data for this CI. Common values include: 'Manual Entry', 'ServiceNow Discovery', 'LDAP', 'Import Set', 'MID Server', 'ECMDB'. If not specified, defaults to 'Manual Entry'. Example: 'Manual Entry', 'ServiceNow Discovery' |
| `os_address_width` | string | No | Operating system architecture bit-width. Common values: '32-bit', '64-bit'. Example: '64-bit' |
| `operational_status` | string | No | Operational status of the Linux server. Common values: '1' = Operational, '2' = Non-Operational, '3' = Being Installed, '4' = Being Repaired, '6' = Under Maintenance. Example: '1' (Operational) |
| `warranty_expiration` | string | No | Date when the server warranty expires. Format: YYYY-MM-DD. Example: '2026-01-15' |
| `sysparm_display_value` | string | No | Determines the type of data returned in the response. 'false': Returns actual database values (default). 'true': Returns display values. 'all': Returns both display and actual values. |
| `sysparm_exclude_reference_link` | boolean | No | Set to true to exclude Table API links for reference fields in the response. Defaults to false. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Ingest CMDB Records

**Slug:** `SERVICENOW_CREATE_CMDB_INGEST`

Inserts multiple records into a ServiceNow Import Set staging table. Use this action when you need to bulk-import configuration items (CIs) or other data into ServiceNow via an Import Set. Records are inserted into the specified staging table, which is processed by the associated transform map to load data into the target table (e.g., CMDB tables like cmdb_ci_server). The staging table name identifies the import set staging table (e.g., 'sys_import_set_row'), and the transform map associated with that table determines how each record is transformed. Note: Records are inserted into the Import Set staging table and will be transformed to the target table via the configured transform map.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `records` | array | Yes | Array of record objects to insert into the Import Set staging table. Each record should contain field-value pairs that match the columns of the staging table. Common fields include: 'name', 'ip_address', 'mac_address', 'serial_number', 'host_name', etc. Example: [{'name': 'test_server', 'ip_address': '192.168.1.100'}] |
| `staging_table_name` | string | Yes | Name of the import set staging table to insert records into. Examples: 'sys_import_set_row', 'u_cmdb_ci_staging', 'sys_import_tst_abc123'. This is a path parameter that identifies the staging table for the import set. The staging table is determined by the transform map configuration. |
| `sysparm_input_display_value` | boolean | No | Set to true if providing display values instead of sys_ids for reference fields in the records. When false (default), reference fields must contain sys_ids. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create CMDB Instance

**Slug:** `SERVICENOW_CREATE_CMDB_INSTANCE`

Creates a single Configuration Item (CI) in ServiceNow CMDB with the specified attributes. Use this action when you need to register a new configuration item (such as servers, databases, network devices, or application services) in the Configuration Management Database. The CI class determines the available attributes and relationships for the item.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `classname` | string | Yes | The name of the CMDB class for the configuration item (CI) to create. Common CI classes include: 'cmdb_ci' (generic CI), 'cmdb_ci_server', 'cmdb_ci_database', 'cmdb_ci_network_adapter', 'cmdb_ci_storage_device', 'cmdb_ci_service_discovered', 'cmdb_ci_hardware', 'cmdb_ciPrinter', etc. Use the full class name without 'u_' prefix for base classes. |
| `attributes` | object | Yes | A dictionary of attribute name-value pairs for the CI. The available attributes depend on the specified class. Common attributes across many CI classes include: 'name' (CI display name), 'serial_number', 'ip_address', 'mac_address', 'host_name', 'fqdn', 'manufacturer', 'model_id', 'vendor', 'purchase_date', 'assigned_to', 'assignment_group', 'location', 'support_group', 'managed_by', 'operational_status', 'install_status', 'cost', 'cost_center', 'u_custom_attribute'. Example: {'name': 'Production Server 01', 'serial_number': 'SN-12345', 'ip_address': '192.168.1.100'} |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create CMDB Instance Relation

**Slug:** `SERVICENOW_CREATE_CMDB_INSTANCE_RELATION`

Creates an inbound and/or outbound relation for a specific configuration item (CI) in the ServiceNow CMDB. Use this action when you need to establish relationships between configuration items in the CMDB, such as indicating that a server 'runs on' hardware, a service 'depends on' a database, or an application 'hosts' middleware components. This action adds relations to the specified CI (identified by classname and sys_id) without modifying the CI itself. Relations are bidirectional in the CMDB - adding an outbound relation from CI A to CI B also creates a corresponding inbound relation on CI B. Common use cases: Building CMDB relationship maps, establishing application dependencies, defining infrastructure hierarchies, or documenting service relationships.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The sys_id of the source configuration item to add relations to. This is a 32-character hexadecimal string. Example: '12345678901234567890123456789012' |
| `classname` | string | Yes | The CMDB class name for the configuration item (e.g., 'cmdb_ci', 'cmdb_ci_server', 'cmdb_ci_service'). This is the table name that defines the type of CI. |
| `inbound_relations` | array | No | List of inbound relations to create to this CI from other CIs. Inbound relations represent relationships where other CIs are the source. Example: To indicate another CI 'depends on' this CI, use type 'Used by::Depends on'. |
| `outbound_relations` | array | No | List of outbound relations to create from this CI to other CIs. Outbound relations represent relationships where this CI is the source. Example: To indicate this CI 'depends on' another CI, use type 'Depends on::Used by'. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create data classification classify

**Slug:** `SERVICENOW_CREATE_DATA_CLASSIFICATION_CLASSIFY`

Assigns pre-defined or user-defined data classification labels to records in ServiceNow tables. Use this action when you need to classify sensitive or confidential data records according to your organization's data governance policies. This action sends records to the Data Classification API which can apply classification labels such as 'Public', 'Internal', 'Confidential', or custom labels defined in the Data Classification table. The classification labels help enforce data access controls, encryption policies, and compliance requirements across the ServiceNow instance.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `items` | array | Yes | An array of items to classify. Each item specifies a source table, the sys_id of the record to classify, and optionally a label_id for the classification to assign. At least one item is required. Example: [{'source': 'sys_user', 'sysId': '005d500b536073005e0addeeff7b12f4', 'labelId': 'f5b4cf4773fc1010ae8dd21efaf6a766'}] |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create data classification clear

**Slug:** `SERVICENOW_CREATE_DATA_CLASSIFICATION_CLEAR`

Removes all data classifications for a specific record in a ServiceNow table. Use this action when you need to clear/reset data classification labels from a record, such as when reclassifying sensitive data, removing outdated classifications, or preparing records for re-processing. This action clears all data classification entries associated with the specified record. Note: This operation may require appropriate ServiceNow permissions. If the user lacks permission to modify data classifications on the specified table, an error will be returned.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the record whose data classifications should be cleared. This is a 32-character hexadecimal string that uniquely identifies the record. Example: 'abc1234567890abcdef1234567890ab' |
| `table_name` | string | Yes | The name of the ServiceNow table containing the record whose data classifications should be cleared. Examples: 'incident', 'problem', 'change_request', 'task', 'sc_request'. The table must exist in the ServiceNow instance and contain data classification fields. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Enhanced CI Identify/Reconcile

**Slug:** `SERVICENOW_CREATE_IDENTIFYRECONCILE_ENHANCED`

Inserts or updates configuration items (CIs) in ServiceNow CMDB using the enhanced Identification and Reconciliation API. Use this action when you need to bulk-insert or update multiple configuration items in the CMDB, with automatic identification of existing CIs based on identifying attributes (name, IP address, serial number, MAC address, hostname, or sys_id) and optional creation of CI relationships. This API provides better error handling and detailed per-item results compared to basic CMDB instance APIs. This action is useful for CMDB data population, reconciliation of discovered CIs against the CMDB, bulk CI updates, and establishing CI relationships during discovery or import workflows.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `items` | array | Yes | Array of configuration item (CI) objects to insert or update in the CMDB. Each item must have at least one identifying field (name, class_name, sys_id, ip_address, serial_number, mac_address, or host_name) to match an existing CI. If no existing CI matches, a new CI is created. The 'attributes' dict can be used to set or update CMDB fields on matched CIs. Example: [{'name': 'Server 01', 'className': 'cmdb_ci_server', 'ip_address': '192.168.1.100', 'attributes': {'operational_status': '1'}}] |
| `relations` | array | No | Array of relationship objects to create between CIs. Relationships are directional, defined as 'Source::Target' format. Each relation requires source and target CI identification (via sys_id, link, or name). Relations are processed after CIs. Example: [{'type': 'Runs on::Runs', 'source': {'name': 'App Server'}, 'target': {'name': 'DB Server'}}] |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Query CMDB Identify Reconcile

**Slug:** `SERVICENOW_CREATE_IDENTIFYRECONCILE_QUERY`

Queries the ServiceNow Identify and Reconcile API to determine whether a Configuration Item (CI) should be inserted (created) or updated in the CMDB based on identity matching rules. Use this action when you need to check whether a CI already exists in the CMDB before creating or updating it, or when you want ServiceNow to automatically determine the correct operation (INSERT vs UPDATE) based on configured identity matching rules and the provided attributes. This is commonly used during data migration, discovery integration, or bulk CI reconciliation workflows where the operation (create vs update) needs to be determined programmatically. Note: This action performs a query/reconciliation check only — it does not execute the actual INSERT or UPDATE operation. It returns the recommended operation and the matched CI details.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `source` | string | Yes | The name of the data source that identifies the origin of the CI data being reconciled. This is used by ServiceNow to determine which reconciliation rules and identity matching rules apply. The source must be a valid data source configured in ServiceNow (e.g., 'cmdb_azure', 'cmdb_aws', 'test_source'). Example: 'cmdb_azure' |
| `attributes` | object | Yes | A dictionary of attribute name-value pairs used to identify or match an existing CI. ServiceNow uses these attributes along with identity matching rules to determine whether an existing CI matches (triggering an update) or no match exists (triggering an insert). Common identifying attributes include: 'name' (CI display name), 'serial_number', 'ip_address', 'mac_address', 'host_name', 'fqdn', 'asset_tag'. Example: {'name': 'Test Server', 'ip_address': '192.168.1.100'} |
| `class_name` | string | Yes | The name of the CMDB class for the configuration item (CI) to identify/reconcile. Common CI classes include: 'cmdb_ci' (generic CI), 'cmdb_ci_server', 'cmdb_ci_database', 'cmdb_ci_network_adapter', 'cmdb_ci_storage_device', 'cmdb_ci_service_discovered', 'cmdb_ci_hardware', 'cmdb_ciPrinter', 'cmdb_ci_application', etc. Example: 'cmdb_ci' |
| `sysparm_display_value` | string | No | Determines the format of field values in the response. 'false': Returns actual database values (sys_ids for references, numeric values for choices). 'true': Returns display values (names for references, text labels for choices). 'all': Returns both display and actual values. |
| `sysparm_exclude_reference_link` | boolean | No | Set to true to exclude Table API links for reference fields in the response. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### CMDB Identify Reconcile QueryEnhanced

**Slug:** `SERVICENOW_CREATE_IDENTIFYRECONCILE_QUERYENHANCED`

Performs identification and reconciliation of configuration items (CIs) in the ServiceNow CMDB. Use this action when you need to determine whether to insert a new CI or update an existing one based on matching attributes. The API compares the provided data against existing CIs and returns the recommended operation (insert/update) along with the matched or created CI details. This is useful for data imports, discovery integration, or synchronizing CI data from external sources. Note: When dry_run is false (default), this action may create or modify existing CIs in the CMDB.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | A dictionary containing the configuration item (CI) attributes to reconcile. The available attributes depend on the CMDB class. Common attributes include: 'name' (CI display name, often required), 'u_class' or 'sys_class_name' (CMDB class), 'serial_number', 'ip_address', 'mac_address', 'host_name', 'fqdn', 'manufacturer', 'model_id', 'vendor', 'operational_status', 'install_status'. The API uses these attributes to match against existing CIs in the CMDB. Example: {'name': 'Production Server 01', 'u_class': 'cmdb_ci_server', 'ip_address': '192.168.1.100'} |
| `source` | string | Yes | The source identifier for the reconciliation query. This identifies the data source or integration point that is providing the CI data. Examples: 'cmdb_import_set', 'discovery', 'manual', or a custom integration name. |
| `dry_run` | boolean | No | When set to true, performs a simulation without actually creating or updating any CIs. Useful for previewing what changes would be made before committing. Default is false, meaning changes will be applied. |
| `reconciliation_type` | string | No | The type of reconciliation to perform. Determines how the API matches incoming data against existing CIs. Common values: 'exact' (exact match on all specified fields), 'fuzzy' (partial match), or 'identify' (identification only without creating/updating). If not specified, uses the default reconciliation behavior configured in ServiceNow. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Import Set

**Slug:** `SERVICENOW_CREATE_IMPORT`

Inserts incoming data into a specified ServiceNow staging table and triggers the associated transform map to move the data into the production table. Use this action when you need to bulk-import data into ServiceNow through the Import Set API. This is commonly used for data migration, integrating external data sources, or loading data from CSV files into ServiceNow tables. The staging table must have a transform map configured to map the staging table fields to the target production table fields.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `items` | array | Yes | List of data objects to import into the staging table. Each object contains field-value pairs corresponding to the columns in the staging table. The fields must match the columns defined in the staging table schema. Example: [{'short_description': 'Test item', 'description': 'Import test'}]. The data will be inserted into the staging table and the transform map associated with the staging table will be triggered to move data to the production table. |
| `staging_table_name` | string | Yes | Name of the import set staging table to insert data into. This is the name of a staging table (usually prefixed with 'u_') that is configured with a transform map to move data into a production table. Common staging table names include: 'u_test_import_set', 'u_incident_staging', 'u_cmdb_ci_staging', etc. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create incident

**Slug:** `SERVICENOW_CREATE_INCIDENT`

Creates a new incident record in ServiceNow with the provided details. Use this action when you need to log or report a new incident in ServiceNow, such as a service outage, system failure, or user-reported issue. The incident will be assigned a unique sys_id and incident number upon creation.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `category` | string | No | Category of the incident (e.g., 'network', 'hardware', 'software', 'database', 'inquiry'). |
| `priority` | string | No | Priority level of the incident. Valid values: 1 (Critical), 2 (High), 3 (Standard), 4 (Low), 5 (Planning). Higher priority values indicate lower urgency. |
| `caller_id` | string | No | sys_id of the user reporting the incident. Use the display name if sysparm_input_display_value is set to true. |
| `description` | string | No | Detailed description of the incident. Include steps to reproduce, error messages, and any other relevant details. |
| `subcategory` | string | No | Subcategory of the incident, further classifying the issue within the selected category. |
| `short_description` | string | Yes | Brief summary of the incident (required). This is a short description that identifies the incident. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Incident

**Slug:** `SERVICENOW_CREATE_INCIDENT1`

Creates a new incident record in ServiceNow with the provided field values. Use this action when you need to log or report a new incident in ServiceNow IT Service Management. The created incident is returned with its sys_id and auto-generated incident number. This action specifically targets the incident table and includes incident-specific fields like urgency, impact, severity, incident_state, and caller_id for proper incident management workflows.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `state` | string ("1" | "2" | "3" | "4" | "5" | "6" | "7" | "8") | No | ServiceNow incident state values |
| `active` | boolean | No | Whether the incident is active. Defaults to true for new incidents. |
| `impact` | string ("1" | "2" | "3" | "4") | No | ServiceNow impact levels - measures of business criticality |
| `cmdb_ci` | string | No | Configuration Item (CI) in the CMDB that is affected. |
| `urgency` | string ("1" | "2" | "3" | "4") | No | ServiceNow urgency levels - measure of business criticality |
| `category` | string | No | Category classification of the incident (e.g., 'Network', 'Hardware', 'Software', 'Database'). |
| `comments` | string | No | Additional comments about the incident, visible to end users. |
| `location` | string | No | Location of the caller or affected service. |
| `priority` | string ("1" | "2" | "3" | "4" | "5") | No | ServiceNow priority levels |
| `caller_id` | string | No | Person who reported or is affected by the incident. Can be a user sys_id or display value depending on sysparm_input_display_value setting. |
| `work_notes` | string | No | Internal work notes about the incident, not visible to end users. |
| `assigned_to` | string | No | Person primarily responsible for working this incident. Can be a user sys_id or display value. |
| `description` | string | No | Detailed description of the incident, including symptoms, steps to reproduce, and any relevant context. |
| `subcategory` | string | No | Subcategory within the main category (e.g., 'Firewall' under 'Network'). |
| `contact_type` | string | No | Method of contact used to report the incident (e.g., 'Phone', 'Email', 'Self-service', 'Chat'). |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response (e.g., 'number,sys_id,short_description,state'). Invalid fields are ignored. If not specified, all fields are returned. |
| `assignment_group` | string | No | Group assigned to handle the incident. Can be a group sys_id or display value. |
| `business_service` | string | No | Business service affected by the incident. |
| `short_description` | string | Yes | Brief summary of the incident. This field is required for most incident records. |
| `sysparm_display_value` | string ("true" | "false" | "all") | No | Determines the type of data returned in the response. 'false': Returns actual database values (sys_ids for references, numeric values for choices). 'true': Returns display values (names for references, text labels for choices). 'all': Returns both display and actual values. |
| `sysparm_input_display_value` | boolean | No | Set to true if providing display values (e.g., user names, group names) instead of sys_ids in caller_id, assigned_to, assignment_group, or other reference fields. When false (default), reference fields must contain sys_ids. |
| `sysparm_exclude_reference_link` | boolean | No | Set to true to exclude Table API links for reference fields in the response. This is recommended for cleaner responses. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create ServiceNow Interaction

**Slug:** `SERVICENOW_CREATE_INTERACTION`

Creates a new interaction record in ServiceNow that can be linked to records in other tables (e.g., incidents, problems, cases). Use this action when you need to log or create an interaction between a customer and service desk, such as recording a phone call, chat session, email exchange, or API-initiated interaction that should be tracked and associated with a specific table record. The interaction is created in the 'interaction' table (com.glide.interaction) and linked to the specified table_name record. If no table_name record exists yet, the interaction can still be created standalone.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `state` | string | No | Current state of the interaction (e.g., 'open', 'in_progress', 'closed', 'pending'). |
| `channel` | string ("api" | "phone" | "email" | "chat" | "portal" | "mobile" | "self_service") | No | The channel through which the interaction was initiated. Defaults to 'api' if not specified. |
| `message` | string | Yes | The main message or content of the interaction. This is a required field. |
| `priority` | string | No | Priority level of the interaction (e.g., '1' for critical, '2' for high, '3' for normal, '4' for low). |
| `caller_id` | string | No | sys_id of the user who initiated the interaction. If not provided, the interaction will be created with the authenticated user's information. |
| `table_name` | string | Yes | The name of the table to link the interaction to (e.g., 'incident', 'problem', 'task', 'sn_customerservice_case'). This determines what record type the interaction is associated with. |
| `assigned_to` | string | No | sys_id of the user to assign the interaction to. |
| `assignment_group` | string | No | sys_id of the group to assign the interaction to. |
| `short_description` | string | Yes | A brief summary or title describing the interaction. This is a required field. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Close Interaction

**Slug:** `SERVICENOW_CREATE_INTERACTION_CLOSE`

Closes an existing interaction record in ServiceNow by changing its state to closed. Use this action when you need to close or finalize an interaction that has been completed or resolved. This action changes the state of the interaction record to indicate that it is no longer active. Note: The interaction must be in a state that allows closing (e.g., not already closed). This action is typically used after an interaction has been handled and resolved. The body of the POST request can optionally include fields like 'state', 'opened_for', 'resolution_code', and 'resolution_notes' to provide additional context about the closure.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `state` | string | No | The state to set for the interaction when closing. Typically this would be a closed state value (e.g., 'closed', 'resolved'). If not provided, the default closed state from the system will be used. |
| `opened_for` | string | No | The sys_id of the user or entity for whom the interaction was originally opened. This field is used to track and attribute the interaction. Example: '681ccaf9c0a8016400b98fa0d0232157' |
| `interaction_id` | string | Yes | The unique system ID (sys_id) of the interaction record to close. This is a 32-character hexadecimal string that uniquely identifies the interaction record. Example: '87e3c4fa837bf210dd2dc2dfeeaad397' |
| `resolution_code` | string | No | Code indicating how the interaction was resolved. Common values include: 'resolved', 'escalated', 'transferred', 'cancelled'. This helps categorize the closure reason. |
| `resolution_notes` | string | No | Notes documenting the resolution of the interaction. This field is used to provide details about how the interaction was handled and closed. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create push installation

**Slug:** `SERVICENOW_CREATE_PUSH_INSTALLATION`

Registers or updates a device token for receiving push notifications through ServiceNow. Use this action when you need to register a mobile device token with ServiceNow's push notification system, enabling the device to receive push notifications from ServiceNow mobile apps. The action creates a new push installation or updates an existing one if the same token already exists for the specified push application. Common use cases: - Registering iOS devices for APNS push notifications - Registering Android devices for FCM push notifications - Updating existing device tokens when they change (token refresh) - Linking devices to specific ServiceNow users This action modifies the ServiceNow push notification registry — registered devices will be eligible to receive push notifications from ServiceNow.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `token` | string | Yes | The device token obtained from Apple Push Notification Service (APNS) for iOS devices or Firebase Cloud Messaging (FCM) for Android devices. This token identifies the device to receive push notifications. |
| `user_id` | string | No | The sys_id of the ServiceNow user associated with this device token. This links the device to a specific user for user-specific push notifications. |
| `platform` | string ("Apple" | "Android") | Yes | The mobile platform for the device token. Use 'Apple' for iOS devices (APNS) or 'Android' for Android devices (FCM). |
| `device_type` | string | No | The type of the mobile device (e.g., 'phone', 'tablet'). This field is optional and helps categorize devices for targeted notifications. |
| `subscription_id` | string | No | A unique identifier for the subscription. If not provided, a new subscription will be created or an existing one with the same token will be updated. |
| `push_application_name` | string | Yes | The name of the push application in ServiceNow (e.g., 'SkyNowPushApp'). This corresponds to the push application record configured in ServiceNow for handling push notifications to mobile devices. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Remove Push Installation

**Slug:** `SERVICENOW_CREATE_PUSH_REMOVE_INSTALLATION`

Deactivates a mobile device installation from receiving push notifications using the ServiceNow Push Installation API. Use this action when you need to remove a mobile device's ability to receive push notifications from a ServiceNow push application. This effectively deactivates the device token that enables communication between ServiceNow and the mobile app on the specified device. This is commonly used when: - A user uninstalls the mobile app from their device - A device needs to be unregistered from push notifications - Managing device registrations for push notification campaigns Note: This action only deactivates the device token - it does not delete any data from ServiceNow.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `token` | string | Yes | The unique device token that identifies the mobile device installation to remove. This token is assigned to a device when it registers with ServiceNow for push notifications. Deactivating this token will prevent the device from receiving push notifications from this application. Example: 'fcm_token_abc123' or 'apns_token_xyz789' |
| `platform` | string ("Apple" | "Android") | Yes | The mobile platform for the device token. Use 'Apple' for iOS devices (APNS) or 'Android' for Android devices (FCM). |
| `push_application_name` | string | Yes | The name of the push application whose device installation should be removed/deactivated. This is a path parameter in the URL, not a body parameter. The push application name identifies the mobile app configuration in ServiceNow. Example: 'ServiceNowPushApp' or 'snc_mobile_app'. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create servic catalog items add to cart

**Slug:** `SERVICENOW_CREATE_SERVIC_CATALOG_ITEMS_ADD_TO_CART`

Adds a specified catalog item to the current user's ServiceNow shopping cart. Use when a user wants to order or request a specific item from the Service Catalog, such as requesting a laptop, software license, or IT service. The item is added to the user's active shopping cart and can be reviewed or submitted in a later step. Note: The action operates on the authenticated user's cart. If the catalog item requires mandatory variables, they must be provided in the `variables` field, otherwise the request may fail.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the catalog item to add to the cart. This is a 32-character hexadecimal string that identifies the specific catalog item in ServiceNow. Example: '039c516237b1300054b6a3549dbe5dfc'. This is a required path parameter. |
| `variables` | object | No | Key-value pairs of catalog item variables to set when adding to cart. The variable names and expected values depend on the specific catalog item's variable definitions. For example, if the item has a 'model' variable, you might pass {'model': 'Laptop Model X'}. Omit this field if the catalog item does not require any variables. |
| `sysparm_quantity` | integer | No | The number of units of the catalog item to add to the shopping cart. Defaults to 1 if not specified. Must be a positive integer. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Submit Service Catalog Producer Item

**Slug:** `SERVICENOW_CREATE_SERVIC_CATALOG_ITEMS_SUBMIT_PRODUCER`

Submits a ServiceNow Service Catalog item using the submit_producer endpoint. This action submits a catalog item with the provided variables and returns the created record details. The submit_producer endpoint is typically used for producer-type catalog items (like change producers) that create records in other tables. Use this action when you need to submit a Service Catalog item that uses a producer script to create records. This is commonly used for change requests, service requests, or other workflow-triggering catalog items. The action returns the created record's details including the sys_id, table name, and record number. This permanently creates a record in the ServiceNow instance.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the catalog item to submit. This is a 32-character hexadecimal string that identifies the service catalog item. Example: '011f117a9f3002002920bde8132e7020'. You can find the sys_id by listing catalog items or navigating to the item in ServiceNow. |
| `variables` | object | No | A dictionary of catalog item variable name-value pairs to provide during submission. These are the variables defined on the catalog item that the user fills out when submitting. The variable names must match exactly as defined in the catalog item. Example: {'short_description': 'New laptop request', 'urgency': 'high', 'std_change_producer': '508e02ec47410200e90d87e8dee49058'} |
| `sysparm_display_value` | string | No | Determines the type of data returned in the response. 'true': Returns display values (names for references, text labels for choices). 'false': Returns actual database values (sys_ids for references, numeric values for choices). 'all': Returns both display and actual values. If not specified, defaults to the instance setting. |
| `sysparm_no_validation` | boolean | No | Set to true to skip variable validation during submission. When false (default), ServiceNow validates all required variables before accepting the submission. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Checkout Service Catalog Cart

**Slug:** `SERVICENOW_CREATE_SERVICE_CATALOG_CART_CHECKOUT`

Checks out the Service Catalog shopping cart and submits the order as a request. This action retrieves the items in the cart, creates a service catalog request, deletes the cart contents, and returns the request ID and number for tracking. The cart is emptied after successful checkout. This action is irreversible once the checkout is completed — the order has been submitted and cannot be cancelled through this action. Use this action when you need to finalize a Service Catalog order by submitting all items in the shopping cart for processing and approval.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `cart_id` | string | No | The unique system ID (sys_id) of the Service Catalog shopping cart to checkout. This is a 32-character hexadecimal string that uniquely identifies the cart record. Example: '8df4cc7a83bbf210dd2dc2dfeeaad380'. If not provided, the current user's default cart will be used. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Submit Service Catalog Cart Order

**Slug:** `SERVICENOW_CREATE_SERVICE_CATALOG_CART_SUBMIT_ORDER`

Submits the Service Catalog shopping cart and creates a service catalog request. This action checks out the user cart, creates a service catalog request with all items in the cart, and returns the request ID and number for tracking. The cart contents are converted into a submitted order. This action is irreversible once submitted — the order has been created and cannot be cancelled through this action. Use this action when you need to finalize a Service Catalog order by submitting all items in the shopping cart for processing and approval. This is typically called after items have been added to the cart using other cart operations.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `cart_id` | string | No | The unique system ID (sys_id) of the Service Catalog shopping cart to submit. This is a 32-character hexadecimal string that uniquely identifies the cart record. Example: '8df4cc7a83bbf210dd2dc2dfeeaad380'. If not provided, the current user's active cart will be used. |
| `quantity` | integer | No | The quantity of items to order. If specified, applies to all items in the cart. Defaults to 1 if not specified. |
| `variables` | object | No | Dictionary of catalog item variables (answers) to set during submission. The keys should be the variable IDs (not the labels) as defined in the catalog item. Example: {'reason': 'New laptop needed', 'location': 'NYC'} |
| `ignore_price` | boolean | No | Set to true to ignore price changes that may have occurred since items were added to cart. When false (default), the order may fail if prices have changed. |
| `requested_for` | string | No | The user ID (sys_id or username) to submit the order on behalf of. Use this parameter when submitting an order for another user. Example: '681ccaf9c0a8016400b98a908cbe7df3' or 'john.doe' |
| `no_attachment_found_warnings` | boolean | No | Set to true to suppress warnings when required attachments are missing. The order will still be submitted even if warnings would normally be generated. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create servicecatalog items checkout guide

**Slug:** `SERVICENOW_CREATE_SERVICECATALOG_ITEMS_CHECKOUT_GUIDE`

Checks out an order guide by updating variable values for selected catalog items. Use this action when a user needs to submit an order guide in ServiceNow's Service Catalog, providing variable values for the items within the order guide. The action retrieves the configured contents of the order guide with the submitted variable values applied. This is commonly used during the checkout process for order guides that contain pre-configured sets of catalog items (e.g., laptop requests, software bundles). The action sends a POST request with the order guide sys_id and variable values, and returns an array of catalog items included in the order guide checkout.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the order guide to check out. This is a 32-character hexadecimal string that uniquely identifies the order guide item. Example: '25110912372211003e7d40ed9dbe5dd6'. The order guide must be active and available in the Service Catalog. |
| `variables` | object | No | Variable values for all selected catalog items within the order guide. Keys are the variable names/IDs and values are the corresponding values to set. The required variables depend on the specific order guide configuration. Common variable types include text inputs, checkboxes, dropdowns, and reference fields. All values should be provided as strings. Example: {'requested_for': '2024-01-15', 'quantity': '1', 'urgency': 'high'} |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Order Service Catalog Item Now

**Slug:** `SERVICENOW_CREATE_SERVICECATALOG_ITEMS_ORDER_NOW`

Orders a specified ServiceNow Service Catalog item immediately. This action submits an order for a catalog item without requiring cart checkout. The item is ordered directly with the specified quantity and optional variables. Use this action when you need to quickly order a known catalog item for a user. Use when you have a catalog item's sys_id and want to order it directly without adding it to a cart first. This action is useful for automated provisioning of standard items like laptop requests, software access, or access cards.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the catalog item to order. This is a 32-character hexadecimal string that identifies the service catalog item. Example: '04b7e94b4f7b4200086eeed18110c7fd'. You can find the sys_id by listing catalog items or navigating to the item in ServiceNow. |
| `variables` | object | No | A dictionary of catalog item variable name-value pairs to provide during ordering. These are the variables defined on the catalog item that the user fills out at order time. The variable names must match exactly as defined in the catalog item. Example: {'reason': 'New laptop needed', 'urgency': 'high'} |
| `sysparm_quantity` | integer | No | The number of instances of the catalog item to order. Must be a positive integer. Defaults to 1 if not specified. |
| `sysparm_requested_for` | string | No | The user ID (sys_id) of the person for whom the item is being ordered. If not specified, the item is ordered for the current user. Example: '681ccaf9c0a8016400b98a06818d57a7' (sys_id of a user). |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Insert Multiple Import Set Records

**Slug:** `SERVICENOW_CREATE_SERVICENOW_IMPORT_INSERTMULTIPLE`

Inserts multiple records into a specified ServiceNow staging table and triggers the associated transform map. Use this action when you need to bulk-import data into ServiceNow via an Import Set. Records are inserted into the specified staging table, then processed by the transform map which maps staging fields to target table fields. This provides improved scalability and stability over inserting records one at a time. The staging table name identifies the import set staging table (e.g., 'sys_import_set_row'), and the transform map associated with that table determines how each record is transformed and loaded into the target table.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `records` | array | Yes | Array of record objects to insert into the staging table. Each record contains field-value pairs matching the columns of the staging table. These records will be queued for transform based on the transform map associated with the staging table. Example: [{'short_description': 'Test record 1'}, {'short_description': 'Test record 2'}] |
| `staging_table_name` | string | Yes | Name of the import set staging table to insert records into. Examples: 'sys_import_set_row', 'u_staging_incident', 'sys_import_tst_abc123'. This is a path parameter that identifies the staging table. |
| `sysparm_input_display_value` | boolean | No | Set to true if providing display values instead of sys_ids for reference fields in the records. When false (default), reference fields must contain sys_ids. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create sn chg rest change

**Slug:** `SERVICENOW_CREATE_SN_CHG_REST_CHANGE`

Creates a new change request in ServiceNow using the Change Management REST API. Use this action when you need to create and submit a new change request for approval and implementation. The action supports specifying change details such as short description, description, category, type, priority, risk, and impact. After creation, the change request will have a unique sys_id and number that can be used to retrieve, update, or delete it in subsequent operations.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `risk` | string | No | Risk level of the change request (e.g., 'low', 'medium', 'high', 'critical'). |
| `type` | string | No | Type of change request (e.g., 'normal', 'standard', 'emergency'). |
| `phase` | string | No | Current phase of the change request workflow (e.g., 'Planning', 'Assessment', 'Implementation'). |
| `impact` | string | No | Impact level of the change request (typically 1-3, where 1 is highest). |
| `vendor` | string | No | Vendor associated with the change request. |
| `cmdb_ci` | string | No | Sys_id of the Configuration Item associated with the change. |
| `company` | string | No | Sys_id of the company associated with the change request. |
| `category` | string | No | Category classification of the change request (e.g., 'Network', 'Hardware', 'Software', 'Communication'). |
| `comments` | string | No | Comments visible to end users. |
| `contract` | string | No | Contract reference or identifier associated with the change. |
| `location` | string | No | Sys_id of the location associated with the change request. |
| `priority` | string | No | Priority level of the change request (typically 1-5, where 1 is highest). |
| `test_plan` | string | No | Plan for testing the change after implementation. |
| `department` | string | No | Sys_id of the department associated with the change request. |
| `work_notes` | string | No | Internal work notes (not visible to end users). |
| `assigned_to` | string | No | Sys_id of the user to assign the change request to. |
| `close_notes` | string | No | Notes to be added when closing the change request. |
| `description` | string | No | Detailed description explaining what the change involves, its purpose, and expected outcomes. |
| `subcategory` | string | No | Subcategory classification within the main category. |
| `backout_plan` | string | No | Plan for rolling back the change if issues occur. |
| `expected_end` | string | No | Expected end date and time for the change (ISO 8601 format recommended). |
| `requested_by` | string | No | Sys_id of the user who requested the change. |
| `justification` | string | No | Business justification explaining why this change is needed. |
| `expected_start` | string | No | Expected start date and time for the change (ISO 8601 format recommended). |
| `on_hold_reason` | string | No | Reason for placing the change request on hold. |
| `assignment_group` | string | No | Sys_id of the group to assign the change request to. |
| `planned_end_date` | string | No | Planned end date and time for the change (format: YYYY-MM-DD HH:MM:SS or ISO 8601). |
| `service_offering` | string | No | Sys_id of the service offering related to the change. |
| `requested_by_date` | string | No | Date by which the change is requested (format: YYYY-MM-DD HH:MM:SS or ISO 8601). |
| `short_description` | string | No | Brief summary or title of the change request (recommended, displayed in lists). |
| `planned_start_date` | string | No | Planned start date and time for the change (format: YYYY-MM-DD HH:MM:SS or ISO 8601). |
| `implementation_plan` | string | No | Detailed plan for implementing the change. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Change Request CI Association

**Slug:** `SERVICENOW_CREATE_SN_CHG_REST_CHANGE_CI`

Creates an association between a change request and one or more configuration items (CIs) in ServiceNow. Use this action when you need to link CIs (servers, databases, applications, etc.) to a change request in ServiceNow's Change Management module. This is commonly used to: - Define which infrastructure components are affected by a change - Include specific CIs in the scope of a change request - Track and manage CI relationships for change planning The action requires the change request sys_id and a list of CI sys_ids to associate.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the change request. This is a 32-character hexadecimal string that uniquely identifies the change request record. Example: '46e9b4afa9fe198101026e122b85f442' |
| `cmdb_ci_sys_ids` | array | Yes | List of sys_ids of the Configuration Items (CIs) to associate with the change request. Each sys_id is a 32-character hexadecimal string that uniquely identifies a CI record in the CMDB. Example: ['00a96c0d3790200044e0bfc8bcbe5db4'] |
| `association_type` | string ("affected" | "requested" | "requested_and_affected") | No | Type of CI association with the change request. 'affected': The CI is affected by the change request. 'requested': The CI is requested to be included in the change request. 'requested_and_affected': The CI is both requested and affected. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Start Change Conflict Check

**Slug:** `SERVICENOW_CREATE_SN_CHG_REST_CHANGE_CONFLICT`

Starts the conflict checking process for a ServiceNow change request, identifying scheduling conflicts with other changes or blackout windows. Use this action when you need to initiate a conflict check for a change request. This is typically used to verify that a change request doesn't conflict with other scheduled changes or fall within a blackout window. This is commonly used before approving or implementing a change to ensure proper scheduling and avoid resource conflicts. Note: This action starts the conflict check process asynchronously. Use the GetChangeConflict action to retrieve the results of the conflict check once it completes.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the change request to start conflict checking for. This is a 32-character hexadecimal string that uniquely identifies the change request. Example: '46e9b4afa9fe198101026e122b85f442' |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create sn chg rest change emergency

**Slug:** `SERVICENOW_CREATE_SN_CHG_REST_CHANGE_EMERGENCY`

Creates an emergency change request in ServiceNow using the Change Management API. Use this action when you need to create an expedited change request that requires urgent approval and implementation due to critical business requirements or emergency situations. Emergency changes bypass standard approval workflows to enable rapid response to urgent needs. This action creates a new emergency change request record and returns the generated sys_id and change request number for future reference.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `reason` | string | No | Reason for the emergency change request explaining the urgency |
| `cmdb_ci` | string | No | Sys_id of the affected Configuration Item (CI) in CMDB |
| `description` | string | No | Full description of the emergency change request providing detailed context |
| `short_description` | string | Yes | Short description of the emergency change request |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Normal Change Request

**Slug:** `SERVICENOW_CREATE_SN_CHG_REST_CHANGE_NORMAL`

Creates a normal change request in ServiceNow using the Change Management REST API. Use when you need to create a standard change request that follows the normal approval workflow. Normal changes are subject to standard CAB (Change Advisory Board) review and approval processes before implementation. This action is appropriate for planned changes that can follow the normal change lifecycle. This action creates a new normal change request record and returns the generated sys_id and change request number for future reference and tracking.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `cmdb_ci` | string | No | Sys_id of the affected Configuration Item (CI) in CMDB |
| `description` | string | No | Full description of the normal change request providing detailed context |
| `assignment_group` | string | No | Sys_id of the assignment group responsible for implementing the change |
| `short_description` | string | Yes | Short description of the normal change request |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create sn chg rest change standard

**Slug:** `SERVICENOW_CREATE_SN_CHG_REST_CHANGE_STANDARD`

Creates a new standard change request in ServiceNow using a pre-approved standard change template. Use this action when you need to create a standard change request based on a predefined template from the std_change_record_producer table. Standard changes follow a pre-approved workflow and are typically lower-risk changes that follow standardized procedures defined by the organization. The template_id parameter should be the sys_id of an active standard change template. This action creates a new change request record populated with the fields defined in the template.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `template_id` | string | Yes | The sys_id of the standard change template to use for creating the change request. This is a 32-character hexadecimal string that uniquely identifies the template in the std_change_record_producer table. Example: '1234567890abcdef1234567890abcdef' |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Change Task

**Slug:** `SERVICENOW_CREATE_SN_CHG_REST_CHANGE_TASK`

Creates a new task for a ServiceNow change request using the Change Management REST API. Use this action when you need to add a new task or subtask to an existing change request, such as breaking down a change into smaller work items, assigning specific work to team members, or tracking additional work needed as part of the change process. The task will be automatically linked to the specified change request. After creation, use the returned sys_id to update or retrieve the task as needed.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `state` | string | No | Initial state of the task. Common values: -5=Cancelled, -4=On hold, -3=Rejected, -2=Pending, -1=Draft, 1=Open, 2=Work In Progress, 3=Pending, 4=Complete. If not specified, defaults to the task type's default state. |
| `category` | string | No | Category or type of the task |
| `comments` | string | No | Public comments on the task (visible to end users) |
| `priority` | string | No | Priority level of the task (e.g., '1' for critical, '2' for high, '3' for moderate, '4' for low, '5' for planning) |
| `work_notes` | string | No | Internal work notes for the task (visible to IT staff only) |
| `assigned_to` | string | No | sys_id of the user assigned to the task |
| `description` | string | No | Full description of the task |
| `expected_end` | string | No | Expected end date and time of the task (ISO 8601 format) |
| `change_sys_id` | string | Yes | The unique system ID (sys_id) of the change request to create a task for. This is a 32-character hexadecimal string that uniquely identifies the change request. Example: '46e9b4afa9fe198101026e122b85f442'. The change request must exist, or a 404 error will be returned. |
| `expected_start` | string | No | Expected start date and time of the task (ISO 8601 format) |
| `on_hold_reason` | string | No | Reason the task is on hold (use with state=-4) |
| `assignment_group` | string | No | sys_id of the group assigned to the task |
| `short_description` | string | Yes | Brief summary or title of the task |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create sn cicd app batch install

**Slug:** `SERVICENOW_CREATE_SN_CICD_APP_BATCH_INSTALL`

Installs two or more ServiceNow application packages in a single batch operation via the CICD API. Use this action when you need to deploy multiple applications at once as part of a CI/CD pipeline or automated deployment process. The batch install allows for efficient bulk installation of related applications rather than installing them one at a time. This action is idempotent — running it multiple times with the same packages will produce the same result. Note: At least two packages must be specified for a batch install operation.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | Yes | The name or label for this batch install operation. This is used for identification purposes. |
| `packages` | array | Yes | List of packages to install in a single batch operation. Each package must have a 'name' field containing the application ID. At least two packages are required for batch installation. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Install App from Repository

**Slug:** `SERVICENOW_CREATE_SN_CICD_APP_REPO_INSTALL`

Installs the specified application from the ServiceNow app repository. Use this action when you need to install an application from the ServiceNow Store or a private app repository onto your ServiceNow instance. This is commonly used during CI/CD pipelines to automate the deployment of applications. The action requires the sys_id of the application to install, which can be obtained from the app repository records or from a previous application listing operation.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The sys_id of the application to install from the app repository. This is the unique system identifier for the application record in ServiceNow. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Run Full Instance Scan

**Slug:** `SERVICENOW_CREATE_SN_CICD_INSTANCE_SCAN_FULL_SCAN`

Initiates a full instance scan by running all active checks present in the ServiceNow instance. Use this action when you need to execute a comprehensive validation scan of your ServiceNow instance, running all configured active checks to identify configuration issues, best practice violations, or compliance problems. This is typically used during CI/CD pipelines or before major changes to ensure the instance meets required standards. This action starts an asynchronous scan operation - the response indicates the scan has been initiated with a 'running' state. Use the returned sys_id to track progress or retrieve detailed results.

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create sn cicd instance scan suite scan combo

**Slug:** `SERVICENOW_CREATE_SN_CICD_INSTANCE_SCAN_SUITE_SCAN_COMBO`

Runs a CI/CD scan using a suite and target (scoped app) combination in ServiceNow. Use this action when you need to execute a compliance or best practices scan against a scoped application using a predefined scan suite and target combination. This is commonly used in CI/CD pipelines to validate that an application meets ServiceNow best practices before deployment or release. The combo_sys_id refers to a saved configuration that links a scan suite with a target scoped application. You can optionally override the target by providing target_scope_app_sys_id. This action modifies the ServiceNow instance by executing a scan. If async_execution is false (default), the request will wait for the scan to complete. Set async_execution to true if you want the scan to run in the background and return immediately.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `combo_sys_id` | string | Yes | The unique system ID (sys_id) of the scan suite and target combination to run. This is a 32-character hexadecimal string that identifies the combo configuration containing the suite and target (scoped app) to scan. Example: 'a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4' |
| `async_execution` | boolean | No | When set to true, the scan runs asynchronously and returns immediately with a job ID. When false (default), the request waits for the scan to complete before returning. |
| `target_scope_app_sys_id` | string | No | The sys_id of the scoped application to run the scan against. If not provided, the target defined in the combo configuration will be used. Example: 'f6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1' |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Activate Plugin

**Slug:** `SERVICENOW_CREATE_SN_CICD_PLUGIN_ACTIVATE`

Activates the specified plugin in ServiceNow's CICD Plugin API. Use this action when you need to activate a plugin on a ServiceNow instance as part of a CI/CD pipeline or automated deployment process. This is commonly used after deploying a plugin to enable its functionality on the target instance. This action modifies the state of the ServiceNow instance by activating the plugin. Ensure the plugin is compatible with your instance and that any prerequisites are met before activation.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `plugin_id` | string | Yes | The unique identifier or name of the plugin to activate. This is typically the plugin's scope name or full identifier (e.g., 'com.glide.cs', 'com.snc.pdap'). |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Run Test Suite

**Slug:** `SERVICENOW_CREATE_SN_CICD_TESTSUITE_RUN`

Starts a specified automated test suite using ServiceNow's CI/CD Pipeline API. Use this action when you need to execute an automated test suite as part of a CI/CD pipeline or deployment process. This action initiates the test suite run and returns a progress identifier that can be used with GetSnCicdProgress to monitor execution status. The action is commonly used during automated testing phases in deployment pipelines to validate application changes before production deployment.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `test_suite_id` | string | Yes | The unique identifier of the test suite to run. This is the sys_id or name of the automated test suite record in ServiceNow. Example: 'test-123' or a system-generated GUID |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create SD-WAN Trouble Ticket

**Slug:** `SERVICENOW_CREATE_SN_IND_TSM_SDWAN_TROUBLETICKET`

Creates a new trouble ticket in ServiceNow using the Service Operations Workspace Trouble Ticket Open API. Use this action when you need to create a new SD-WAN or network-related trouble ticket for tracking and resolution. This action sends a POST request to the sn_ind_tsm_sdwan trouble ticket API, creating a record in the Case or other configured ticket table. After creation, the ticket will have a unique sys_id and number that can be used to retrieve, update, or close it in subsequent operations. This action is specifically for the Service Operations Workspace / Service Management SD-WAN integration's trouble ticket creation functionality.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `category` | string | No | Category or classification of the trouble ticket. Example categories: 'Network', 'Hardware', 'Software', 'Security'. The exact categories depend on your ServiceNow configuration. |
| `priority` | string | No | Priority level of the trouble ticket. Typical values: 1 = Critical (service down), 2 = High (major impact), 3 = Medium (moderate impact), 4 = Low (minor impact). The exact priority values depend on your ServiceNow configuration. |
| `caller_id` | string | No | Sys_id of the user who reported or initiated the trouble ticket. This is the 32-character hexadecimal string that identifies the user. Example: 'usr123abc456def789ghi012jkl345' |
| `work_notes` | string | No | Internal work notes about the trouble ticket. These notes are only visible to users with appropriate roles and are not visible to end users or customers. Use this for technical details and updates. Example: 'Investigated the issue and identified root cause as faulty switch' |
| `assigned_to` | string | No | Sys_id of the user assigned to handle the trouble ticket. This is the 32-character hexadecimal string that identifies the user. Example: 'usr789xyz012abc345def678ghi901' |
| `description` | string | No | Full detailed description of the trouble ticket, including symptoms, impact, and any relevant background information. Example: 'Users unable to access the corporate network since 9 AM' |
| `subcategory` | string | No | Subcategory of the trouble ticket for more specific classification. Example subcategories: 'Firewall', 'Router', 'Switch', 'VPN'. The exact subcategories depend on your ServiceNow configuration. |
| `ticket_type` | string | Yes | The type of trouble ticket to create. Common values include 'case', 'incident', or other ticket types supported by your ServiceNow Service Operations Workspace SD-WAN configuration. Example: 'case' |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response. Invalid fields are ignored. If not specified, all fields are returned. Example: 'number,short_description,state,assigned_to' |
| `assignment_group` | string | No | Sys_id of the group assigned to handle the trouble ticket. This is the 32-character hexadecimal string that identifies the group. Example: 'grp456def789ghi012jkl345mno678' |
| `short_description` | string | No | Brief summary or title of the trouble ticket. This describes the issue or request in a concise manner. Example: 'Network connectivity issue in DC1' |
| `sysparm_display_value` | string ("true" | "false" | "all") | No | Determines the type of data returned in the response. 'false': Returns actual database values (sys_ids for references, numeric values for choices). 'true': Returns display values (names for references, text labels for choices). 'all': Returns both display and actual values. |
| `sysparm_input_display_value` | boolean | No | Set to true if providing display values (e.g., user names) instead of sys_ids in record_data for reference fields. When false (default), reference fields must contain sys_ids. |
| `sysparm_exclude_reference_link` | boolean | No | Set to true to exclude Table API links for reference fields in the response. Use this to reduce response size when reference links are not needed. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create TMF Service Category

**Slug:** `SERVICENOW_CREATE_SN_TMF_SERVICE_CATEGORY`

Creates a new service category record in the ServiceNow TMF Service Catalog API. This action calls the POST /api/sn_tmf_api/catalogmanagement/serviceCategory endpoint to create a top-level or nested service category within the ServiceNow Service Catalog. Use this action when you need to organize items in the service catalog into categories, enabling better navigation and grouping of related catalog offerings. Use this action when you need to add a new category to the ServiceNow Service Catalog for organizing catalog items such as requested items, record producers, or other offerings. For root categories, set is_root=true. For subcategories, provide the parent_id of the existing parent category. If the category name already exists within the same parent scope, the API may return a conflict error.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | Yes | Name of the service category. This is a required field and should be a descriptive label for the category (e.g., 'Hardware Services', 'Software Requests'). Category names should be unique within the same parent scope. |
| `is_root` | boolean | No | Indicates whether this category is a root-level (top-level) category. Set to true to create a top-level category with no parent. Set to false (or omit) to create a subcategory under an existing parent. When true, parent_id should not be provided. |
| `parent_id` | string | No | The unique identifier of the parent service category. Required when creating a subcategory (is_root=false or omitted). Should be omitted or left empty when is_root=true. The parent category must exist, or the API will return an error. |
| `description` | string | No | Detailed description of the service category explaining its purpose, scope, and what types of items it contains. Use this to provide additional context for users browsing the service catalog. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create table

**Slug:** `SERVICENOW_CREATE_TABLE`

Inserts a new record into the specified ServiceNow table with the provided field values. Use this action when you need to create a new record in any ServiceNow table (e.g., incident, problem, change_request, task, sys_user). The created record is returned with its sys_id and auto-generated number. NOTE: This action uses the /api/now/table/ endpoint as documented. The existing CreateARecord action uses /api/now/v1/table/.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `table_name` | string | Yes | The name of the table where the record will be created (e.g., 'incident', 'problem', 'change_request', 'sys_user'). |
| `record_data` | object | No | Field-value pairs for the new record. Available fields depend on the table schema. For 'incident' table, common fields include: 'short_description', 'description', 'urgency' (1-3), 'impact' (1-3), 'priority', 'assignment_group', 'assigned_to', 'category', 'state'. For reference fields (like 'assignment_group' or 'assigned_to'), use the sys_id of the referenced record, or set sysparm_input_display_value=true to use display values. Example: {'short_description': 'Network outage', 'urgency': '1', 'impact': '1', 'description': 'Unable to access network'} |
| `sysparm_view` | string ("desktop" | "mobile" | "both") | No | UI view to determine which fields are returned in the response. If not specified, returns fields from the default view. |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response (e.g., 'number,short_description,state'). Invalid fields are ignored. If not specified, all fields are returned. |
| `sysparm_display_value` | string ("true" | "false" | "all") | No | Determines the type of data returned in the response. 'false': Returns actual database values (sys_ids for references, numeric values for choices). 'true': Returns display values (names for references, text labels for choices). 'all': Returns both display and actual values. |
| `sysparm_input_display_value` | boolean | No | Set to true if providing display values (e.g., user names) instead of sys_ids in record_data for reference fields. When false (default), reference fields must contain sys_ids. |
| `sysparm_exclude_reference_link` | boolean | No | Set to true to exclude Table API links for reference fields in the response. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create ServiceNow Incident

**Slug:** `SERVICENOW_CREATE_TABLE_INCIDENT`

Creates a new incident record in the ServiceNow incident table using the Table API. Use this action when you need to create a new incident in ServiceNow, such as logging IT service disruptions, reporting bugs, or tracking system issues. The action accepts incident-specific fields like short_description, description, priority, impact, urgency, and assignment information. The created incident is returned with its auto-generated sys_id and display number (e.g., INC0010001). This action is specifically designed for the incident table and provides a more focused and intuitive interface compared to the generic table creation endpoint.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `state` | string ("1" | "2" | "3" | "6" | "7" | "8") | No | Incident state values |
| `impact` | string ("1" | "2" | "3" | "4") | No | Impact levels for incident records |
| `cmdb_ci` | string | No | Sys_id of the Configuration Item (CI) affected by this incident. |
| `company` | string | No | Sys_id of the company associated with this incident. |
| `urgency` | string ("1" | "2" | "3" | "4") | No | Urgency levels for incident records |
| `category` | string | No | Category of the incident (e.g., 'Inquiry', 'Problem', 'Software', 'Hardware', 'Network'). |
| `comments` | string | No | Additional comments or notes about the incident that are visible to end users. |
| `location` | string | No | Sys_id of the location where the incident occurred. |
| `priority` | string ("1" | "2" | "3" | "4" | "5") | No | Priority levels for incident records |
| `caller_id` | string | No | Sys_id of the user who reported the incident. If not provided, the current user is used as the caller. |
| `watch_list` | string | No | Comma-separated list of user sys_ids who should receive notifications about this incident. |
| `work_notes` | string | No | Internal work notes visible only to support staff, not to end users. |
| `assigned_to` | string | No | Sys_id of the user assigned to work on the incident. |
| `description` | string | No | Detailed description of the incident including steps to reproduce, error messages, and any relevant context. |
| `subcategory` | string | No | Subcategory of the incident within the selected category. |
| `contact_type` | string | No | Method by which the incident was reported (e.g., 'Phone', 'Email', 'Self-service', 'Walk-in'). |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response (e.g., 'number,sys_id,state'). Invalid fields are ignored. |
| `assignment_group` | string | No | Sys_id of the group to which the incident is assigned. |
| `business_service` | string | No | Sys_id of the business service affected by this incident. |
| `short_description` | string | Yes | Brief summary of the incident. This field is required and should clearly describe the issue. |
| `sysparm_display_value` | string | No | Determines the format of field values in the response. 'false' returns actual values (default), 'true' returns display values, 'all' returns both. |
| `sysparm_exclude_reference_link` | boolean | No | Set to true to exclude Table API links for reference fields in the response. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create or Update CMDB CI via IRE

**Slug:** `SERVICENOW_CREATE_UPDATE_CMD_CI`

Creates or updates CMDB configuration items (CIs) using the ServiceNow Identification and Reconciliation Engine (IRE) via the identify-reconcile endpoint. Use this action when you need to upsert CIs into the CMDB with automatic deduplication. The IRE matches incoming CI data against existing records using configured identification rules (based on fields like name, IP address, serial number, etc.) and either updates the matched CI or creates a new one. This prevents duplicate configuration items from being created. You can also submit relationship data alongside CIs to create or update CI relationships (e.g., 'Contains', 'Depends on'). Note: Identification rules must be configured in ServiceNow for this endpoint to work correctly. If no matching rule is found, the IRE may create a new CI or reject the entry depending on your configuration.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `items` | array | Yes | Array of CI objects to insert or update in the CMDB using the Identification and Reconciliation Engine (IRE). Each object contains CMDB fields that are used both for matching (via identification rules) and for populating CI attributes. Key fields include: 'className' (CMDB table name), 'name' (CI display name), 'sys_id' (to update an existing CI directly), 'ip_address', 'serial_number', 'host_name', 'mac_address', 'fqdn', 'manufacturer', 'model_id', etc. The IRE matches incoming CIs against existing records using identification rules configured in ServiceNow, preventing duplicate CIs. Example: [{'className': 'cmdb_ci', 'name': 'test-ci', 'ip_address': '192.168.1.100'}] |
| `relations` | array | No | Array of relationship objects to create or update alongside the CIs. Each relation links a parent CI to a child CI with a relationship type. Fields include: 'parent' (sys_id or name of parent CI), 'child' (sys_id or name of child CI), 'type' (relationship type name). Example: [{'parent': 'web-server-01', 'child': 'web-app-01', 'type': 'Contains'}] |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete a record

**Slug:** `SERVICENOW_DELETE_A_RECORD`

Permanently deletes a specific record from a ServiceNow table using its sys_id. This is a destructive operation that cannot be undone. The record will be permanently removed from the table. Requires the user to have delete permissions on the specified table. If the record doesn't exist or the user lacks permissions, an error will be returned. Common use cases: Removing test data, cleaning up duplicate records, deleting obsolete incidents/problems/tasks.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the record to delete. This is a 32-character hexadecimal string that uniquely identifies the record. Example: '8866498dc37a3610eb10d8477d013161'. The record must exist in the specified table, or a 404 error will be returned. |
| `table_name` | string | Yes | Name of the ServiceNow table from which to delete the record (e.g., 'incident', 'problem', 'change_request', 'task'). The table must exist in the ServiceNow instance and the user must have delete permissions for it. |
| `sysparm_query_no_domain` | boolean | No | Set to true to include records from domains the logged-in user is not configured to access (requires admin or query_no_domain_table_api role). When false (default), only records in the user's configured domains can be deleted. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete attachment by

**Slug:** `SERVICENOW_DELETE_ATTACHMENT_BY_ID`

Permanently deletes a specific attachment from ServiceNow using its sys_id. This is a destructive, irreversible operation — the attachment cannot be recovered once deleted. Requires the user to have delete permissions on the attachment. If the attachment doesn't exist or the user lacks permissions, an error will be returned. This action should be used when you have the specific sys_id of an attachment to remove (obtained from FindFile action). Use when you need to remove a specific file attachment from a record and know its sys_id.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the attachment to delete. This is a 32-character hexadecimal string that uniquely identifies the attachment record in ServiceNow. Example: '003a3ef24ff1120031577d2ca310c74b'. The attachment must exist, or a 404 error will be returned. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete attachment by id v1

**Slug:** `SERVICENOW_DELETE_ATTACHMENT_BY_ID_V1`

Permanently deletes a specific attachment from ServiceNow using its sys_id via the v1 API endpoint. This is a destructive, irreversible operation — the attachment cannot be recovered once deleted. Requires the user to have delete permissions on the attachment record. If the attachment does not exist or the user lacks permissions, an error will be returned. This action uses the /api/now/v1/attachment/{sys_id} endpoint specifically. Use when you need to remove a specific file attachment from a record and already know its sys_id.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the attachment to delete. This is a 32-character hexadecimal string that uniquely identifies the attachment record in ServiceNow. Example: '00e7525ddf710100a9e78b6c3df2639c'. The attachment must exist, or a 404 error will be returned. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete attachment csm

**Slug:** `SERVICENOW_DELETE_ATTACHMENT_CSM`

Permanently deletes a specific CSM (Customer Service Management) attachment from ServiceNow using its sys_id. This is a destructive, irreversible operation — the CSM attachment cannot be recovered once deleted. Requires the user to have delete permissions on the attachment. If the attachment doesn't exist or the user lacks permissions, an error will be returned. This action specifically targets attachments associated with CSM records (cases, etc.). Use when you need to remove a specific file attachment from a CSM record and know its sys_id.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the CSM attachment to delete. This is a 32-character hexadecimal string that uniquely identifies the attachment record in ServiceNow. Example: '260380fa833bf210dd2dc2dfeeaad3c1'. The attachment must exist, or a 404 error will be returned. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete change task

**Slug:** `SERVICENOW_DELETE_CHANGE_TASK`

Permanently deletes a specific task from a ServiceNow change request using its sys_id. This is a destructive, irreversible operation. The task will be permanently removed from the change request and cannot be recovered once deleted. Use this action with caution. Requires the user to have appropriate permissions to delete tasks from change requests. If the change request or task doesn't exist, or if the user lacks permissions, an error will be returned. Use this action when you need to clean up obsolete or incorrect tasks from change requests.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `task_sys_id` | string | Yes | The unique system ID (sys_id) of the task to delete from the change request. This is a 32-character hexadecimal string that uniquely identifies the task. Example: 'd262847a833bf210dd2dc2dfeeaad353'. The task must exist within the specified change request, or a 404 error will be returned. |
| `change_sys_id` | string | Yes | The unique system ID (sys_id) of the change request that contains the task. This is a 32-character hexadecimal string that uniquely identifies the change request. Example: '46e9b4afa9fe198101026e122b85f442'. The change request must exist, or a 404 error will be returned. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete ci lifecycle mgmt action

**Slug:** `SERVICENOW_DELETE_CI_LIFECYCLE_MGMT_ACTION`

Permanently deletes a specific CI Lifecycle Management action from ServiceNow using its sys_id. Use this action when you need to remove a CI Lifecycle Management action record that is no longer needed. This action is irreversible — the CI action cannot be recovered once deleted. Requires the user to have appropriate permissions for the CI Lifecycle Management module. Use when you need to clean up obsolete, incorrect, or duplicate CI lifecycle action records.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `action_sys_id` | string | Yes | The unique system ID (sys_id) of the CI Lifecycle Management action to delete. This is a 32-character hexadecimal string that uniquely identifies the action record. Example: '9a8f5b3c1d4e7f2a6b0c8d3e5f7a1b9c'. The action must exist, or a 404 error will be returned. This parameter corresponds to the 'sys_id' field of the 'statemgmt_ci_actions' table. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete ci lifecycle mgmt operators

**Slug:** `SERVICENOW_DELETE_CI_LIFECYCLE_MGMT_OPERATORS`

Permanently unregisters an operator from the ServiceNow CI Lifecycle Management system. This action removes an operator registration for non-workflow users. This is a destructive, irreversible operation — once the operator is unregistered, it cannot be recovered and will need to be re-registered if needed again. Use this action with caution. Use when you need to clean up obsolete operator registrations for non-workflow users in the CI Lifecycle Management system. The user must have appropriate permissions to unregister operators. If the operator doesn't exist or the user lacks permissions, an error will be returned.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `req_id` | string | Yes | The unique identifier of the operator to unregister. This is the operator ID that was assigned when the operator was registered. Example: 'test-operator-id-123'. The operator must exist in the CI Lifecycle Management system, or a 404 error will be returned. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete cmdb instance relation

**Slug:** `SERVICENOW_DELETE_CMDB_INSTANCE_RELATION`

Permanently deletes a specific CMDB CI (Configuration Item) relation using its sys_id. This is a destructive, irreversible operation — the relation between two CIs cannot be recovered once deleted. The relation represents a connection between a parent and child CI (e.g., a server running an application). Requires the user to have the ITIL role and appropriate CMDB permissions. If the relation, CI, or class doesn't exist, or the user lacks permissions, an error will be returned. Use when you need to remove a specific relationship between two configuration items in the CMDB.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The sys_id of the CI (Configuration Item) record. This is a required path parameter that uniquely identifies the CI instance within the specified class table. It is a 32-character hexadecimal string. Example: '106c5c13c61122750194a1e96cfde951' |
| `classname` | string | Yes | Name of the CMDB CI (Configuration Item) class. This is a required path parameter that identifies the class table to which the CI belongs. Common values include 'cmdb_ci_server', 'cmdb_ci_application', 'cmdb_ci_service_discovered', etc. Example: 'cmdb_ci_server' |
| `rel_sys_id` | string | Yes | The sys_id of the CMDB relation to delete. This is a required path parameter that uniquely identifies the relationship record between two CIs. It is a 32-character hexadecimal string. Example: '2ce248ba833bf210dd2dc2dfeeaad3c0' |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete emergency change request

**Slug:** `SERVICENOW_DELETE_EMERGENCY_CHANGE_REQUEST`

Permanently deletes a specific emergency change request from ServiceNow using its sys_id. This is a destructive operation that cannot be undone. The emergency change request will be permanently removed from the system. Use this action when an emergency change request is no longer needed or was created in error. Use this action when you need to remove an emergency change request from ServiceNow. This action is irreversible — the emergency change request cannot be recovered once deleted. Requires the user to have delete permissions for change requests. If the record doesn't exist, is not an emergency change request, or the user lacks permissions, an error will be returned.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the emergency change request to delete. This is a 32-character hexadecimal string that uniquely identifies the change request. Example: '45b188f6833bf210dd2dc2dfeeaad324'. The record must exist and be an emergency change request, or a 404 error will be returned. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete incident by

**Slug:** `SERVICENOW_DELETE_INCIDENT_BY_ID`

Permanently deletes a specific incident from ServiceNow using its sys_id. This is a destructive, irreversible operation — the incident cannot be recovered once deleted. Requires the user to have delete permissions for the incident table. If the incident doesn't exist or the user lacks permissions, an error will be returned. Use this action when you need to remove a specific incident record and know its sys_id.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the incident to delete. This is a 32-character hexadecimal string that uniquely identifies the incident record. Example: '46b66a40a9fe198101f243dfbc79033d'. The incident must exist, or a 404 error will be returned. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete incident by id2

**Slug:** `SERVICENOW_DELETE_INCIDENT_BY_ID2`

Permanently deletes a specific incident from ServiceNow using its sys_id via the Table API. This is a destructive, irreversible operation — the incident cannot be recovered once deleted. Requires the user to have delete permissions for the incident table. If the incident doesn't exist or the user lacks permissions, an error will be returned. Use when you need to remove a specific incident record and know its sys_id.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the incident to delete. This is a 32-character hexadecimal string that uniquely identifies the incident record. Example: '46b66a40a9fe198101f243dfbc79033d'. The incident must exist, or a 404 error will be returned. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete servicecatalog cart

**Slug:** `SERVICENOW_DELETE_SERVICECATALOG_CART`

Removes a specific item from the current ServiceNow Service Portal shopping cart. This action permanently removes a cart item from the active shopping cart session. Use this action when a user wants to remove an unwanted item from their Service Catalog cart before submitting the order. This action is irreversible — once the item is removed, it must be added again if still needed. Use when you need to remove an item from a user's Service Portal shopping cart and have the cart item's sys_id.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `cart_item_id` | string | Yes | The unique system ID (sys_id) of the cart item to remove from the current shopping cart. This is a 32-character hexadecimal string that uniquely identifies the cart item. Example: 'b2754c3283fbf210dd2dc2dfeeaad33b'. The cart item must exist in the current user's cart, or a 404 error will be returned. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete service catalog cart empty

**Slug:** `SERVICENOW_DELETE_SERVICE_CATALOG_CART_EMPTY`

Empties all items from a specified Service Catalog shopping cart using its sys_id. This action removes all items from the cart but does not delete the cart itself. This is a destructive, irreversible operation — all cart items will be permanently removed and cannot be recovered once emptied. Use this action with caution. Use when you need to clear all items from a user's Service Catalog shopping cart before adding new items or before discarding an unwanted order.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the Service Catalog shopping cart to empty. This is a 32-character hexadecimal string that uniquely identifies the cart record. Example: '8df4cc7a83bbf210dd2dc2dfeeaad380'. All items within the cart will be permanently removed, but the cart itself will remain. The cart must exist, or a 404 error will be returned. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete sn chg rest change

**Slug:** `SERVICENOW_DELETE_SN_CHG_REST_CHANGE`

Permanently deletes a specific change request using its sys_id via the Change Management REST API. Use this action when you need to remove a change request from ServiceNow that is no longer needed. This action is irreversible — the change request cannot be recovered once deleted. Requires the user to have appropriate permissions for the change management module.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the change request to delete. This is a 32-character hexadecimal string that uniquely identifies the change request. Example: '1766f1de47410200e90d87e8dee490f6'. The change request must exist, or a 404 error will be returned. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Normal Change Request

**Slug:** `SERVICENOW_DELETE_SN_CHG_REST_CHANGE_NORMAL`

Permanently deletes a normal change request identified by its sys_id using the ServiceNow Change Management REST API. This is a destructive operation that cannot be undone. The normal change request will be permanently removed from the system. Use when you need to remove an unwanted or obsolete normal change request from ServiceNow. This action is irreversible — the change request cannot be recovered once deleted.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the normal change request to delete. This is a 32-character hexadecimal string that uniquely identifies the change request record. Example: '2071a5d037310200f212cc028e41f107'. The change request must exist, or a 404 error will be returned. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete sn chg rest change standard

**Slug:** `SERVICENOW_DELETE_SN_CHG_REST_CHANGE_STANDARD`

Permanently deletes a standard change request from ServiceNow using its sys_id. Use this action when you need to remove a specific standard change request that is no longer needed. This is a destructive operation that cannot be undone — the standard change request cannot be recovered once deleted. Requires appropriate permissions to delete change requests in ServiceNow.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the standard change request to delete. This is a 32-character hexadecimal string that uniquely identifies the change request. Example: '2de5121347c12200e0ef563dbb9a71eb'. The change request must exist, or a 404 error will be returned. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete table

**Slug:** `SERVICENOW_DELETE_TABLE`

Permanently deletes a specific record from a ServiceNow table using its sys_id. Use this action when you need to remove a record from a ServiceNow table and the record's sys_id is known. This is a destructive operation that cannot be undone. The record will be permanently removed from the table. Requires the user to have delete permissions on the specified table. If the record doesn't exist or the user lacks permissions, an error will be returned.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the record to delete. This is a 32-character hexadecimal string that uniquely identifies the record. Example: '3a24ff2e83b7f210dd2dc2dfeeaad37e'. The record must exist in the specified table, or a 404 error will be returned. |
| `table_name` | string | Yes | Name of the ServiceNow table from which to delete the record (e.g., 'incident', 'problem', 'change_request', 'task'). The table must exist in the ServiceNow instance and the user must have delete permissions for it. |
| `sysparm_query_no_domain` | boolean | No | Set to true to include records from domains the logged-in user is not configured to access (requires admin or query_no_domain_table_api role). When false (default), only records in the user's configured domains can be deleted. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete table incident

**Slug:** `SERVICENOW_DELETE_TABLE_INCIDENT`

Permanently deletes a specific incident record from ServiceNow using its sys_id. This is a destructive, irreversible operation — the incident cannot be recovered once deleted. Requires the user to have delete permissions on the incident table. If the incident doesn't exist or the user lacks permissions, an error will be returned. Use when you need to remove a specific incident record from ServiceNow and know its sys_id.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the incident record to delete. This is a 32-character hexadecimal string that uniquely identifies the incident. Example: '1c741bd70b2322007518478d83673af3'. The incident must exist, or a 404 error will be returned. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Find file

**Slug:** `SERVICENOW_FIND_FILE`

Retrieves attachment metadata from ServiceNow's sys_attachment table. This endpoint queries file attachments and returns metadata including file name, size, content type, download links, and associated table information. Use sysparm_query to filter by file name, table name, content type, or other attachment properties. Note: This returns metadata only; use the download_link in the response to retrieve actual file content.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sysparm_limit` | string | No | Limit to be applied on pagination. Note: Unusually large sysparm_limit values can impact system performance. |
| `sysparm_query` | string | No | Encoded query. Queries for the Attachment API are relative to the Attachments [sys_attachment] table. For example: (sysparm_query=file_name=attachment.doc) The encoded query provides support for order by. To sort responses based on certain fields, use the ORDERBY and ORDERBYDESC clauses in sysparm_query. For example, sysparm_query=ORDERBYfile_name^ORDERBYDESCtable_Name orders the results in ascending order by name first, then in descending order by table name. |
| `sysparm_offset` | string | No | Number of records to exclude from the query. Use this parameter to get more records than specified in sysparm_limit parameter. For example, if sysparm_limit is set to 500, but there are additional records you want to query, you can specify a sysparm_offset parameter value of 500 to get the second set of records. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Activity Subscription Activities

**Slug:** `SERVICENOW_GET_ACTSUB_ACTIVITIES`

Retrieves activity records from the ServiceNow ActivitySubscription API. Use this action when you need to fetch activity/change history records from ServiceNow subscriptions. This API returns activities such as record creations, updates, comments, and other events from subscribed tables. The default stream returns all available activity records. Results can be paginated using the sysparm_limit and sysparm_offset parameters.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `stream` | string | No | The type of activity stream to retrieve. Default value is 'activities' which returns all activity records. Other values may include specific activity types supported by the subscription API. |
| `sysparm_limit` | integer | No | Maximum number of activity records to return. Use pagination parameters to retrieve additional records if the limit is exceeded. |
| `sysparm_offset` | integer | No | Starting record index for which to begin retrieving activities. Use this value to paginate through activity records by incrementing by the limit value. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Activity Subscription Facets

**Slug:** `SERVICENOW_GET_ACTSUB_FACETS`

Retrieves facets configured for an activity context in ServiceNow. Use this action when you need to discover available filterable attributes or metadata for activity subscriptions. Facets represent the different dimensions along which activity data can be filtered or grouped. This is a read-only operation that queries the Activity Subscriptions API to return facet configuration information for the specified context.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `activity_context` | string | Yes | The type of activity context for which to retrieve facets. Common values include 'table' for table-level subscriptions, 'record' for specific record subscriptions, or other activity context types defined in the ServiceNow instance. |
| `context_instance` | string | Yes | The specific instance identifier for the activity context. For 'table' context, this would be the table name (e.g., 'incident', 'task'). For 'record' context, this would be the sys_id of the specific record. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Agent Intelligence Solution Prediction

**Slug:** `SERVICENOW_GET_AGENT_INTELLIGENCE_SOLUTION_PREDICTION`

Predicts an output field value using a trained Agent Intelligence solution model. Use this action when you need to invoke a deployed Predictive Intelligence solution to predict an output field value based on input field data. This is typically used after the Predictive Intelligence plugin is activated and solutions have been trained and deployed — for example, to predict incident assignment, priority, urgency, category, or any other custom trained output field. The action requires the name of an existing, deployed solution and optionally accepts input field values that the model uses to generate the prediction. The response includes the predicted value along with a confidence score indicating the model's certainty.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `input_fields` | object | No | A dictionary of input field names and their values to pass to the prediction model. The required fields depend on the solution's trained model — typically these are the input features the model was trained on (e.g., for an incident predictor: {'urgency': 'high', 'impact': 'medium', 'category': 'software'}). Leave empty or omit if the solution does not require input field values. Values can be strings, integers, floats, or booleans. |
| `solution_name` | string | Yes | The name of the Agent Intelligence solution to use for prediction. This is a required path parameter identifying the trained predictive model. Example: 'incident_assignment_predictor' or 'task_priority_model'. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Agent Intelligence Solution Predictions

**Slug:** `SERVICENOW_GET_AGENT_INTELLIGENCE_SOLUTION_PREDICTION_LIST`

Retrieves a list of solution predictions from ServiceNow's Agent Intelligence engine. Use this action when you need to fetch predicted solutions for multiple records, such as retrieving AI-recommended solutions for incidents, problems, or change requests. The predictions include confidence scores, solution details, and relevance metrics to help resolve issues more efficiently. Supports filtering, pagination, and confidence thresholds. This action is useful for implementing AI-powered resolution suggestions, analyzing prediction patterns, or integrating Agent Intelligence insights into custom workflows.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sysparm_limit` | integer | No | Maximum number of solution predictions to return. Use pagination parameters to retrieve additional results if needed. Note: Large values may impact system performance. |
| `sysparm_query` | string | No | Encoded query to filter solution predictions. Syntax: <col_name><operator><value>. Supports operators: = (exact match), != (not equal), ^ (AND), ^OR (OR), LIKE (contains string), STARTSWITH, ENDSWITH. Example: category=password^confidence_score>=0.8 |
| `sysparm_offset` | integer | No | Starting record index for pagination. Use sysparm_offset + sysparm_limit to page through results. For example, first call with offset=0, next call with offset=sysparm_limit. |
| `prediction_type` | string | No | Type of predictions to retrieve. Common values: 'incident', 'problem', 'change', 'task'. If not specified, returns all prediction types. |
| `include_metadata` | boolean | No | Flag to include additional metadata in the response. Set to true to include extended prediction metadata. |
| `confidence_threshold` | number | No | Minimum confidence score threshold for returned predictions. Only predictions with confidence_score >= this value will be returned. Example: 0.8 returns only high-confidence predictions. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get All Data Classes

**Slug:** `SERVICENOW_GET_ALL_DATA_CLASSES`

Retrieves all data classification records from the ServiceNow Data Classification API. Use this action when you need to list all available data classification levels (e.g., Public, Internal, Confidential, Restricted) configured in a ServiceNow instance. Data classifications are used to label and categorize data based on sensitivity levels for security and compliance purposes. This action is read-only and does not modify any records. It requires no request parameters and returns all classification records configured in the system.

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get App Service CMDB Content

**Slug:** `SERVICENOW_GET_APP_SERVICE_CONTENT`

Retrieves a list of configuration items (CIs) associated with a specific application service in ServiceNow CMDB. Use this action when you need to query what infrastructure components (servers, databases, applications, etc.) are part of a given application service. This is useful for impact analysis, change management, and understanding service dependencies within the CMDB.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The sys_id (unique identifier) of the application service whose configuration items (CIs) you want to retrieve. |
| `sysparm_limit` | integer | No | Maximum number of configuration items to return. Use pagination parameters for larger result sets. |
| `sysparm_fields` | string | No | Comma-separated list of fields to return. Invalid field names are silently ignored. Example: 'sys_id,name,ip_address' |
| `sysparm_offset` | integer | No | Starting record offset for pagination. Set to sysparm_offset + sysparm_limit to paginate through results. |
| `sysparm_display_value` | string | No | Determines the format of field values in the response. 'false': Returns actual database values (sys_ids for references, numeric values for choices). 'true': Returns display values (names for references, text labels for choices). 'all': Returns both display and actual values. |
| `sysparm_exclude_reference_link` | boolean | No | Set to true to exclude Table API links for reference fields in the response. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get attachment by

**Slug:** `SERVICENOW_GET_ATTACHMENT_BY_ID`

Retrieves metadata for a specific attachment by its sys_id from ServiceNow. Use this action when you need to fetch information about a single attachment file, such as its file name, content type, size, and associated record details. This action returns metadata only; to download the actual file content, use the download_link from the FindFile action or access the file directly via the ServiceNow attachment API.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The sys_id of the attachment to retrieve. This is the unique identifier assigned to the attachment when it was created. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Attachment by ID

**Slug:** `SERVICENOW_GET_ATTACHMENT_BY_ID_V1`

Retrieves metadata for a specific attachment by its sys_id from ServiceNow. Use this action when you need to fetch detailed information about a single attachment file, such as its file name, content type, size, download link, image dimensions (for images), and associated record details. This action returns metadata only; to download the actual file content, use the download_link provided in the response or the GetAttachmentFile action.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The sys_id of the attachment to retrieve. This is the unique identifier assigned to the attachment when it was created. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get attachment file

**Slug:** `SERVICENOW_GET_ATTACHMENT_FILE`

Downloads the binary file attachment with the specified sys_id from ServiceNow. Use this action when you need to retrieve the actual file content of an attachment that was previously uploaded to a ServiceNow record (e.g., incident, problem, change_request). This action returns the raw binary file data which can then be saved locally or processed further. The attachment sys_id can be obtained from the 'FindFile' action or from the ServiceNow UI.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | Sys_id of the attachment to download. This is the unique identifier of the attachment record in ServiceNow. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get attachment file file

**Slug:** `SERVICENOW_GET_ATTACHMENT_FILE_FILE`

Downloads the binary file attachment with the specified sys_id from ServiceNow using the v1 API endpoint. Use this action when you need to retrieve the actual file content of an attachment that was previously uploaded to a ServiceNow record (e.g., incident, problem, change_request) via the /api/now/v1/attachment endpoint. This action returns the raw binary file data which can then be saved locally or processed further. The attachment sys_id can be obtained from the 'GetAttachmentList' or 'GetAttachmentById' actions.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | System ID of the attachment record from which to return binary data. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Attachment List

**Slug:** `SERVICENOW_GET_ATTACHMENT_LIST`

Retrieves metadata for multiple file attachments from ServiceNow's Attachment API. Use this action to list and filter attachments across the instance, including filtering by table name, file name, content type, size, or other attachment properties. Supports pagination via sysparm_limit and sysparm_offset parameters. Note: This returns metadata only; actual file content must be downloaded separately using the sys_id.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sysparm_limit` | integer | No | Maximum number of attachment records to return. Use this parameter to limit the response size when querying multiple attachments. For requests that exceed this number, use sysparm_offset to paginate. Note: Unusually large sysparm_limit values can impact system performance. |
| `sysparm_query` | string | No | Encoded query to filter attachments. Queries are relative to the sys_attachment table. Syntax follows ServiceNow encoded query format: <column><operator><value>. Operators: = (equals), != (not equals), ^ (AND), ^OR (OR), LIKE (contains), STARTSWITH, ENDSWITH. Examples: file_nameLIKEreport - attachments with 'report' in the file name; table_name=incident - attachments on incident records; content_type=image%2Fpng - PNG images; size_bytes>1000000 - files larger than 1MB. Use ORDERBY or ORDERBYDESC for sorting: ORDERBYfile_name, ORDERBYDESCsys_created_on. |
| `sysparm_offset` | integer | No | Starting record index for pagination. Use this to retrieve additional records beyond the sysparm_limit. For example, if sysparm_limit is 25, set sysparm_offset=25 to retrieve the next batch of records. Continue incrementing by sysparm_limit until you have retrieved all desired records. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get change ci schedule

**Slug:** `SERVICENOW_GET_CHANGE_CI_SCHEDULE`

Retrieves available time slots for scheduling changes against a specific Configuration Item (CI). Use this action when you need to find available change windows for a given CI in ServiceNow's Change Management module. The endpoint queries the CMDB with the specified CI sys_id and returns available schedule slots. Optionally filter by duration_in_seconds to find slots that can accommodate a specific change window length.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `cmdb_ci_sys_id` | string | Yes | The sys_id of the Configuration Item (CI) in the CMDB for which to retrieve available change schedule time slots. This is a 32-character unique identifier for the CI record. |
| `duration_in_seconds` | integer | Yes | The requested duration of the change window in seconds. The API returns only schedule slots that can accommodate a change of this duration. For example, 3600 seconds = 1 hour, 7200 seconds = 2 hours. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Change Conflict Status

**Slug:** `SERVICENOW_GET_CHANGE_CONFLICT`

Retrieves the conflict status for a ServiceNow change request, identifying scheduling conflicts with other changes or blackout windows. Use this action when you need to check if a change request has any scheduling conflicts with other changes or if it falls within a blackout window. This is typically used before approving or implementing a change to ensure proper scheduling and avoid resource conflicts.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the change request to retrieve conflict status for. This is a 32-character hexadecimal string that uniquely identifies the change request. Example: '46e9b4afa9fe198101026e122b85f442' |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get change nextstates

**Slug:** `SERVICENOW_GET_CHANGE_NEXTSTATES`

Retrieves a list of available next states for a specified change request based on the current state and workflow. Use this action when you need to determine what state transitions are valid for a particular change request, such as when deciding which state to move a change to or when validating workflow transitions.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `change_sys_id` | string | Yes | The sys_id of the change request for which to retrieve available next states. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Change Request Configuration Items

**Slug:** `SERVICENOW_GET_CHANGE_REQUEST_CI`

Retrieves configuration items (CIs) associated with a specific change request in ServiceNow. Use this action when you need to fetch the list of configuration items (servers, databases, applications, etc.) that are linked to a change request. This is commonly used to: - Review affected infrastructure before approving a change - Understand the scope of impact for a change request - Verify that all required CIs are included in the change The association_type parameter determines which CIs to retrieve based on their relationship to the change request.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the change request. This is a 32-character hexadecimal string that uniquely identifies the change request record. Example: '46e9b4afa9fe198101026e122b85f442' |
| `association_type` | string ("affected" | "requested" | "requested_and_affected") | No | Type of CI association to retrieve for the change request. 'affected': Retrieves CIs that are affected by the change request. 'requested': Retrieves CIs that are requested to be included in the change request. 'requested_and_affected': Retrieves both requested and affected CIs. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get change schedule

**Slug:** `SERVICENOW_GET_CHANGE_SCHEDULE`

Retrieves available time slots for scheduling a ServiceNow change request. Use this action when you need to find available scheduling windows for a change request that has been created but not yet scheduled. This helps identify appropriate times to schedule the change work based on the configured calendar and availability. The response includes schedule windows with start/end times, duration, and availability status. Note: The change request must exist and the user must have permission to view the schedule.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `change_sys_id` | string | Yes | The unique system ID (sys_id) of the change request. This is a 32-character hexadecimal string that uniquely identifies the change request. Example: '46e9b4afa9fe198101026e122b85f442'. You can obtain this from the sys_id field of a change request record. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get CI Lifecycle Management Action

**Slug:** `SERVICENOW_GET_CILIFECYCLEMGMT_ACTIONS`

Retrieves a specific CI Lifecycle Management action from ServiceNow using its sys_id. Use this action when you need to fetch detailed information about a particular CI Lifecycle Management action, including its name, state, description, and associated CMDB class. This is a read-only operation that does not modify any data in ServiceNow.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the CI Lifecycle Management action to retrieve. This is a 32-character hexadecimal string that uniquely identifies the action record. Example: '00000000000000000000000000000000' |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response. Invalid field names are silently ignored. Example: 'sys_id,name,state,class_name' |
| `sysparm_display_value` | string | No | Determines the type of data returned for reference fields. 'false': Returns actual database values (sys_ids for references). 'true': Returns display values (names for references). 'all': Returns both display and actual values. |
| `sysparm_exclude_reference_link` | boolean | No | Flag that indicates whether to exclude Table API links for reference fields. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Check CI Compatibility

**Slug:** `SERVICENOW_GET_CILIFECYCLEMGMT_COMPAT_ACTIONS`

Determines whether two specified Configuration Items (CIs) in the ServiceNow CMDB are compatible using the CI Lifecycle Management compatActions endpoint. Use this action when you need to verify compatibility between two Configuration Items before planning changes, deployments, or scheduling activities that involve multiple CIs. This helps ensure that changes to one CI won't negatively impact another CI in the configuration.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `ci1` | string | Yes | The sys_id of the first Configuration Item (CI) to check for compatibility. This is a 32-character hexadecimal string that uniquely identifies the CI record in the CMDB. Example: '00a96c0d3790200044e0bfc8bcbe5db4' |
| `ci2` | string | Yes | The sys_id of the second Configuration Item (CI) to check for compatibility. This is a 32-character hexadecimal string that uniquely identifies the CI record in the CMDB. Example: '00a96c0d3790200044e0bfc8bcbe5db5' |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Check CI Lease Expiration Status

**Slug:** `SERVICENOW_GET_CI_LIFECYCLE_MGMT_LEASES_EXPIRED`

Determines whether a CI Lifecycle Management lease has expired for the specified lease record. Use this action when you need to check the expiration status of a lease in ServiceNow's CI Lifecycle Management system. This is a read-only operation that queries whether the specified lease has expired based on its end date and current system time. This action is useful for: - Verifying lease validity before performing operations that require an active lease - Auditing expired leases in the CMDB - Triggering renewal workflows when leases are expired

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the lease record to check for expiration status. This is a 32-character hexadecimal string that uniquely identifies the lease record in the CI Lifecycle Management system. Example: '00000000000000000000000000000001' |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Check CI Not Allowed Ops Transition

**Slug:** `SERVICENOW_GET_CI_LIFECYCLE_MGMT_NOT_ALLOWED_OPS_TRANSITION`

Determines whether a configuration item (CI) can be transitioned based on CI lifecycle management rules. Use this action when you need to check if a configuration item (CI) in ServiceNow's CMDB has any allowed state transitions under the CI lifecycle management rules. This is typically used when validating whether a CI can be moved to a specific state in its lifecycle, such as before scheduling maintenance or making configuration changes. The endpoint queries the CI lifecycle management rules to determine if the specified CI has any transition restrictions or if certain state changes are not permitted.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the configuration item (CI) to check for not allowed operations transition. This is a 32-character hexadecimal string that uniquely identifies the CI record in ServiceNow CMDB. Example: '00a96c0d3790200044e0bfc8bcbe5db4' |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Validate CI Lifecycle Management Requestor

**Slug:** `SERVICENOW_GET_CILIFECYCLEMGMT_REQUESTORS_VALID`

Validates whether a specified active workflow requestor exists and is valid in ServiceNow CI Lifecycle Management. Use this action when you need to verify that a CI Lifecycle Management workflow requestor is valid and active before proceeding with related operations such as change requests, deployment approvals, or CI lifecycle workflows. This is a read-only check that does not modify any data. The action queries the CI Lifecycle Management API with the requestor ID and returns a boolean result indicating validity. If the requestor is not found or is inactive, the API typically returns false.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `req_id` | string | Yes | The unique identifier of the workflow requestor to validate. This is typically the sys_id of the requestor record in the CI Lifecycle Management system. Example: 'test123456789012345678901234567' |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get CI Lifecycle Mgmt Status

**Slug:** `SERVICENOW_GET_CI_LIFECYCLE_MGMT_STATUSES`

Retrieves the current operational status for a Configuration Item (CI) in ServiceNow CMDB using the CI Lifecycle Management API. Use this action when you need to check the current operational state of a specific Configuration Item, such as whether it is running, has a problem, or is non-operational. This is a read-only operation that does not modify any data in ServiceNow.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the Configuration Item (CI) for which to retrieve the current operational status. This is a 32-character hexadecimal string that uniquely identifies the CI record in ServiceNow CMDB. Example: '00a96c0d3790200044e0bfc8bcbe5db4' |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get CMDB Linux Server by ID

**Slug:** `SERVICENOW_GET_CMDB_CI_LINUX_SERVER`

Retrieves a single CMDB Linux server configuration item (CI) by its sys_id, including its attributes and relationship information. Use this action when you need to fetch detailed information about a specific Linux server from ServiceNow's CMDB, such as its attributes (name, IP address, OS version, kernel version, etc.) and both its inbound (dependents) and outbound (dependencies) relationships with other CIs. This is a read-only operation that does not modify any data in ServiceNow.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the CMDB Linux server configuration item to retrieve. This is a 32-character hexadecimal string that uniquely identifies the CI record. Example: '3a290cc60a0a0bb400000bdb386af1cf' |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response. Invalid field names are silently ignored. Example: 'sys_id,name,ip_address,operational_status' |
| `sysparm_display_value` | string | No | Determines the format of field values in the response. 'false': Returns actual database values (sys_ids for references, numeric values for choices). 'true': Returns display values (names for references, text labels for choices). 'all': Returns both display and actual values. |
| `sysparm_exclude_reference_link` | boolean | No | Set to true to exclude Table API links for reference fields in the response. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Find CSDM Application Service

**Slug:** `SERVICENOW_GET_CMDB_CSDM_APP_SERVICE_FIND_SERVICE`

Finds and returns basic information about one or more application services in the ServiceNow CMDB using the CSDM (Common Service Data Model) app_service find_service endpoint. Use this action when you need to search for application services by name (supports wildcards), retrieve their basic metadata such as operational status, owning segment, and business criticality, or check whether a specific application service exists in the CMDB.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | Yes | Name of the application service to find. Supports wildcards using '*' prefix or suffix. Examples: 'My Service', '*-production', 'app-*', '*-db-*' |
| `sysparm_limit` | integer | No | Maximum number of application service records to return. Use pagination parameters for larger result sets. |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response. Invalid field names are silently ignored. Example: 'sys_id,name,description,operational_status' |
| `sysparm_offset` | integer | No | Starting record offset for pagination. Set to sysparm_offset + sysparm_limit to paginate through results. |
| `sysparm_display_value` | string | No | Determines the format of field values in the response. 'false': Returns actual database values (sys_ids for references, numeric values for choices). 'true': Returns display values (names for references, text labels for choices). 'all': Returns both display and actual values. |
| `sysparm_exclude_reference_link` | boolean | No | Set to true to exclude Table API links for reference fields in the response. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get CMDB Instance by Class

**Slug:** `SERVICENOW_GET_CMDB_INSTANCE`

Retrieves configuration items (CIs) from a specified CMDB class using the ServiceNow CMDB Instance API. Use this action when you need to query configuration items from the CMDB by class name, such as retrieving all servers (cmdb_ci_server), computers (cmdb_ci_computer), databases (cmdb_ci_database), or all CIs (cmdb_ci). Supports filtering via sysparm_query and pagination via sysparm_limit and sysparm_offset.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `classname` | string | Yes | Name of the CMDB class to query (e.g., 'cmdb_ci', 'cmdb_ci_server', 'cmdb_ci_computer', 'cmdb_ci_database', 'cmdb_ci_service_discovered', 'cmdb_ci_application'). Use 'cmdb_ci' to query the base CI class and retrieve all configuration items. |
| `sysparm_limit` | integer | No | Maximum number of configuration item records to return. Use pagination for larger result sets. |
| `sysparm_query` | string | No | Encoded query to filter configuration items. Syntax: <col_name><operator><value>. Operators: '=' (exact match), '!=' (not equal), '^' (AND), '^OR' (OR), LIKE, STARTSWITH, ENDSWITH. Example: operational_status=1^environment=Production |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response. Invalid field names are silently ignored. Example: 'sys_id,name,ip_address,operational_status' |
| `sysparm_offset` | integer | No | Starting record offset for pagination. Set to sysparm_offset + sysparm_limit to paginate through results. |
| `sysparm_display_value` | string | No | Determines the format of field values in the response. 'false': Returns actual database values (sys_ids for references, numeric values for choices). 'true': Returns display values (names for references, text labels for choices). 'all': Returns both display and actual values. |
| `sysparm_exclude_reference_link` | boolean | No | Set to true to exclude Table API links for reference fields in the response. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get CMDB Instance by ID

**Slug:** `SERVICENOW_GET_CMDB_INSTANCE_BY_ID`

Retrieves a single CMDB configuration item (CI) by its class name and sys_id, including its attributes and relationship information. Use this action when you need to fetch detailed information about a specific configuration item from ServiceNow's CMDB, such as its attributes (name, IP, status, etc.) and both its inbound (dependents) and outbound (dependencies) relationships with other CIs. This is a read-only operation that does not modify any data in ServiceNow.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the CMDB configuration item to retrieve. This is a 32-character hexadecimal string that uniquely identifies the CI record. Example: '00a96c0d3790200044e0bfc8bcbe5db4' |
| `classname` | string | Yes | Name of the CMDB CI class (table) to query. Examples: 'cmdb_ci', 'cmdb_ci_linux_server', 'cmdb_ci_apache', 'cmdb_ci_service_discovered'. The class name determines which type of configuration item to retrieve. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get CMDB Class Metadata

**Slug:** `SERVICENOW_GET_CMDB_META`

Retrieves metadata and schema information for a specified CMDB (Configuration Management Database) class. Use this action when you need to discover the field structure, data types, mandatory fields, and relationships of a CMDB class before performing queries or updates. This is useful for understanding what fields are available for filtering, display, or modification operations. The user must have the ITIL role to access CMDB metadata.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `class_name` | string | Yes | The CMDB class name to retrieve metadata for. Common classes include: 'cmdb_ci' (base CI class), 'cmdb_ci_server', 'cmdb_ci_database', 'cmdb_ci_service', 'cmdb_ci_web_server', 'cmdb_ci_linux_server', 'cmdb_ci_win_server', 'cmdb_ci_appl'. |
| `sysparm_display_value` | string | No | Determines the format of field values in the response. 'false': Returns actual database values. 'true': Returns display values. 'all': Returns both display and actual values. |
| `sysparm_exclude_reference_link` | boolean | No | Set to true to exclude Table API links for reference fields in the response. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Cloud Catalog Services

**Slug:** `SERVICENOW_GET_CMP_CATALOG_API_SERVICES`

Retrieves a list of catalog items from the ServiceNow Cloud Services Catalog API. Use this action when you need to query and fetch catalog service items (from the sc_cat_item table) through the Cloud Services Catalog API. Supports filtering via encoded queries, field selection, pagination, and display value options. This is useful for browsing available catalog offerings, checking item availability, or searching for specific services in the ServiceNow Service Catalog.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sysparm_view` | string ("desktop" | "mobile" | "both") | No | UI view for which to render the data (desktop, mobile, or both). |
| `sysparm_limit` | integer | No | Maximum number of catalog service items to return in the response. Use pagination parameters (sysparm_offset) for retrieving larger result sets. Note: Unusually large values can impact system performance. |
| `sysparm_query` | string | No | Encoded query string to filter catalog items. Syntax: <col_name><operator><value>. Operators: = (equals), != (not equals), ^ (AND), ^OR (OR), LIKE, STARTSWITH, ENDSWITH. Example: active=true^price>0 Example: retired=false^availability=available |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response. Invalid field names are silently ignored. Example: 'sys_id,name,short_description,price' |
| `sysparm_offset` | integer | No | Starting record index for which to begin retrieving catalog items. Use this value to paginate through results. For example, set sysparm_offset=0 for the first page, then sysparm_offset=sysparm_limit for the next page. |
| `sysparm_no_count` | boolean | No | Flag that indicates whether to execute a select count(*) query to return the number of rows. |
| `sysparm_display_value` | string ("true" | "false" | "all") | No | Determines the type of data returned, either the actual values from the database or the display values of the fields. Display values are manipulated based on the actual value in the database and user or system settings and preferences. 'false': Returns actual database values (sys_ids for references, numeric values for choices). 'true': Returns display values (names for references, text labels for choices). 'all': Returns both display and actual values. |
| `sysparm_query_category` | string | No | Name of the category to use when querying. Restricts results to items belonging to the specified category. |
| `sysparm_exclude_reference_link` | boolean | No | Flag that indicates whether to exclude Table API links for reference fields. |
| `sysparm_suppress_pagination_header` | boolean | No | Flag that indicates whether to remove the Link header from the response. The Link header provides URLs to relative pages in the record set for pagination. Set to 'true' to remove the Link header, 'false' to include it. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Email by ID

**Slug:** `SERVICENOW_GET_EMAIL`

Retrieves a specific email record from ServiceNow's Email [sys_email] table by its sys_id. Use this action when you need to fetch detailed information about a particular email message, including its subject, body content, sender, recipients, status, and timestamps. This is a read-only operation that does not modify any data in ServiceNow.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the email record to retrieve. This is a 32-character hexadecimal string that uniquely identifies the email in the sys_email table. Example: '1228ed5283333210dd2dc2dfeeaad376' |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response. Invalid field names are ignored. |
| `sysparm_display_value` | string | No | Determines the type of data returned, either 'true' for display values or 'false' for actual values. Display values are manipulated based on user or system settings. Choice fields: Returns descriptive text instead of numeric values. Date fields: Returns formatted date based on user's time zone instead of UTC. Reference fields: Returns display field of referenced record instead of sys_id. |
| `sysparm_exclude_reference_link` | boolean | No | Flag that indicates whether to exclude Table API links for reference fields. Set to true to exclude links. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Global User Role Inheritance

**Slug:** `SERVICENOW_GET_GLOBAL_USER_ROLE_INHERITANCE`

Retrieves the granted and inherited roles for a specified ServiceNow user using the Global User Role Inheritance API. Use this action when you need to audit a user's role assignments in ServiceNow, check what roles a user has (both directly granted and inherited through group membership), troubleshoot access issues, or verify compliance by reviewing role inheritance for a specific user account. The authenticated user must have the appropriate role (such as 'admin' or a role with user_role_inheritance API access) to query other users' role inheritance. If no user is specified, returns the role inheritance for the authenticated user.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | No | The sys_id of the user whose role inheritance to retrieve. If not provided, returns the role inheritance for the authenticated user making the request. You must have the appropriate role (such as 'admin' or a role with user_role_inheritance API access) to query role inheritance for users other than yourself. |
| `user_id` | string | No | The user ID (user_name) of the user whose role inheritance to retrieve. This is the login name or user ID of the ServiceNow user. Either sys_id or user_id can be used to specify the user, but not both. If neither is provided, returns the role inheritance for the authenticated user. |
| `expand_groups` | boolean | No | When set to true, returns additional details about the groups through which roles are inherited. When false (default), only role names and basic information are returned. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get import

**Slug:** `SERVICENOW_GET_IMPORT`

Retrieves the specified import staging record and its associated target records. Use this action when you need to fetch a specific import staging record to view its current state, check import status, or retrieve the imported data before it is loaded into the target table. This is useful for auditing import processes, debugging failed imports, or monitoring data import progress. Common use cases: - Check the status of a specific import record - View the raw imported data for debugging - Verify that data was correctly staged before transformation - Retrieve import metadata (source, target table, batch info)

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The sys_id of the import staging record to retrieve. This is the unique identifier assigned to the staging record. |
| `staging_table_name` | string | Yes | Name of the import set staging table from which to retrieve the record. This is the table where imported data is staged before being transformed and loaded into target tables. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get incident by

**Slug:** `SERVICENOW_GET_INCIDENT_BY_ID`

Retrieves a specific incident from ServiceNow by its sys_id. Use this action when you need to fetch detailed information about a particular incident, including its state, priority, caller, assignment details, and resolution information. This is a read-only operation that does not modify any data in ServiceNow.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the incident to retrieve. This is a 32-character hexadecimal string that uniquely identifies the incident record. Example: '46b66a40a9fe198101f243dfbc79033d' |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response. If not specified, all fields are returned. |
| `sysparm_display_value` | boolean | No | Determines whether to return actual database values (false) or display values (true) for reference fields. |
| `sysparm_exclude_reference_link` | boolean | No | Determines whether reference links should be excluded from the response. Set to true to exclude reference links. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get incident by id2

**Slug:** `SERVICENOW_GET_INCIDENT_BY_ID2`

Retrieves a specific incident from ServiceNow by its sys_id using the Table API. Use this action when you need to fetch detailed information about a particular incident, including its state, priority, caller, assignment details, and other incident fields. This is a read-only operation that does not modify any data in ServiceNow.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the incident to retrieve. This is a 32-character hexadecimal string that uniquely identifies the incident record. Example: '46b9490da9fe1981003c938dab89bda3' |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Incidents

**Slug:** `SERVICENOW_GET_INCIDENTS`

Retrieves incidents from the ServiceNow incident table using the Table API. Use this action when you need to query and fetch incidents with optional filtering via sysparm_query, pagination via sysparm_limit and sysparm_offset, and field selection via sysparm_fields.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sysparm_limit` | integer | No | Maximum number of incident records to return. Use pagination for larger result sets. |
| `sysparm_query` | string | No | Encoded query to filter incidents. Syntax: <col_name><operator><value>. Operators: '=' (exact match), '!=' (not equal), '^' (AND), '^OR' (OR), LIKE, STARTSWITH, ENDSWITH. Example: state=2^priority=1 (active critical incidents) |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response. Invalid field names are silently ignored. Example: 'sys_id,number,state,priority,short_description' |
| `sysparm_offset` | integer | No | Starting record offset for pagination. Set to sysparm_offset + sysparm_limit to paginate through results. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Performance Analytics Scorecards

**Slug:** `SERVICENOW_GET_PA_SCORECARDS`

Retrieves details about indicators from the Analytics Hub, including scorecard information for performance analytics. Use this action when you need to fetch performance analytics scorecards and their associated indicators, such as when drilling down into specific indicators or retrieving overall analytics hub data. When sysparm_uuid is provided, returns details for a specific indicator; otherwise returns all available scorecards. Supports optional inclusion of score values via sysparm_include_scores.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sysparm_uuid` | string | No | UUID of the indicator to retrieve. When provided, returns details for a specific indicator. |
| `sysparm_include_scores` | boolean | No | Flag that indicates whether to include score values in the response. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get records

**Slug:** `SERVICENOW_GET_RECORDS`

Retrieves multiple records from a specified ServiceNow table with optional filtering and pagination. Use this action to query and fetch records from any ServiceNow table (e.g., incident, sys_user, problem). Supports filtering via sysparm_query, field selection, pagination, and display value options.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `table_name` | string | Yes | The name of the table from which to retrieve the record. |
| `sysparm_view` | string ("desktop" | "mobile" | "both") | No | UI view for which to render the data. Determines the fields returned in the response. |
| `sysparm_limit` | integer | No | Maximum number of records to return. For requests that exceed this number of records, use the sysparm_offset parameter to paginate record retrieval. This limit is applied before ACL evaluation. If no records return, including records you have access to, rearrange the record order so records you have access to return first. Note: Unusually large sysparm_limit values can impact system performance. |
| `sysparm_query` | string | No | Encoded query used to filter the result set. You can use a UI filter to obtain a properly encoded query. Syntax: sysparm_query=<col_name><operator><value>. <col_name>: Name of the table column to filter against. <operator>: Supports the following values: =: Exactly matches <value>. !=: Does not match <value>. ^: Logically AND multiple query statements. ^OR: Logically OR multiple query statements. LIKE: <col_name> contains the specified string. Only works for <col_name> fields whose data type is string. STARTSWITH: <col_name> starts with the specified string. Only works for <col_name> fields whose data type is string. ENDSWITH: <col_name> ends with the specified string. Only works for <col_name> fields whose data type is string. <value>: Value to match against. All parameters are case-sensitive. Queries can contain more than one entry, such as sysparm_query=<col_name><operator><value>[<operator><col_name><operator><value>]. For example: (sysparm_query=caller_id=javascript:gs.getUserID()^active=true) Encoded queries also support order by functionality. To sort responses based on certain fields, use the ORDERBY and ORDERBYDESC clauses in sysparm_query. Syntax: ORDERBY<col_name> ORDERBYDESC<col_name> For example: sysparm_query=active=true^ORDERBYnumber^ORDERBYDESCcategory This query filters all active records and orders the results in ascending order by number, and then in descending order by category. If part of the query is invalid, such as by specifying an invalid field name, the instance ignores the invalid part. It then returns rows using only the valid portion of the query. You can control this behavior using the property glide.invalid_query.returns_no_rows. Set this property to true to return no rows on an invalid query. Note: The glide.invalid_query.returns_no_rows property controls the behavior of all queries across the instance, such as in lists, scripts (GlideRecord.query()), and web service APIs. |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response. Invalid fields are ignored. |
| `sysparm_offset` | integer | No | Starting record index for which to begin retrieving records. Use this value to paginate record retrieval. This functionality enables the retrieval of all records, regardless of the number of records, in small manageable chunks. For example, the first time you call this endpoint, sysparm_offset is set to '0'. To simply page through all available records, use sysparm_offset=sysparm_offset+sysparm_limit, until you reach the end of all records. Don't pass a negative number in the sysparm_offset parameter. |
| `name_value_pairs` | string | No | DEPRECATED: This parameter does not work in the ServiceNow Table API and will be ignored. Use 'sysparm_query' instead for filtering records. Example: sysparm_query='active=true^priority=1' for multiple conditions. |
| `sysparm_no_count` | boolean | No | Flag that indicates whether to execute a select count(*) query on the table to return the number of rows in the associated table. |
| `sysparm_display_value` | string ("true" | "false" | "all") | No | Determines the type of data returned, either the actual values from the database or the display values of the fields. Display values are manipulated based on the actual value in the database and user or system settings and preferences. If returning display values, the value that is returned is dependent on the field type. Choice fields: The database value may be a number, but the display value will be more descriptive. Date fields: The database value is in UTC format, while the display value is based on the user's time zone. Encrypted text: The database value is encrypted, while the displayed value is unencrypted based on the user's encryption context. Reference fields: The database value is sys_id, but the display value is a display field of the referenced record. |
| `sysparm_query_category` | string | No | Name of the category to use for queries. |
| `sysparm_query_no_domain` | boolean | No | Flag that indicates whether to restrict the record search to only the domains for which the logged in user is configured. Valid values: false (Exclude the record if it is in a domain that the currently logged in user is not configured to access), true (Include the record even if it is in a domain that the currently logged in user is not configured to access). Note: The sysparm_query_no_domain parameter is available only to system administrators or users who have the query_no_domain_table_api role. |
| `sysparm_exclude_reference_link` | boolean | No | Flag that indicates whether to exclude Table API links for reference fields. |
| `sysparm_suppress_pagination_header` | boolean | No | Flag that indicates whether to remove the Link header from the response. The Link header provides various URLs to relative pages in the record set which you can use to paginate the returned record set. Valid values: true (Remove the Link header from the response), false (Do not remove the Link header from the response). |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Record Types

**Slug:** `SERVICENOW_GET_RECORD_TYPES`

Retrieves all available table record types from the ServiceNow instance using the Table API documentation endpoint. Use this action when you need to discover all available tables and their record types in a ServiceNow instance before performing queries, creating records, or understanding the data structure available in the instance. This is useful for dynamic table selection and exploration purposes. This action queries the /api/now/doc/table/schema endpoint which returns metadata about all tables accessible in the ServiceNow instance, including both system tables and custom tables.

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Rows from Table

**Slug:** `SERVICENOW_GET_ROWS`

Retrieves records from a specified ServiceNow table using the Table API v2. Use this action when you need to fetch one or more records from any ServiceNow table (e.g., incident, task, problem, change_request). When sys_id is provided, retrieves a single record. Without sys_id, retrieves multiple records up to the sysparm_limit. Supports filtering via sysparm_query, field selection, pagination, and display value options.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | No | The unique system ID (sys_id) of the record to retrieve. If provided, fetches a single record by its sys_id. If not provided, returns all records from the table (up to sysparm_limit). |
| `table_name` | string | Yes | The name of the ServiceNow table to query (e.g., 'incident', 'task', 'sys_user', 'problem'). Use the table name without the 'sys_ prefix for base tables. |
| `sysparm_limit` | integer | No | Maximum number of records to return. For requests that exceed this number of records, use pagination via sysparm_offset. Note: Unusually large values can impact system performance. |
| `sysparm_query` | string | No | Encoded query to filter results. Syntax: <col_name><operator><value>. Operators: '=' (exact match), '!=' (not equal), '^' (AND), '^OR' (OR), LIKE, STARTSWITH, ENDSWITH. Example: state=1^priority=2 |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response. Invalid field names are silently ignored. Example: 'sys_id,number,state,priority' |
| `sysparm_offset` | integer | No | Starting record index for pagination. Set to sysparm_offset + sysparm_limit to retrieve subsequent pages of results. |
| `sysparm_display_value` | string | No | Determines the type of data returned. 'false': Returns actual database values. 'true': Returns display values (more human-readable). 'all': Returns both display and actual values. |
| `sysparm_exclude_reference_link` | boolean | No | Set to true to exclude Table API links for reference fields in the response. |
| `sysparm_suppress_pagination_header` | boolean | No | Set to true to exclude the Link header from the response for pagination. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get servicatalog items by

**Slug:** `SERVICENOW_GET_SERVICATALOG_ITEMS_BY_ID`

Retrieves a specific Service Catalog item from ServiceNow using its sys_id. Use this action when you need to fetch detailed information about a particular catalog item, including its name, description, associated categories, variables, client scripts, and display settings. This is a read-only operation that does not modify any data in ServiceNow.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the catalog item to retrieve. This is a 32-character hexadecimal string that uniquely identifies the catalog item. Example: '011f117a9f3002002920bde8132e7020' |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Catalog Item Variables

**Slug:** `SERVICENOW_GET_SERVIC_CATALOG_ITEM_VARIABLES`

Retrieves the list of variables defined for a ServiceNow Service Catalog item. Use this action when you need to fetch all variables associated with a catalog item, such as when building dynamic forms, validating required inputs, or understanding what information a user must provide when ordering an item. This is a read-only operation that does not modify any data in ServiceNow.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the catalog item to retrieve variables for. This is a 32-character hexadecimal string that uniquely identifies the catalog item. Example: '011f117a9f3002002920bde8132e7020' |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Service Catalog Cart

**Slug:** `SERVICENOW_GET_SERVICE_CATALOG_CART`

Retrieves the details of all items within the logged-in user's Service Catalog shopping cart. This action fetches the current contents of the shopping cart, including item details, quantities, prices, and any selected variables/options. The cart is associated with the authenticated user making the request. Use this action when you need to review items before submitting an order, verify quantities, or check selected options. This is a read-only operation that does not modify any data.

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Service Catalog Cart Delivery Address

**Slug:** `SERVICENOW_GET_SERVICE_CATALOG_CART_DELIVERY_ADDRESS`

Retrieves the delivery/shipping address configured for a user's Service Catalog shopping cart. Use this action when you need to fetch the delivery address information associated with a user's ServiceNow Service Catalog cart. This is useful for verifying delivery details before placing an order or for displaying address information to users. The action returns address fields including street, city, state, zip code, country, and contact information such as phone and email.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `user_id` | string | Yes | The unique identifier of the user whose delivery address to retrieve. This can be the user's sys_id (a 32-character hexadecimal string) or the user's username. For guest users, this is typically 'guest'. Example: 'guest' or '681ccaf9c0a8016400b98a908cbe7df3' |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Service Catalog Catalog by ID

**Slug:** `SERVICENOW_GET_SERVICE_CATALOG_CATALOG_BY_ID`

Retrieves the available information for a specified service catalog by its sys_id. Use this action when you need to fetch detailed information about a specific service catalog in ServiceNow, including its title and description. This is a read-only operation that does not modify any data in ServiceNow.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the service catalog to retrieve. This is a 32-character hexadecimal string that uniquely identifies the catalog. Example: '742ce428d7211100f2d224837e61036d' |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Service Catalog Catalog Categories

**Slug:** `SERVICENOW_GET_SERVICE_CATALOG_CATALOG_CATEGORIES`

Retrieves the list of available categories for a specified ServiceNow Service Catalog. Use this action when you need to fetch the categories available within a specific service catalog, such as displaying available categories to users or navigating through catalog items. This is a read-only operation that does not modify any data in ServiceNow.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `catalog_id` | string | Yes | The unique system ID (sys_id) of the Service Catalog catalog to retrieve categories from. This is a 32-character hexadecimal string that uniquely identifies the catalog. Example: '742ce428d7211100f2d224837e61036d' |
| `sysparm_limit` | integer | No | Maximum number of categories to return. Defaults to 25 if not specified. |
| `sysparm_offset` | integer | No | Number of records to skip for pagination. Use with sysparm_limit to paginate through results. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Service Catalog Category by ID

**Slug:** `SERVICENOW_GET_SERVICE_CATALOG_CATEGORY_BY_ID`

Retrieves the available information for a specified service catalog category by its sys_id. Use this action when you need to fetch detailed information about a specific service catalog category in ServiceNow, including its title, description, subcategories, and item count. This is a read-only operation that does not modify any data in ServiceNow.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the service catalog category to retrieve. This is a 32-character hexadecimal string that uniquely identifies the category. Example: 'd258b953c611227a0146101fb1be7c31' |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Service Catalog Item Delegation

**Slug:** `SERVICENOW_GET_SERVICE_CATALOG_ITEM_DELEGATION`

Verifies whether a delegated user has access to a specific ServiceNow Service Catalog item. This action checks if a delegated user (identified by user_sys_id) is authorized to order or access a particular catalog item (identified by item_sys_id). Use this action to validate delegation permissions before attempting to submit orders on behalf of another user. Use this action when you need to verify delegation permissions for Service Catalog items, such as checking if a manager can order items on behalf of their team members or if an assistant has been granted proper access to order items for someone else.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `item_sys_id` | string | Yes | The unique system ID (sys_id) of the Service Catalog item to check delegation access for. This is a 32-character hexadecimal string that uniquely identifies the catalog item. Example: '0123456789abcdef0123456789abcdef' |
| `user_sys_id` | string | Yes | The unique system ID (sys_id) of the delegated user to verify access for. This is a 32-character hexadecimal string that uniquely identifies the user. Example: 'fedcba9876543210fedcba9876543210' |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Service Catalog Items List

**Slug:** `SERVICENOW_GET_SERVICE_CATALOG_ITEMS_LIST`

Retrieves a list of catalog items from ServiceNow's Service Catalog API. Use when you need to browse available service catalog offerings, search for specific items by name or description, filter items by category or catalog, or retrieve catalog item details including pricing, availability, and metadata. Supports filtering via category, catalog, and text search parameters.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sysparm_text` | string | No | Text search filter for catalog item name and short description. Searches across item names and descriptions to find matching items. |
| `sysparm_limit` | integer | No | Maximum number of catalog items to return. Use this parameter to limit response size. For requests that exceed this number, use pagination to retrieve additional records. Note: Unusually large values can impact system performance. |
| `sysparm_catalog` | string | No | Filter catalog items by catalog sys_id or name. Returns only items that belong to the specified service catalog. |
| `sysparm_category` | string | No | Filter catalog items by category sys_id or name. Returns only items that belong to the specified category. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Service Catalog Wishlist List

**Slug:** `SERVICENOW_GET_SERVICE_CATALOG_WISHLIST_LIST`

Retrieves the list of items in the logged-in user's ServiceNow Service Catalog wishlist. Use this action when you need to fetch the wishlist items for the currently authenticated user in ServiceNow's Service Catalog. This is useful for displaying a user's saved items, checking what items they have bookmarked, or preparing to add items to a cart. This is a read-only operation that does not modify any data in ServiceNow.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sysparm_limit` | integer | No | Maximum number of wishlist items to return. Defaults to 25 if not specified. |
| `sysparm_offset` | integer | No | Number of records to skip for pagination. Use with sysparm_limit to paginate through results. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get sn cdm shared libraries upload status

**Slug:** `SERVICENOW_GET_SN_CDM_SHARED_LIBRARIES_UPLOAD_STATUS`

Retrieves the current status of a shared library upload operation in ServiceNow. Use this action when you need to check whether a library upload has completed successfully, is still in progress, or has failed. The upload_id should be obtained from a previous upload operation response or task. This is a read-only operation that queries the current status without modifying any data.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `upload_id` | string | Yes | The unique identifier of the upload operation to retrieve the status for. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get sn chg rest change by

**Slug:** `SERVICENOW_GET_SN_CHG_REST_CHANGE_BY_ID`

Retrieves a specific change request from ServiceNow using its sys_id. Use this action when you need to fetch detailed information about a particular change request, including its state, type, and description. This is a read-only operation that does not modify any data in ServiceNow.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the change request to retrieve. This is a 32-character hexadecimal string that uniquely identifies the change request. Example: '8866498dc37a3610eb10d8477d013161' |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get sn chg rest change emergency by

**Slug:** `SERVICENOW_GET_SN_CHG_REST_CHANGE_EMERGENCY_BY_ID`

Retrieves a specific emergency change request from ServiceNow using its sys_id. Use this action when you need to fetch detailed information about a particular emergency change request, including its state, risk level, priority, implementation details, approval status, and schedule. This is a read-only operation that does not modify any data in ServiceNow.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the emergency change request to retrieve. This is a 32-character hexadecimal string that uniquely identifies the emergency change request. Example: 'd53e72ec73d423002728660c4cf6a78d' |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get sn chg rest change emergency list

**Slug:** `SERVICENOW_GET_SN_CHG_REST_CHANGE_EMERGENCY_LIST`

Retrieves one or more emergency change requests from ServiceNow using the Change Management API. Use this action when you need to query emergency change requests. Emergency changes are a type of change request that requires expedited approval and implementation due to urgent business needs. Supports filtering via sysparm_query, field selection, pagination, and display value options. Common use cases: Retrieving active emergency changes for approval, listing recently submitted emergency changes, monitoring emergency change status, or finding emergency changes by assignee.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sysparm_view` | string | No | UI view for which to render the data. Determines the fields returned in the response. Valid values: desktop, mobile, both. |
| `sysparm_limit` | integer | No | Maximum number of emergency change records to return. For requests that exceed this number of records, use pagination via sysparm_offset. Note: Unusually large sysparm_limit values can impact system performance. |
| `sysparm_query` | string | No | Encoded query used to filter the result set. Syntax: sysparm_query=<col_name><operator><value>. Supports operators: =, !=, ^ (AND), ^OR, LIKE, STARTSWITH, ENDSWITH. Example: sysparm_query=state!=4^priority=1 Can also use ORDERBY/ORDERBYDESC for sorting. Example: sysparm_query=ORDERBYDESCopened_at |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response (e.g., 'number,short_description,state,priority'). Invalid fields are ignored. If not specified, all fields are returned. |
| `sysparm_offset` | integer | No | Starting record index for which to begin retrieving records. Use this value to paginate record retrieval. For example, if sysparm_limit is 25, use sysparm_offset=25 to get the next 25 records. |
| `sysparm_display_value` | string ("true" | "false" | "all") | No | Determines the type of data returned in the response. 'false': Returns actual database values (sys_ids for references, numeric values for choices). 'true': Returns display values (names for references, text labels for choices). 'all': Returns both display and actual values. |
| `sysparm_exclude_reference_link` | boolean | No | Flag that indicates whether to exclude Table API links for reference fields. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List ServiceNow Change Requests

**Slug:** `SERVICENOW_GET_SN_CHG_REST_CHANGE_LIST`

Retrieves one or more change requests from ServiceNow based on specified filter criteria. Use when you need to query change management records, monitor pending changes, find changes by state or type, or list all changes assigned to a specific user or group. Supports filtering via encoded queries, pagination via limit/offset, and returns rich change request details including state, priority, dates, assignments, and approvals.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sysparm_limit` | integer | No | Maximum number of change request records to return. Use sysparm_offset for pagination to retrieve additional records. Note: Unusually large values can impact system performance. |
| `sysparm_query` | string | No | Encoded query to filter change requests. Syntax: <col_name><operator><value>. Supports operators: = (exact match), != (not equal), ^ (AND), ^OR (OR), LIKE (contains string), STARTSWITH, ENDSWITH. Example: sysparm_query=state!=7^active=true You can also use ORDERBY and ORDERBYDESC to sort results, e.g., ORDERBYDESCopened_at to sort by most recently opened. |
| `sysparm_offset` | integer | No | Starting record index for pagination. Use sysparm_offset + sysparm_limit to page through large result sets. For example, first call with offset=0, next call with offset=sysparm_limit. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get sn chg rest change model by

**Slug:** `SERVICENOW_GET_SN_CHG_REST_CHANGE_MODEL_BY_ID`

Retrieves a specific change model from ServiceNow using its sys_id. Use this action when you need to fetch detailed information about a particular change model, including its name, description, type, category, workflow, and other configuration settings. This is a read-only operation that does not modify any data in ServiceNow.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the change model to retrieve. This is a 32-character hexadecimal string that uniquely identifies the change model. Example: '7840d2515323101034d1ddeeff7b12a6' |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get sn chg rest change model list

**Slug:** `SERVICENOW_GET_SN_CHG_REST_CHANGE_MODEL_LIST`

Retrieves one or more change models from ServiceNow's Change Management API. Use this action when you need to fetch change model definitions that define the structure and workflow for change requests. Change models determine the type of change (normal, standard, emergency), associated workflows, and other configuration. This is a read-only operation that does not modify any data in ServiceNow. You can retrieve a specific change model by sys_id, or list all change models with optional filtering and pagination.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | No | The unique system ID (sys_id) of a specific change model to retrieve. If specified, returns only the change model with this sys_id. If not specified, returns all change models (with optional filtering). Example: '8766498dc37a3610eb10d8477d013161' |
| `sysparm_limit` | integer | No | Maximum number of change models to return in the response. Defaults to 25 if not specified. Use this with sysparm_offset for pagination. Note: Unusually large limit values can impact system performance. |
| `sysparm_query` | string | No | Encoded query string to filter change models. Uses ServiceNow query syntax. Example: 'active=true' or 'nameLIKEstandard'. Supports operators: =, !=, ^ (AND), ^OR, LIKE, STARTSWITH, ENDSWITH. Example: 'active=true^nameLIKEemergency' |
| `sysparm_offset` | integer | No | Starting record index for pagination. Use this to paginate through results. For example, set sysparm_offset to 25 to retrieve the second page of results when combined with sysparm_limit=25. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Normal Change Request by ID

**Slug:** `SERVICENOW_GET_SN_CHG_REST_CHANGE_NORMAL_BY_ID`

Retrieves a specific normal change request from ServiceNow using its sys_id via the Change Management REST API. Use when you need to fetch detailed information about a particular normal change request, including its state, type, priority, dates, assignments, and approvals. This is a read-only operation that does not modify any data in ServiceNow. The action specifically targets change requests of type 'normal' — if the provided sys_id does not correspond to a normal change request, a 404 error will be returned.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the normal change request to retrieve. This is a 32-character hexadecimal string that uniquely identifies the change request. Example: 'a9e9c33dc61122760072455df62663d2'. The change request must exist and be of type 'normal', or a 404 error will be returned. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List ServiceNow Normal Change Requests

**Slug:** `SERVICENOW_GET_SN_CHG_REST_CHANGE_NORMAL_LIST`

Retrieves one or more normal change requests from ServiceNow's Change Management API. Use this action when you need to query normal change management records, monitor pending normal changes, find normal changes by state or type, or list all normal changes assigned to a specific user or group. Supports filtering via encoded queries, pagination via limit/offset, and returns rich normal change request details including state, priority, dates, assignments, and approvals. This is a read-only operation that does not modify any data in ServiceNow.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sysparm_limit` | integer | No | Maximum number of normal change request records to return. Use sysparm_offset for pagination to retrieve additional records. Note: Unusually large values can impact system performance. |
| `sysparm_query` | string | No | Encoded query to filter normal change requests. Syntax: <col_name><operator><value>. Supports operators: = (exact match), != (not equal), ^ (AND), ^OR (OR), LIKE (contains string), STARTSWITH, ENDSWITH. Example: sysparm_query=state!=7^active=true You can also use ORDERBY and ORDERBYDESC to sort results, e.g., ORDERBYDESCopened_at to sort by most recently opened. |
| `sysparm_offset` | integer | No | Starting record index for pagination. Use sysparm_offset + sysparm_limit to page through large result sets. For example, first call with offset=0, next call with offset=sysparm_limit. |
| `sysparm_display_value` | string ("true" | "false" | "all") | No | Determines the type of data returned in the response. 'false': Returns actual database values (sys_ids for references, numeric values for choices). 'true': Returns display values (names for references, text labels for choices). 'all': Returns both display and actual values. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get sn chg rest change standard by

**Slug:** `SERVICENOW_GET_SN_CHG_REST_CHANGE_STANDARD_BY_ID`

Retrieves a specific standard change request from ServiceNow using its sys_id. Use this action when you need to fetch detailed information about a particular standard change request, including its state, phase, description, assignments, and schedule. This is a read-only operation that does not modify any data in ServiceNow. Standard changes are pre-approved changes following a standardized process defined by the organization.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the standard change request to retrieve. This is a 32-character hexadecimal string that uniquely identifies the standard change request. Example: 'eaf5d21347c12200e0ef563dbb9a7109' |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get sn chg rest change standard list

**Slug:** `SERVICENOW_GET_SN_CHG_REST_CHANGE_STANDARD_LIST`

Retrieves one or more standard change requests from ServiceNow using the Change Management API. Use this action when you need to query standard change requests. Standard changes are a type of change request that follows a pre-approved template and workflow, typically for routine or recurring changes that have been assessed and authorized in advance. Supports filtering via sysparm_query, field selection, pagination, and display value options. Common use cases: Retrieving active standard changes for approval, listing recently submitted standard changes, monitoring standard change status, or finding standard changes by assignee.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sysparm_view` | string | No | UI view for which to render the data. Determines the fields returned in the response. Valid values: desktop, mobile, both. |
| `sysparm_limit` | integer | No | Maximum number of standard change records to return. For requests that exceed this number of records, use pagination via sysparm_offset. Note: Unusually large sysparm_limit values can impact system performance. |
| `sysparm_query` | string | No | Encoded query used to filter the result set. Syntax: sysparm_query=<col_name><operator><value>. Supports operators: =, !=, ^ (AND), ^OR, LIKE, STARTSWITH, ENDSWITH. Example: sysparm_query=state!=4^priority=1 Can also use ORDERBY/ORDERBYDESC for sorting. Example: sysparm_query=ORDERBYDESCopened_at |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response (e.g., 'number,short_description,state,priority'). Invalid fields are ignored. If not specified, all fields are returned. |
| `sysparm_offset` | integer | No | Starting record index for which to begin retrieving records. Use this value to paginate record retrieval. For example, if sysparm_limit is 25, use sysparm_offset=25 to get the next 25 records. |
| `sysparm_display_value` | string ("true" | "false" | "all") | No | Determines the type of data returned in the response. 'false': Returns actual database values (sys_ids for references, numeric values for choices). 'true': Returns display values (names for references, text labels for choices). 'all': Returns both display and actual values. |
| `sysparm_exclude_reference_link` | boolean | No | Flag that indicates whether to exclude Table API links for reference fields. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get ServiceNow Standard Change Template by ID

**Slug:** `SERVICENOW_GET_SN_CHG_REST_CHANGE_STANDARD_TEMPLATE_BY_ID`

Retrieves a specific standard change template from ServiceNow using its sys_id. Use this action when you need to fetch detailed information about a particular standard change template, including its name, description, category, implementation plan, test plan, risk assessment, and other predefined fields. This is a read-only operation that does not modify any data in ServiceNow. This action complements the list action — use the list action to discover template sys_ids, then use this action to retrieve full details of a specific template by its sys_id.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the standard change template to retrieve. This is a 32-character hexadecimal string that uniquely identifies the template. Example: '508e02ec47410200e90d87e8dee49058' |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List ServiceNow Standard Change Templates

**Slug:** `SERVICENOW_GET_SN_CHG_REST_CHANGE_STANDARD_TEMPLATE_LIST`

Retrieves one or more standard change templates from ServiceNow's Change Management API. Use this action when you need to query standard change templates that provide pre-defined structures for creating standard change requests. Standard change templates help ensure consistency in change implementation by providing predefined fields such as category, implementation plan, test plan, and risk assessment. This is a read-only operation that does not modify any data in ServiceNow. Common use cases: Listing available templates for a change request, filtering templates by category or active status, or retrieving templates for display in a user interface.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sysparm_limit` | integer | No | Maximum number of standard change template records to return. Defaults to 25 if not specified. Use sysparm_offset for pagination to retrieve additional records. Note: Unusually large limit values can impact system performance. |
| `sysparm_query` | string | No | Encoded query to filter standard change templates. Uses ServiceNow query syntax to filter results. Example: 'active=true' to only return active templates, or 'category=software' to filter by category. Supports operators: = (exact match), != (not equal), ^ (AND), ^OR (OR), LIKE (contains string), STARTSWITH, ENDSWITH. Can also use ORDERBY/ORDERBYDESC for sorting, e.g., ORDERBYDESCname. |
| `sysparm_offset` | integer | No | Starting record index for pagination. Use sysparm_offset + sysparm_limit to page through large result sets. For example, first call with offset=0, next call with offset=sysparm_limit. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Change Tasks

**Slug:** `SERVICENOW_GET_SN_CHG_REST_CHANGE_TASK`

Retrieves one or more tasks associated with a specific ServiceNow change request. Use this action when you need to fetch the tasks or subtasks related to a change request, such as to view task status, track progress, or list all work items assigned to a change. This is a read-only operation that does not modify any data in ServiceNow. The endpoint returns tasks that are linked to the change request via the task_for field or as child records in the change management workflow.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `change_sys_id` | string | Yes | The unique system ID (sys_id) of the change request whose tasks to retrieve. This is a 32-character hexadecimal string that uniquely identifies the change request. Example: '46e9b4afa9fe198101026e122b85f442'. The change request must exist, or a 404 error will be returned. |
| `sysparm_limit` | integer | No | Maximum number of task records to return. Use sysparm_offset for pagination to retrieve additional records. Note: Unusually large values can impact system performance. |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response. Invalid fields are ignored. If not specified, all fields are returned. Example: 'number,short_description,state,assigned_to' |
| `sysparm_offset` | integer | No | Starting record index for pagination. Use sysparm_offset + sysparm_limit to page through large result sets. For example, first call with offset=0, next call with offset=sysparm_limit. |
| `sysparm_display_value` | string | No | Determines the type of data returned. 'true': Returns display values (names for references, text labels for choices). 'false': Returns actual database values (sys_ids for references, numeric values for choices). 'all': Returns both display and actual values. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get sn cicd app batch results

**Slug:** `SERVICENOW_GET_SN_CICD_APP_BATCH_RESULTS`

Retrieves the results of a batch application install operation from ServiceNow CI/CD. Use this action when you need to check the status and details of a previously initiated batch application install or deployment operation. The result_id should be obtained from the response of the batch operation that was initiated. This is a read-only operation that does not modify any data in ServiceNow. This action is particularly useful for tracking the progress of multi-app deployments or installations, checking individual item success/failure status, and identifying any errors that occurred during the batch operation.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `result_id` | string | Yes | The unique identifier of the batch operation result to retrieve. This is a 32-character hexadecimal string that identifies the batch results record. Obtain this value from the response of a previous batch install operation. Example: 'bb23487e833bf210dd2dc2dfeeaad3c4' |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Instance Scan Result

**Slug:** `SERVICENOW_GET_SN_CICD_INSTANCE_SCAN_RESULT`

Retrieves the current progress and status of a CI/CD instance scan operation in ServiceNow. Use this action when you need to check the status of an ongoing or completed ServiceNow instance scan that validates configurations, detects issues, or checks compliance. The progress_id should be obtained from the response of a previously initiated instance scan operation. This is a read-only operation that queries the current scan status without modifying any data. This action is typically used in a polling loop after initiating an instance scan to determine when the scan completes and to retrieve the scan results once finished.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `progress_id` | string | Yes | The unique identifier for the instance scan progress operation to retrieve. This ID is typically returned from a previous instance scan initiation response. Example: 'test-progress-id-12345' or a system-generated GUID |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get CI/CD Progress

**Slug:** `SERVICENOW_GET_SN_CICD_PROGRESS`

Retrieves the current progress and status of a CI/CD operation in ServiceNow. Use this action when you need to check the status of an ongoing CI/CD pipeline execution, commit operation, or deployment. The progress_id should be obtained from a previous CI/CD operation response. This is a read-only operation that queries the current status without modifying any data.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `progress_id` | string | Yes | The unique identifier for the CI/CD progress operation to retrieve. This ID is typically returned from a previous CI/CD operation such as a pipeline execution, commit, or deployment. Example: 'test' or a system-generated GUID |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get sn cicd testsuite results

**Slug:** `SERVICENOW_GET_SN_CICD_TESTSUITE_RESULTS`

Retrieves the results of a test suite run from ServiceNow CI/CD based on the result ID. Use this action when you need to check the status, completion percentage, or final outcome of a previously initiated test suite execution in the ServiceNow CI/CD pipeline. The result_id should be obtained from the response of a test suite run initiation action. This is a read-only operation that queries the current state without modifying any data.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `result_id` | string | Yes | The unique identifier of the test suite result to retrieve. This ID is returned when a test suite run is initiated. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get stats

**Slug:** `SERVICENOW_GET_STATS`

Retrieves aggregate statistics for a specified ServiceNow table, including COUNT, AVG, MIN, MAX, and SUM calculations. Use this action when you need to perform aggregate queries on ServiceNow tables to get statistical summaries (e.g., count of incidents by state, average priority, min/max values for specific fields, or grouped aggregations). Supports filtering records with sysparm_query, calculating various aggregates, grouping results, and filtering aggregated results with the having clause.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `table_name` | string | Yes | The name of the table to aggregate statistics from (e.g., 'incident', 'sys_user', 'task'). |
| `sysparm_count` | boolean | No | Set to true to return the count of records matching the query. |
| `sysparm_query` | string | No | Encoded query string to filter records before aggregating. Syntax: <col_name><operator><value>. Operators: = (equals), != (not equals), ^ (AND), ^OR (OR), LIKE, STARTSWITH, ENDSWITH. Example: active=true^priority=1 |
| `sysparm_having` | string | No | Having clause to filter aggregated results based on aggregate values. Syntax: <aggregate_function><operator><value>. Example: 'count>10' returns only groups with count greater than 10. |
| `sysparm_group_by` | string | No | Comma-separated list of fields to group results by. When specified, aggregate functions are calculated per group. Example: 'state,active' groups results by state and active status. |
| `sysparm_avg_fields` | string | No | Comma-separated list of numeric fields to calculate average for. Example: 'priority,urgency' calculates average priority and urgency values. |
| `sysparm_max_fields` | string | No | Comma-separated list of fields to calculate maximum value for. Example: 'priority,state' returns maximum priority and state values. |
| `sysparm_min_fields` | string | No | Comma-separated list of fields to calculate minimum value for. Example: 'priority,state' returns minimum priority and state values. |
| `sysparm_sum_fields` | string | No | Comma-separated list of numeric fields to calculate sum for. Example: 'priority' returns sum of all priority values. |
| `sysparm_display_value` | string ("true" | "false" | "all") | No | Display value options for stats query responses |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Table Records by ID

**Slug:** `SERVICENOW_GET_TABLE_BY_ID`

Retrieves multiple records from a specified ServiceNow table using the Table API. Use this action when you need to query and fetch records from any ServiceNow table (e.g., incident, sys_user, problem, change_request). Supports filtering via sysparm_query and field selection via sysparm_fields. This action performs a GET request and is read-only.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `table_name` | string | Yes | The name of the table from which to retrieve records (e.g., 'incident', 'sys_user', 'problem', 'change_request'). |
| `sysparm_query` | string | No | Encoded query used to filter the result set. You can use a UI filter to obtain a properly encoded query. Syntax: sysparm_query=<col_name><operator><value>. <col_name>: Name of the table column to filter against. <operator>: Supports the following values: =: Exactly matches <value>. !=: Does not match <value>. ^: Logically AND multiple query statements. ^OR: Logically OR multiple query statements. LIKE: <col_name> contains the specified string. Only works for <col_name> fields whose data type is string. STARTSWITH: <col_name> starts with the specified string. Only works for <col_name> fields whose data type is string. ENDSWITH: <col_name> ends with the specified string. Only works for <col_name> fields whose data type is string. <value>: Value to match against. All parameters are case-sensitive. Queries can contain more than one entry, such as sysparm_query=<col_name><operator><value>[<operator><col_name><operator><value>]. For example: (sysparm_query=caller_id=javascript:gs.getUserID()^active=true) Encoded queries also support order by functionality. To sort responses based on certain fields, use the ORDERBY and ORDERBYDESC clauses in sysparm_query. Syntax: ORDERBY<col_name> ORDERBYDESC<col_name> For example: sysparm_query=active=true^ORDERBYnumber^ORDERBYDESCcategory This query filters all active records and orders the results in ascending order by number, and then in descending order by category. If part of the query is invalid, such as by specifying an invalid field name, the instance ignores the invalid part. It then returns rows using only the valid portion of the query. You can control this behavior using the property glide.invalid_query.returns_no_rows. Set this property to true to return no rows on an invalid query. Note: The glide.invalid_query.returns_no_rows property controls the behavior of all queries across the instance, such as in lists, scripts (GlideRecord.query()), and web service APIs. |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response. Invalid field names are silently ignored. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Table Record by ID

**Slug:** `SERVICENOW_GET_TABLE_BY_ID2`

Retrieves the record identified by the specified sys_id from the specified table. Use this action when you need to fetch a single record from any ServiceNow table (e.g., incident, sys_user, problem) by providing its table name and unique sys_id. This is a read-only operation that does not modify any data in ServiceNow.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | Sys_id of the record to retrieve. This is a 32-character hexadecimal string that uniquely identifies the record. |
| `table_name` | string | Yes | Name of the table to retrieve the record from. |
| `sysparm_view` | string | No | UI view to use for field selection. |
| `sysparm_fields` | string | No | Comma-separated list of fields to return. |
| `sysparm_display_value` | string ("true" | "false" | "all") | No | Determines the type of data returned in the response. |
| `sysparm_exclude_reference_link` | boolean | No | Exclude reference links in the response. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get table incident by

**Slug:** `SERVICENOW_GET_TABLE_INCIDENT_BY_ID`

Retrieves a single incident record from ServiceNow by its sys_id using the Table API. Use this action when you need to fetch detailed information about a specific incident from ServiceNow's incident table, including its state, priority, assignment, description, and all other standard incident fields. This is a read-only operation that does not modify any data in ServiceNow.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the incident record to retrieve. This is a 32-character hexadecimal string that uniquely identifies the incident. Example: '1c832706732023002728660c4cf6a7b9' |
| `sysparm_view` | string ("desktop" | "mobile" | "both") | No | UI view for which to render the data. Determines the fields returned in the response. |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response. Invalid fields are ignored. |
| `sysparm_display_value` | string ("true" | "false" | "all") | No | Determines the type of data returned, either the actual values from the database or the display values of the fields. Display values are manipulated based on the actual value in the database and user or system settings and preferences. If returning display values, the value that is returned is dependent on the field type. Choice fields: The database value may be a number, but the display value will be more descriptive. Date fields: The database value is in UTC format, while the display value is based on the user's time zone. Encrypted text: The database value is encrypted, while the displayed value is unencrypted based on the user's encryption context. Reference fields: The database value is sys_id, but the display value is a display field of the referenced record. |
| `sysparm_query_category` | string | No | Name of the category to use for queries. |
| `sysparm_exclude_reference_link` | boolean | No | Flag that indicates whether to exclude Table API links for reference fields. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List ServiceNow Incidents

**Slug:** `SERVICENOW_GET_TABLE_INCIDENT_LIST`

Retrieves one or more incident records from the ServiceNow incident table using the Table API. Use this action when you need to query and list incidents from ServiceNow, such as finding active incidents, filtering by priority or state, searching for incidents by caller, or retrieving all incidents assigned to a specific user or group. Supports filtering via encoded queries, field selection, pagination via limit, and returns rich incident details including state, priority, assignments, timestamps, and SLA information. The incident table contains fields for tracking IT service disruptions including caller information, assigned personnel, affected services, priorities, and resolution status.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sysparm_limit` | integer | No | Maximum number of incident records to return. Use pagination for larger result sets. |
| `sysparm_query` | string | No | Encoded query used to filter the result set. Syntax: <col_name><operator><value>. Supports operators: '=' (exact match), '!=' (not equal), '^' (AND), '^OR' (OR), LIKE (contains), STARTSWITH, ENDSWITH. Example: state=2^priority=1 to get active high-priority incidents. Use ORDERBY or ORDERBYDESC to sort results, e.g., ORDERBYDESCopened_at. |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response. Invalid fields are silently ignored. |
| `sysparm_display_value` | boolean | No | Determines if system references should be returned as actual values (false) or display values (true). |
| `sysparm_exclude_reference_link` | boolean | No | Determines whether to exclude reference links from the response. Set to true to simplify the response. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get ServiceNow Tables

**Slug:** `SERVICENOW_GET_TABLES`

Retrieves one or more records from a ServiceNow table using the Table API (GET /api/now/v2/table). Use this action when you need to query and list records from any ServiceNow table, such as finding incidents, tasks, change requests, users, or any other table record. Supports filtering via encoded queries (sysparm_query), field selection (sysparm_fields), pagination via sysparm_limit and sysparm_offset, and display value options. This is a generic table listing action that works with any table name specified in the request. For a list of available tables in the instance, consider using the GetRecordTypes action first to discover table names and labels before querying specific tables.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `table_name` | string | No | The name of the ServiceNow table to query (e.g., 'incident', 'task', 'sys_user', 'change_request'). If not specified, the API may return records from a default or accessible table. Common tables: 'incident', 'task', 'sys_user', 'cmdb_ci', 'change_request', 'problem', 'kb_knowledge'. |
| `sysparm_limit` | integer | No | Maximum number of records to return in the response. For result sets larger than this limit, use sysparm_offset to paginate. Example: sysparm_offset=0 returns records 1-N, then sysparm_offset=N returns the next batch. |
| `sysparm_query` | string | No | Encoded query string to filter the records returned. Syntax: <col_name><operator><value>. Operators: '=' (exact match), '!=' (not equal), '^' (AND), '^OR' (OR), LIKE (contains), STARTSWITH, ENDSWITH. Example: active=true^priority=1 to get active high-priority records. Use ORDERBY or ORDERBYDESC to sort results, e.g., ORDERBYDESCopened_at. |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response. Invalid field names are silently ignored. Example: 'sys_id,name,state,priority,short_description' |
| `sysparm_offset` | integer | No | Starting record offset for pagination. Set to sysparm_offset + sysparm_limit to page through large result sets. For example, to get records 101-200, set sysparm_offset=100 with sysparm_limit=100. |
| `sysparm_no_count` | boolean | No | Flag that indicates whether to execute a select count(*) query on the table to return the number of rows in the associated table. |
| `sysparm_display_value` | string ("true" | "false" | "all") | No | Display value options for table query responses |
| `sysparm_exclude_reference_link` | boolean | No | Set to true to exclude Table API links for reference fields in the response. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get user

**Slug:** `SERVICENOW_GET_USER`

Retrieves a specific user record from ServiceNow using its sys_id. Use this action when you need to fetch detailed information about a particular user, such as their contact details, department, location, manager, or account status. This is a read-only operation that does not modify any data in ServiceNow.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the user record to retrieve. This is a 32-character hexadecimal string that uniquely identifies the user in ServiceNow. Example: '02826bf03710200044e0bfc8bcbe5d3f' |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response. Invalid fields are ignored. |
| `sysparm_display_value` | boolean | No | Determines the type of data returned, either the actual values from the database or the display values of the fields. Display values are manipulated based on the actual value in the database and user or system settings and preferences. If returning display values, the value that is returned is dependent on the field type. Choice fields: The database value may be a number, but the display value will be more descriptive. Date fields: The database value is in UTC format, while the display value is based on the user's time zone. Encrypted text: The database value is encrypted, while the displayed value is unencrypted based on the user's encryption context. Reference fields: The database value is sys_id, but the display value is a display field of the referenced record. |
| `sysparm_exclude_reference_link` | boolean | No | Flag that indicates whether to exclude Table API links for reference fields. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get users

**Slug:** `SERVICENOW_GET_USERS`

Retrieves multiple user records from the ServiceNow sys_user table with optional filtering and pagination. Use this action when you need to query and fetch a list of users from ServiceNow, such as finding active users, users by department, or users matching specific criteria. Supports filtering via sysparm_query, field selection, pagination via sysparm_limit and sysparm_offset, and display value options. This is a read-only operation that does not modify any data.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sysparm_limit` | integer | No | Maximum number of user records to return. Use pagination (sysparm_offset) for result sets larger than this limit. |
| `sysparm_query` | string | No | Encoded query used to filter the result set. Syntax: sysparm_query=<col_name><operator><value>. Operators: '=' (exact match), '!=' (not equal), '^' (AND), '^OR' (OR), LIKE, STARTSWITH, ENDSWITH. Example: active=true^emailLIKEsomething.com |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response. Invalid field names are silently ignored. Example: 'sys_id,user_name,first_name,last_name,email,active' |
| `sysparm_offset` | integer | No | Starting record offset for pagination. Use with sysparm_limit to paginate through results. |
| `sysparm_display_value` | string | No | Determines the format of field values in the response. 'false': Returns actual database values (sys_ids for references). 'true': Returns display values (names for references). 'all': Returns both display and actual values. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List ServiceNow Attachments

**Slug:** `SERVICENOW_LIST_ATTACHMENTS`

Retrieves metadata for multiple file attachments from ServiceNow's Attachment API. Use this action when you need to list and filter attachments across the instance, including filtering by table name, file name, content type, size, or other attachment properties. Supports pagination via sysparm_limit parameter. Note: This returns metadata only; actual file content must be downloaded separately using the sys_id or download_link provided in the response.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sysparm_limit` | integer | No | Limit to be applied on pagination. Use this parameter to limit the number of attachment records returned. For requests that exceed this limit, use sysparm_offset to paginate through results. Note: Unusually large sysparm_limit values can impact system performance. |
| `sysparm_query` | string | No | Encoded query to filter attachments. Queries are relative to the sys_attachment table. Syntax follows ServiceNow encoded query format: <column><operator><value>. Operators: = (equals), != (not equals), ^ (AND), ^OR (OR), LIKE (contains), STARTSWITH, ENDSWITH. Examples: file_nameLIKEreport - attachments with 'report' in the file name; table_name=incident - attachments on incident records; content_type=image%2Fpng - PNG images; size_bytes>1000000 - files larger than 1MB. Use ORDERBY or ORDERBYDESC for sorting: ORDERBYfile_name, ORDERBYDESCsys_created_on. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List CMDB Linux Servers

**Slug:** `SERVICENOW_LIST_CMDB_CI_LINUX_SERVERS`

Retrieves Linux server configuration items (CIs) from the ServiceNow CMDB using the cmdb_ci_linux_server class. Use this action when you need to query Linux servers from the CMDB, such as retrieving all Linux servers for inventory reporting, filtering by operational status, environment, or other attributes. Supports filtering via sysparm_query and pagination via sysparm_limit and sysparm_offset. This is a read-only operation that does not modify any data in ServiceNow.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sysparm_limit` | integer | No | Maximum number of Linux server records to return. Use pagination for larger result sets. |
| `sysparm_query` | string | No | Encoded query to filter Linux servers. Syntax: <col_name><operator><value>. Operators: '=' (exact match), '!=' (not equal), '^' (AND), '^OR' (OR), LIKE, STARTSWITH, ENDSWITH. Example: operational_status=1^environment=Production |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response. Invalid field names are silently ignored. Example: 'sys_id,name,ip_address,operational_status' |
| `sysparm_offset` | integer | No | Starting record offset for pagination. Set to sysparm_offset + sysparm_limit to paginate through results. |
| `sysparm_display_value` | string | No | Determines the format of field values in the response. 'false': Returns actual database values (sys_ids for references, numeric values for choices). 'true': Returns display values (names for references, text labels for choices). 'all': Returns both display and actual values. |
| `sysparm_exclude_reference_link` | boolean | No | Set to true to exclude Table API links for reference fields in the response. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List CMDB Configuration Items

**Slug:** `SERVICENOW_LIST_CMDBC_IS`

Retrieves configuration items (CIs) from the ServiceNow CMDB using the base cmdb_ci class. Use this action when you need to query all configuration items from the CMDB, regardless of their specific type (servers, computers, databases, applications, etc.). This endpoint queries the base cmdb_ci class which contains all CIs. Supports filtering via sysparm_query and pagination via sysparm_limit and sysparm_offset.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sysparm_limit` | integer | No | Maximum number of configuration item records to return. Use pagination for larger result sets. |
| `sysparm_query` | string | No | Encoded query to filter configuration items. Syntax: <col_name><operator><value>. Operators: '=' (exact match), '!=' (not equal), '^' (AND), '^OR' (OR), LIKE, STARTSWITH, ENDSWITH. Example: operational_status=1^environment=Production |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response. Invalid field names are silently ignored. Example: 'sys_id,name,ip_address,operational_status' |
| `sysparm_offset` | integer | No | Starting record offset for pagination. Set to sysparm_offset + sysparm_limit to paginate through results. |
| `sysparm_display_value` | string | No | Determines the format of field values in the response. 'false': Returns actual database values (sys_ids for references, numeric values for choices). 'true': Returns display values (names for references, text labels for choices). 'all': Returns both display and actual values. |
| `sysparm_exclude_reference_link` | boolean | No | Set to true to exclude Table API links for reference fields in the response. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List CMDB Relationship Types

**Slug:** `SERVICENOW_LIST_CMDB_REL_TYPES`

Retrieves CMDB relationship types from the ServiceNow cmdb_rel_type table using the Table API. Use this action when you need to discover what types of relationships are defined between Configuration Items (CIs) in the CMDB. Common relationship types include 'Runs on', 'Contains', 'Depends on', 'Hosted on', and 'Connects to'. This is useful for understanding the relationship schema before creating or querying CI relationships. Supports filtering via sysparm_query, pagination via sysparm_limit and sysparm_offset, field selection via sysparm_fields, and display value formatting via sysparm_display_value.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sysparm_limit` | integer | No | Maximum number of relationship type records to return. Use pagination for larger result sets. |
| `sysparm_query` | string | No | Encoded query to filter relationship types. Syntax: <col_name><operator><value>. Operators: '=' (exact match), '!=' (not equal), '^' (AND), '^OR' (OR), LIKE, STARTSWITH, ENDSWITH. Example: active=true^nameLIKEserver |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response. Invalid field names are silently ignored. Example: 'sys_id,name,child_class_name,parent_class_name' |
| `sysparm_offset` | integer | No | Starting record offset for pagination. Set to sysparm_offset + sysparm_limit to paginate through results. |
| `sysparm_display_value` | string | No | Determines the format of field values in the response. 'false': Returns actual database values (sys_ids for references, numeric values for choices). 'true': Returns display values (names for references, text labels for choices). 'all': Returns both display and actual values. |
| `sysparm_exclude_reference_link` | boolean | No | Set to true to exclude Table API links for reference fields in the response. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Service Catalog Catalogs

**Slug:** `SERVICENOW_LIST_SERVICE_CATALOG_CATALOGS`

Retrieves a list of ServiceNow Service Catalog catalogs to which the user has access. Use this action when you need to fetch available service catalogs from ServiceNow, such as displaying available catalogs to users or filtering catalogs by name or description.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sysparm_text` | string | No | Search text to filter catalogs by title or description |
| `sysparm_limit` | integer | No | Maximum number of catalogs to return. Defaults to 25 if not specified. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Refresh Impacted Services for Change

**Slug:** `SERVICENOW_REFRESH_IMPACTED_SERVICES`

Refreshes and repopulates the impacted services/configuration items for a change request in ServiceNow using the Change Management REST API. Use this action when you need to recalculate and update the list of impacted services or configuration items for a change request. This is commonly used when: - The change request's scope has changed - Configuration items need to be re-evaluated for impact - A new CI is added to the change and its impact needs to be computed Note: This action triggers a refresh of the impacted services based on the change request's current configuration items and may modify the associated services.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the change request for which to refresh impacted services. This is a 32-character hexadecimal string that uniquely identifies the change request record. Example: '46e9b4afa9fe198101026e122b85f442' |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Retrieve sn cicd update set

**Slug:** `SERVICENOW_RETRIEVE_SN_CICD_UPDATE_SET`

Retrieves an update set with a given sys_id from the ServiceNow CICD (Continuous Integration/Continuous Delivery) plugin. Use this action when you need to retrieve an update set from the CICD plugin to access its contents, including remote updates and application details. This operation is typically used as a preliminary step before deploying or reviewing update set changes through the CICD pipeline. The action requires the sys_id of an existing update set that is available in the CICD system. After successful retrieval, the update set details including its state, application info, and remote updates will be returned.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `update_set_id` | string | Yes | The sys_id of the update set to retrieve from the CICD plugin. This is the unique system identifier assigned to the update set. |
| `update_source_id` | string | No | The sys_id of the update source. Either update_source_id or update_source_instance_id is required. |
| `update_source_instance_id` | string | No | The sys_id of the update source instance. Either update_source_id or update_source_instance_id is required. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Schedule change first available

**Slug:** `SERVICENOW_SCHEDULE_CHANGE_FIRST_AVAILABLE`

Updates the planned start and end times of a ServiceNow change request to the first available schedule slot. Use this action when you need to automatically schedule a change request at the earliest available time slot based on the configured calendar and availability. This is useful for finding optimal scheduling windows when the specific timing is less important than scheduling as soon as possible. This action sends a PATCH request to the Change Management API endpoint, which automatically calculates and assigns the first available time slot for the change request. Note: The change request must exist and be in a schedulable state (typically 'Open' or 'Approved'). The user must have appropriate permissions to modify the change request schedule.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `change_sys_id` | string | Yes | The unique system ID (sys_id) of the change request to schedule. This is a 32-character hexadecimal string that uniquely identifies the change request. Example: '46e9b4afa9fe198101026e122b85f442'. The change request must exist and be in a schedulable state. |
| `duration_in_seconds` | integer | No | The expected duration of the change request in seconds. This is used to find the first available time slot that can accommodate the change. Default is 3600 seconds (1 hour). Minimum recommended is 300 seconds (5 minutes). |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update cmdb csdm app service populate service

**Slug:** `SERVICENOW_UPDATE_CMDB_CSDM_APP_SERVICE_POPULATE_SERVICE`

Populates an Application Service with CI (Configuration Item) relationships based on the CSDM (Common Service Data Model) model. Use this action when you need to automatically discover and populate the CIs (Configuration Items) and their relationships that belong to an application service in ServiceNow's CMDB. This endpoint has been deprecated by ServiceNow. Consider using alternative approaches for CI population.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `service_sys_id` | string | Yes | The sys_id of the Application Service to populate with CI relationships. This is a required path parameter that uniquely identifies the application service record. Example: '17c04876833bf210dd2dc2dfeeaad3ee' |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update CMDB CSDM App Service Service Details

**Slug:** `SERVICENOW_UPDATE_CMDBCSDM_APP_SERVICE_SERVICE_DETAILS`

Updates the service details for a specific application service in the CMDB CSDM (Common Service Data Model). Use this action when you need to modify the metadata, ownership, tier classification, or operational details of an application service in ServiceNow's Configuration Management Database. This endpoint specifically updates the service_details attributes of the application service identified by its sys_id. This is an update (PUT) operation, so the provided fields will be set on the record. Fields not included in the request will retain their current values unless otherwise specified by the API. Common use cases: Updating application service ownership, changing tier or environment classifications, modifying criticality levels, or updating operational status.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | No | The display name of the application service. This is the human-readable name used to identify the service. Example: 'Payment Processing Service' |
| `tier` | string | No | The tier classification of the application service. Valid values: '1' = Prescription, '2' = Billing, '3' = Monitoring, '4' = Custom Application Services. Use the numeric string value corresponding to the desired tier. |
| `criticality` | string | No | The criticality level of the application service for business operations. Valid values: '1' = High, '2' = Medium, '3' = Low. Use the numeric string value corresponding to the criticality level. |
| `description` | string | No | A detailed description of the application service explaining its purpose, functionality, and business value. Example: 'Handles all payment processing including credit cards and ACH transfers' |
| `environment` | string | No | The deployment environment for the application service. Valid values: '1' = Development, '2' = Test, '3' = Production, '4' = Staging. Use the numeric string value corresponding to the environment. |
| `owning_team` | string | No | The sys_id of the team responsible for owning and maintaining the application service. Reference to sn_orgstructure_team table. Example: 'xyz987654321fedcba9876543210zyxw' |
| `primary_owner` | string | No | The sys_id of the primary owner/person responsible for this application service. Reference to sys_user table. Example: 'usr1234567890abcdef1234567890ab' |
| `service_sys_id` | string | Yes | The unique system ID (sys_id) of the application service record to update. This is a 32-character hexadecimal string that identifies the specific application service in the cmdb_ci_appl_service table. Example: 'abc1234567890abcdef1234567890ab' |
| `secondary_owner` | string | No | The sys_id of the secondary/backup owner for this application service. Reference to sys_user table. Example: 'usr987654321fedcba9876543210zyxw' |
| `operational_status` | string | No | The current operational status of the application service. Typical values: '1' = Operational, '2' = Non-Operational, '3' = Decommissioned, '7' = Under Maintenance. Example: '1' |
| `owning_application` | string | No | The sys_id of the application that this service supports. Reference to cmdb_ci_appl table. Example: 'app1234567890abcdef1234567890ab' |
| `business_criticality` | string | No | Additional business criticality designation or notes. Can include details about why the service is critical and any associated SLAs. Example: 'Mission critical - 99.99% uptime required' |
| `owning_business_service` | string | No | The sys_id of the parent business service that owns this application service. Reference to cmdb_ci_service table. Example: 'svc1234567890abcdef1234567890ab' |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update cmdb instance by

**Slug:** `SERVICENOW_UPDATE_CMDB_INSTANCE_BY_ID`

Updates an existing configuration item (CI) record in the ServiceNow CMDB by its sys_id. Use this action when you need to modify attributes of a specific configuration item in the Configuration Management Database. This action sends a PUT request to the CMDB Instance API endpoint, replacing the specified attributes of the CI record. Note: The classname and sys_id are required path parameters. Only include the attributes you want to update in the request. This action performs a full update operation - fields not included in the request will retain their current values unless the API enforces specific default behavior. Common use cases: Updating CI operational status, changing ownership, modifying location information, updating IP addresses, changing assignment groups, or updating custom CMDB fields.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the configuration item record to update. This is a 32-character hexadecimal string that uniquely identifies the CI. Example: '1234567890abcdef1234567890abcdef' |
| `classname` | string | Yes | The name of the CMDB class (table) that the configuration item belongs to. This is a required path parameter. Common class names include: cmdb_ci (generic CI), cmdb_ci_server, cmdb_ci_database, cmdb_ci_network_adapter, cmdb_ci_ip_switch, cmdb_ci_lb, cmdb_ci_storage_device, cmdb_ciPrinter, cmdb_ci_appl, etc. Example: 'cmdb_ci' or 'cmdb_ci_server' |
| `attributes` | object | No | A dictionary of CI attribute name-value pairs to update. These are the field names and values specific to the CMDB class. Common attributes include: name, short_description, description, serial_number, ip_address, mac_address, manufacturer, model_number, install_status, operational_status, owned_by, assigned_to, assignment_group, location, etc. Example: {'name': 'Production Web Server', 'operational_status': '1'} |
| `additional_attributes` | object | No | Additional CMDB attributes to update that are not explicitly listed above. Use this for custom fields (prefixed with u_) or less common fields. Example: {'u_custom_field': 'value', 'u_environment': 'production'} |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update CMDB Instance by ID

**Slug:** `SERVICENOW_UPDATE_CMDB_INSTANCE_BY_ID2`

Updates an existing Configuration Item (CI) instance in the ServiceNow CMDB. Use this action when you need to modify the attributes of a specific CMDB record, such as updating its description, operational status, assignment group, IP address, or any other supported field. This action sends a PATCH request to the CMDB Instance API, replacing only the specified attributes on the target record. This is an update operation — changes made by this action can be reverted by calling this action again with corrected values.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `cost` | string | No | Cost or price of the configuration item. Example: '15000.00' |
| `fqdn` | string | No | Fully qualified domain name of the configuration item. Example: 'web-server-prod-01.example.com' |
| `name` | string | No | Display name of the configuration item. Example: 'web-server-prod-01' |
| `sys_id` | string | Yes | The 32-character hexadecimal sys_id of the CMDB instance to update. This uniquely identifies the specific configuration item record. Example: '00a96c0d3790200044e0bfc8bcbe5db4' |
| `company` | string | No | Sys_id of the company that owns or is associated with this configuration item. |
| `location` | string | No | Physical location or data center of the configuration item. Example: 'NYC-DC-1', 'EU-West-1' |
| `classname` | string | Yes | The CMDB table class name that identifies the type of configuration item (CI) to update. Common values include 'cmdb_ci' (generic CI), 'cmdb_ci_server', 'cmdb_ci_database', 'cmdb_ci_appl', 'cmdb_ci_service', 'cmdb_ci_network_device', 'cmdb_ci_hardware', etc. Example: 'cmdb_ci' |
| `host_name` | string | No | Hostname of the configuration item. Example: 'web-server-prod-01' |
| `ip_address` | string | No | Primary IP address of the configuration item. Example: '192.168.1.100' |
| `managed_by` | string | No | Sys_id of the user or group that manages this configuration item. |
| `description` | string | No | Detailed description of the configuration item explaining its purpose and functionality. |
| `environment` | string | No | Environment type for the configuration item. Common values: 'Development', 'Test', 'Production', 'Staging', 'QA'. Example: 'Production' |
| `manufacturer` | string | No | Manufacturer or vendor of the configuration item. Example: 'Dell Inc.', 'Cisco Systems' |
| `model_number` | string | No | Model number of the configuration item. Example: 'PowerEdge R740', 'UCS-B200-M4' |
| `supported_by` | string | No | Sys_id of the user or group that provides support for this configuration item. |
| `purchase_date` | string | No | Date the configuration item was purchased (format: YYYY-MM-DD). Example: '2024-01-15' |
| `serial_number` | string | No | Serial number assigned by the manufacturer. Example: 'ABC123XYZ' |
| `install_status` | string | No | Installation status of the configuration item. Common values: '1' = Installed, '2' = On Order, '3' = On Maintenance, '4' = Stocked, '6' = In Service, '7' = Retired. Example: '1' |
| `assignment_group` | string | No | Sys_id of the assignment group responsible for this configuration item. |
| `short_description` | string | No | Brief summary or title of the configuration item. Example: 'Production web server for app-1' |
| `operational_status` | string | No | Operational status of the configuration item. Common values: '1' = Operational, '2' = Non-Operational, '3' = Decommissioned, '7' = Under Maintenance. Example: '1' |
| `warranty_expiration` | string | No | Warranty expiration date for the configuration item (format: YYYY-MM-DD). Example: '2027-01-15' |
| `additional_attributes` | object | No | Additional CMDB instance fields to update that are not explicitly listed above. Use this for custom fields (prefixed with u_) or less common fields supported by the target class. Example: {'u_custom_field': 'value', 'u_environment_tier': 'tier-3'} |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update conversation member drop

**Slug:** `SERVICENOW_UPDATE_CONVERSATION_MEMBER_DROP`

Drops an agent from a conversation in ServiceNow using the Conversation Member API. Use this action when you need to remove an agent or user from an active conversation. This operation requires the wa_integration_user role. The member will be immediately removed from the conversation and will no longer receive messages or events for it. This action is irreversible — once a member is dropped from a conversation, they cannot be automatically restored through this API and would need to be re-added manually.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `user_id` | string | Yes | The unique identifier of the user/agent to drop from the conversation. This is a path parameter that identifies the conversation member to remove. The user must be currently assigned to a conversation for this operation to succeed. |
| `conversation_id` | string | No | The sys_id of the conversation to drop the member from. If not provided, the API will attempt to drop the member from the default conversation. This is recommended if the user is a member of multiple conversations. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update incident by

**Slug:** `SERVICENOW_UPDATE_INCIDENT_BY_ID`

Updates an existing incident in ServiceNow identified by its sys_id using the Table API. Use this action when you need to modify an existing incident, such as updating its state, changing assignments, adding notes, updating priority, or resolving/closing the incident. Only the fields provided in the request will be updated; all other fields retain their current values. Note: This action performs a PUT (replace) operation. Only include the fields you want to update. This is a destructive operation in that it modifies data, but the changes can be reverted by calling this action again with corrected values.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `state` | string | No | Current state of the incident. Common values: '1'=New, '2'=In Progress, '3'=On Hold, '4'=Resolved, '5'=Closed, '6'=Cancelled. Use the numeric string value corresponding to the desired state. |
| `active` | string | No | Boolean indicating whether the incident is active. Set to 'true' to activate or 'false' to deactivate. |
| `impact` | string | No | Impact level of the incident (business criticality). Typical values: '1'=High, '2'=Medium, '3'=Low. Use the numeric string value corresponding to the impact level. |
| `sys_id` | string | Yes | The unique system ID (sys_id) of the incident to update. This is a 32-character hexadecimal string that uniquely identifies the incident. Example: '1c832706732023002728660c4cf6a7b9' |
| `cmdb_ci` | string | No | The sys_id of the Configuration Item (CI) associated with the incident. Reference to cmdb_ci table. Example: 'f9e9c33dc61122760072455df62663d2' |
| `urgency` | string | No | Urgency level of the incident (business criticality based on business needs). Typical values: '1'=High, '2'=Medium, '3'=Low. Use the numeric string value corresponding to the urgency level. |
| `category` | string | No | Category or classification of the incident. Examples: 'network', 'hardware', 'software', 'database'. Values must match valid categories defined in your ServiceNow instance. |
| `comments` | string | No | Additional comments or notes on the incident (visible to end users). Example: 'Updated user on status of the incident' |
| `due_date` | string | No | Expected resolution date/time from assigned user. Format: ISO 8601 datetime string or YYYY-MM-DD HH:MM:SS. Example: '2024-12-01 17:00:00' |
| `location` | string | No | The sys_id of the location where the caller or service is located. Reference to cmn_location table. Example: 'abcdef1234567890abcdef1234567890' |
| `made_sla` | string | No | Boolean indicating whether the SLA was met (true/false as string). Example: 'true' |
| `priority` | string | No | Priority level of the incident. Typical values: '1'=Critical, '2'=High, '3'=Medium, '4'=Low, '5'=Planning. Use the numeric string value corresponding to the priority. |
| `caller_id` | string | No | The sys_id of the person who reported the incident. Reference to sys_user table. Example: '681ccaf9c0a8016400b98a4e52c54f82' |
| `closed_at` | string | No | Timestamp when the incident was closed. Format: ISO 8601 datetime string or YYYY-MM-DD HH:MM:SS. Example: '2024-12-01 15:00:00' |
| `closed_by` | string | No | The sys_id of the user who closed the incident. Reference to sys_user table. Example: '681ccaf9c0a8016400b98a4e52c54f82' |
| `knowledge` | string | No | Boolean indicating whether the incident is linked to a knowledge base article (true/false as string). Example: 'false' |
| `close_code` | string | No | Resolution code when closing the incident. Examples: 'Resolved (Temporary Fix)', 'Closed (Permanent Fix)', 'Closed (Workaround)'. Values must match valid close codes defined in your ServiceNow instance. |
| `escalation` | string | No | Escalation status of the incident. Typical values: 'normal', 'escalated'. Values must match valid escalation values defined in your ServiceNow instance. |
| `problem_id` | string | No | Sys_id of the related problem record, if one exists. Reference to problem table. Example: 'c9e9c33dc61122760072455df62663d2' |
| `work_notes` | string | No | Internal work notes on the incident (not visible to end users). Example: 'Checked logs and found service restart resolved the issue' |
| `assigned_to` | string | No | The sys_id of the user assigned to work on the incident. Reference to sys_user table. Example: '681ccaf9c0a8016400b98a4e52c54f82' |
| `close_notes` | string | No | Notes added when closing the incident. Example: 'Issue resolved by restarting the email service' |
| `description` | string | No | Detailed description of the incident. Example: 'User unable to access email after password reset' |
| `hold_reason` | string | No | Reason the incident is on hold. Example: 'Waiting for user feedback' |
| `resolved_at` | string | No | Timestamp when the incident was resolved. Format: ISO 8601 datetime string or YYYY-MM-DD HH:MM:SS. Example: '2024-12-01 14:30:00' |
| `resolved_by` | string | No | The sys_id of the user who resolved the incident. Reference to sys_user table. Example: '681ccaf9c0a8016400b98a4e52c54f82' |
| `subcategory` | string | No | Subcategory of the incident. Must correspond to a valid subcategory for the selected category. Example: 'email' under 'software' |
| `upon_reject` | string | No | Action to take upon rejection. Example: 'cancel' |
| `contact_type` | string | No | Method by which the incident was reported. Examples: 'phone', 'email', 'self-service', 'walk-in'. Values must match valid contact types defined in your ServiceNow instance. |
| `upon_approval` | string | No | Action to take upon approval. Example: 'proceed' |
| `correlation_id` | string | No | Correlation ID for linking related incidents or external references. Example: 'EXT-12345' |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response (e.g., 'number,short_description,state'). Invalid fields are ignored. If not specified, all fields are returned. |
| `parent_incident` | string | No | Sys_id of the parent incident (can be used to collect incidents for the same root issue). Reference to incident table. Example: 'a9e9c33dc61122760072455df62663d2' |
| `assignment_group` | string | No | The sys_id of the group assigned to the incident. Reference to sys_user_group table. Example: '287e8906c61122730024e53cf3104b26' |
| `business_service` | string | No | The sys_id of the business service affected by the incident. Reference to service_offering or business service table. Example: 'b1e9c33dc61122760072455df62663d2' |
| `short_description` | string | No | Brief summary or title of the incident. Example: 'Cannot access email system' |
| `correlation_display` | string | No | Display text for the correlation ID. Example: 'External Ticket #12345' |
| `sysparm_display_value` | boolean | No | Determines the type of data returned in the response. false: Returns actual database values (sys_ids for references, numeric values for choices). true: Returns display values (names for references, text labels for choices). all: Returns both display and actual values. |
| `sysparm_input_display_value` | boolean | No | Set to true if providing display values (e.g., user names) instead of sys_ids in request fields. When false (default), reference fields must contain sys_ids. |
| `sysparm_exclude_reference_link` | boolean | No | Set to true to exclude Table API links for reference fields in the response. Recommended to set to true to reduce response size. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update incident by id2

**Slug:** `SERVICENOW_UPDATE_INCIDENT_BY_ID2`

Updates an existing incident record in ServiceNow using the Table API. Use this action when you need to modify an existing incident, such as updating its state, changing assignments, adding work notes, updating priority/urgency, or modifying any other incident field. This action sends a PUT request to the Table API endpoint for the incident table at /api/now/table/incident/{sys_id}. This action is commonly used to resolve an incident by setting the state to 'Resolved' (6) and optionally providing resolution notes and resolved_at timestamp. Only include the fields you want to update in the request. Fields not included will retain their current values. This operation modifies data but changes can be reverted by calling this action again with corrected values.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `state` | string ("1" | "2" | "3" | "4" | "5" | "6" | "7" | "8" | "9") | No | Incident state values in ServiceNow |
| `impact` | string | No | Impact level of the incident (1=High, 2=Medium, 3=Low). Indicates the effect on the business or users. |
| `sys_id` | string | Yes | The unique system ID (sys_id) of the incident to update. This is a 32-character hexadecimal string that uniquely identifies the incident record. Example: '46b9490da9fe1981003c938dab89bda3' |
| `urgency` | string | No | Urgency level of the incident (1=High, 2=Medium, 3=Low). Indicates how quickly a response is needed. |
| `category` | string | No | Category or classification of the incident (e.g., 'network', 'hardware', 'software', 'database'). |
| `priority` | string ("1" | "2" | "3" | "4" | "5") | No | Incident priority values in ServiceNow |
| `caller_id` | string | No | Sys_id of the user who reported the incident. |
| `work_notes` | string | No | Internal work notes visible only to support staff (not visible to end users). Use for documenting investigation progress, actions taken, and resolution steps. |
| `assigned_to` | string | No | Sys_id of the user assigned to handle the incident. Example: 'usr789xyz012abc345def678ghi901' |
| `close_notes` | string | No | Notes added when closing the incident, typically explaining the resolution. |
| `description` | string | No | Detailed description of the incident, including steps to reproduce, error messages, and any relevant context. Example: 'Users in Building A are unable to access the internal network since 9am' |
| `resolved_at` | string | No | Timestamp when the incident was resolved (format: YYYY-MM-DD HH:MM:SS). |
| `subcategory` | string | No | Subcategory of the incident (e.g., 'router', 'firewall', 'wifi'). |
| `contact_type` | string | No | Method of contact (e.g., 'phone', 'email', 'self-service', 'chat'). |
| `sysparm_view` | string ("desktop" | "mobile" | "both") | No | UI view options for ServiceNow API |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response (e.g., 'number,short_description,state'). Invalid fields are ignored. If not specified, all fields are returned. |
| `assignment_group` | string | No | Sys_id of the group assigned to the incident. Example: 'grp456def789ghi012jkl345mno678' |
| `short_description` | string | No | Brief summary or title of the incident. Required when creating a new incident. This should be a concise description of the issue visible to end users. Example: 'Network connectivity issue in Building A' |
| `sysparm_display_value` | string ("true" | "false" | "all") | No | Determines the type of data returned in the response. 'false': Returns actual database values (sys_ids for references, numeric values for choices). 'true': Returns display values (names for references, text labels for choices). 'all': Returns both display and actual values. |
| `sysparm_input_display_value` | boolean | No | Set to true if providing display values (e.g., user names) instead of sys_ids in the request body for reference fields. When false (default), reference fields must contain sys_ids. |
| `sysparm_exclude_reference_link` | boolean | No | Set to true to exclude Table API links for reference fields in the response. Recommended to set to true to reduce response size. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update openframe voice interaction

**Slug:** `SERVICENOW_UPDATE_OPENFRAME_VOICE_INTERACTION`

Updates an existing voice interaction record in ServiceNow OpenFrame. Use this action when you need to modify an existing voice interaction record, such as updating its status, changing assignment, adding notes, or resolving the interaction. This action sends a PATCH request to the OpenFrame voice-interaction API, allowing partial updates of the record fields. Note: Only include the fields you want to update in the request. Fields not included will retain their current values.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `notes` | string | No | Internal notes or comments about the voice interaction. |
| `state` | string | No | Current state or status of the voice interaction (e.g., 'open', 'in_progress', 'closed'). |
| `priority` | string | No | Priority level of the voice interaction (e.g., '1' for critical, '2' for high, '3' for normal, '4' for low). |
| `caller_id` | string | No | sys_id of the user who initiated the voice interaction. |
| `assigned_to` | string | No | sys_id of the user assigned to handle the voice interaction. |
| `description` | string | No | Detailed description of the voice interaction. |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response (e.g., 'number,short_description,state'). |
| `resolution_code` | string | No | Code indicating how the interaction was resolved (e.g., 'resolved', 'escalated', 'transferred'). |
| `assignment_group` | string | No | sys_id of the group assigned to handle the voice interaction. |
| `resolution_notes` | string | No | Notes documenting the resolution of the voice interaction. |
| `short_description` | string | No | A brief summary or title describing the voice interaction. |
| `interaction_sys_id` | string | Yes | The unique system ID (sys_id) of the voice interaction record to update. This is a path parameter. |
| `sysparm_display_value` | string ("true" | "false" | "all") | No | Determines the type of data returned in the response. 'false': Returns actual database values (sys_ids for references, numeric values for choices). 'true': Returns display values (names for references, text labels for choices). 'all': Returns both display and actual values. |
| `sysparm_input_display_value` | boolean | No | Set to true if providing display values instead of sys_ids for reference fields. |
| `sysparm_exclude_reference_link` | boolean | No | Set to true to exclude Table API links for reference fields in the response. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update servicecatalog cart

**Slug:** `SERVICENOW_UPDATE_SERVICECATALOG_CART`

Updates an existing item in the ServiceNow Service Portal shopping cart. Use this action when you need to modify the quantity or variables of a cart item in the Service Catalog before checking out. This action sends a PUT request to the Service Catalog cart API endpoint, updating the specified cart item. Use when you need to change the quantity of an item in a user's Service Portal shopping cart or update catalog item variables. The cart_item_id is required, and at least one of sysparm_quantity or variables should be provided.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `variables` | object | No | A dictionary of catalog item variable name-value string pairs to update. These are the variables associated with the catalog item. Example: {'u_department': 'IT', 'u_justification': 'New laptop needed'} |
| `cart_item_id` | string | Yes | The unique system ID (sys_id) of the cart item to update in the current shopping cart. This is a 32-character hexadecimal string that uniquely identifies the cart item. Example: 'da46c07e83fbf210dd2dc2dfeeaad346'. The cart item must exist in the current user's cart. |
| `sysparm_quantity` | integer | No | The new quantity for the cart item. Must be a positive integer (minimum 1). If not provided or set to null, the quantity remains unchanged. Example: 3 |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update servicecatalog items submit guide

**Slug:** `SERVICENOW_UPDATE_SERVICECATALOG_ITEMS_SUBMIT_GUIDE`

Submits an order guide in ServiceNow's Service Catalog with the specified variable values. Use this action when a user needs to submit an order guide in ServiceNow's Service Catalog, providing variable values for the items within the order guide. The action retrieves the configured contents of the order guide with the submitted variable values and calculates pricing totals. This is commonly used to preview and submit order guides that contain pre-configured sets of catalog items (e.g., laptop requests, software bundles). The action sends a PUT request with the order guide sys_id and variable values, and returns the order guide items with calculated pricing information. Note: This action is idempotent - submitting the same order guide multiple times with the same variables will return the same calculated values.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the order guide to submit. This is a 32-character hexadecimal string that uniquely identifies the order guide item. Example: '25110912372211003e7d40ed9dbe5dd6'. The order guide must be active and available in the Service Catalog. |
| `variables` | object | No | Variable values for the order guide submission. Keys are the variable names/IDs and values are the corresponding values to set. The required variables depend on the specific order guide configuration. Common variable types include text inputs, checkboxes, dropdowns, and reference fields. Example: {'requested_for': 'user@example.com', 'justification': 'New equipment needed'} |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update sn chg rest change

**Slug:** `SERVICENOW_UPDATE_SN_CHG_REST_CHANGE`

Updates an existing change request in ServiceNow using the Change Management REST API. Use this action when you need to modify an existing change request, such as updating its state, changing assignments, adding notes, modifying dates, or updating the implementation plan. This action sends a PATCH request to the Change Management API, allowing partial updates of the record fields. Note: Only include the fields you want to update in the request. Fields not included will retain their current values. This is a destructive operation in that it modifies data, but the changes can be reverted by calling this action again with corrected values.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `risk` | string | No | Risk assessment of the change request (e.g., 1=High, 2=Medium, 3=Low) |
| `phase` | string | No | Current phase of the change request lifecycle (e.g., planning, assessment, authorization, implementation, closure) |
| `state` | string | No | Current state of the change request. Common values: -7=Cancelled, -6=Rejected, -5=Skipped, -4=Closed Incomplete, -3=Closed Complete, -2=Closed Skipped, -1=Closed Cancelled, 0=Pending, 1=In Progress, 2=Open, 3=Approved, 4=Review, 5=Scheduled, 6=Implemented, 7=Evaluated |
| `impact` | string | No | Impact level of the change request (e.g., 1=High, 2=Medium, 3=Low) |
| `sys_id` | string | Yes | The unique system ID (sys_id) of the change request to update. This is a 32-character hexadecimal string that uniquely identifies the change request. Example: '46e9b4afa9fe198101026e122b85f442' |
| `category` | string | No | Category or classification of the change request |
| `priority` | string | No | Priority of the change request (e.g., 1=Critical, 2=High, 3=Medium, 4=Low) |
| `test_plan` | string | No | Test plan for the change |
| `work_notes` | string | No | Internal work notes (not visible to end users) |
| `assigned_to` | string | No | Sys_id of the user assigned to implement the change |
| `close_notes` | string | No | Notes added when closing the change request |
| `description` | string | No | Full description of the change request |
| `subcategory` | string | No | Subcategory of the change request |
| `requested_by` | string | No | Sys_id of the user who requested the change |
| `justification` | string | No | Business justification for the change |
| `on_hold_reason` | string | No | Reason the change is on hold |
| `assignment_group` | string | No | Sys_id of the group assigned to the change |
| `planned_end_date` | string | No | Planned end date and time of the change (format: YYYY-MM-DD HH:MM:SS) |
| `short_description` | string | No | Brief summary or title of the change request |
| `planned_start_date` | string | No | Planned start date and time of the change (format: YYYY-MM-DD HH:MM:SS) |
| `implementation_plan` | string | No | Implementation plan details |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update sn chg rest change emergency

**Slug:** `SERVICENOW_UPDATE_SN_CHG_REST_CHANGE_EMERGENCY`

Updates an existing emergency change request in ServiceNow using the Change Management API. Use this action when you need to modify an existing emergency change request, such as updating its description, changing assignment, modifying priority, updating the implementation plan, or changing any other modifiable field. This is an update (PATCH) operation that performs a partial update of the record. Only fields that are included in the request body will be modified; all other fields retain their current values. Note: This action only works with emergency change requests. For normal or standard changes, use the appropriate change-specific endpoints.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `risk` | string | No | Risk level of the emergency change request. Valid values: 'low', 'medium', 'high', 'critical' |
| `phase` | string | No | Current phase of the emergency change request workflow. |
| `state` | string | No | Current state of the emergency change request. Valid values: -5=Cancelled, -4=On hold, -3=Rejected, -2=Pending, -1=Draft, 1=Initiating, 2=Pending, 3=Open, 4=In Progress, 5=Under Review, 6=Scheduled, 7=Implemented, 8=Verified, 9=Closed |
| `impact` | string | No | Impact level of the emergency change request. Valid values: 1=High, 2=Medium, 3=Low |
| `reason` | string | No | Reason for the emergency change request or its current state. |
| `sys_id` | string | Yes | The unique system ID (sys_id) of the emergency change request to update. This is a 32-character hexadecimal string that uniquely identifies the emergency change request. Example: 'd53e72ec73d423002728660c4cf6a78d' |
| `cab_date` | string | No | Scheduled CAB (Change Advisory Board) date in YYYY-MM-DD format. |
| `category` | string | No | Category classification of the emergency change request. |
| `comments` | string | No | Comments visible to end users. |
| `priority` | string | No | Priority level of the emergency change request. Valid values: 1=Critical, 2=High, 3=Moderate, 4=Low, 5=Planning |
| `test_plan` | string | No | Test plan for validating the emergency change implementation. |
| `work_notes` | string | No | Internal work notes not visible to end users. |
| `assigned_to` | string | No | sys_id of the user assigned to handle the emergency change request. Reference to sys_user table. |
| `close_notes` | string | No | Notes added when closing the emergency change request. |
| `description` | string | No | Detailed description of the emergency change request. Use this to provide comprehensive details about the change, its purpose, and expected outcomes. |
| `subcategory` | string | No | Subcategory classification of the emergency change request. |
| `expected_end` | string | No | Expected end date and time of the emergency change. Format: YYYY-MM-DD HH:MM:SS |
| `justification` | string | No | Business justification for the emergency change request. |
| `rollback_plan` | string | No | Plan for rolling back the change if issues arise. |
| `expected_start` | string | No | Expected start date and time of the emergency change. Format: YYYY-MM-DD HH:MM:SS |
| `on_hold_reason` | string | No | Reason for placing the emergency change request on hold. |
| `assignment_group` | string | No | sys_id of the group assigned to handle the emergency change request. Reference to sys_user_group table. |
| `short_description` | string | No | Brief summary or title of the emergency change request. This field provides a quick overview of what the emergency change is about. |
| `cab_recommendation` | string | No | CAB recommendation for the emergency change. |
| `implementation_plan` | string | No | Detailed implementation steps for the emergency change. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Normal Change Request

**Slug:** `SERVICENOW_UPDATE_SN_CHG_REST_CHANGE_NORMAL`

Updates a normal change request identified by its sys_id using the ServiceNow Change Management REST API. Use this action when you need to modify the details of an existing normal change request, such as updating its description, changing its state or priority, reassigning it to a different user or group, or updating schedule dates. Only the fields provided in the request will be updated; all other fields retain their current values. This is a PATCH operation — it performs a partial update. Only include the fields you want to change.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `risk` | string | No | Risk level of the change request. Typical values: 'low', 'medium', 'high', 'critical'. Use lowercase string values as defined in your ServiceNow instance. |
| `phase` | string | No | Current phase of the change request workflow. Typical values: 'Draft', 'Assessment', 'Authorization', 'Scheduled', 'Implementation', 'Post-Implementation', 'Closed'. Use the exact phase names as defined in your ServiceNow instance. |
| `state` | string | No | Current state of the change request. Common values: '-5'=Cancelled, '-4'=On hold, '-3'=Rejected, '-2'=Pending, '-1'=Draft, '1'=Initiating, '2'=Pending, '3'=Open, '4'=In Progress, '5'=Under Review, '6'=Scheduled, '7'=Implemented, '8'=Verified, '9'=Closed. Use the numeric string value corresponding to the desired state. |
| `active` | string | No | Boolean indicating whether the change request is active. Set to 'true' to activate or 'false' to deactivate. |
| `impact` | string | No | Impact level of the change request. Typical values: '1'=High, '2'=Medium, '3'=Low. Use the numeric string value corresponding to the impact level. |
| `reason` | string | No | Reason for the change. Example: 'End of life for legacy system component' |
| `sys_id` | string | Yes | The unique system ID (sys_id) of the normal change request to update. This is a 32-character hexadecimal string that uniquely identifies the change request. Example: 'a9e9c33dc61122760072455df62663d2' |
| `vendor` | string | No | Vendor associated with the change request. Example: 'Acme Corp' |
| `cmdb_ci` | string | No | The sys_id of the Configuration Item (CI) associated with the change. Reference to cmdb_ci table. Example: 'f9e9c33dc61122760072455df62663d2' |
| `company` | string | No | Company associated with the change request. Reference to core_company table via sys_id. Example: '1234567890abcdef1234567890abcdef' |
| `cab_date` | string | No | CAB (Change Advisory Board) meeting date. Format: ISO 8601 datetime string. Example: '2024-11-25 10:00:00' |
| `category` | string | No | Category or classification of the change request. Examples: 'Network', 'Hardware', 'Software', 'Application'. Values must match valid categories defined in your ServiceNow instance. |
| `comments` | string | No | Comments visible to end users regarding the change. Example: 'Scheduled maintenance window: 2024-12-01 02:00-04:00 UTC' |
| `contract` | string | No | Contract associated with the change request. Example: 'Vendor Support Agreement #12345' |
| `location` | string | No | Location associated with the change request. Reference to cmn_location table via sys_id. Example: 'abcdef1234567890abcdef1234567890' |
| `priority` | string | No | Priority level of the change request. Typical values: '1'=Critical, '2'=High, '3'=Standard, '4'=Low, '5'=Planning. Use the numeric string value corresponding to the priority. |
| `opened_by` | string | No | The sys_id of the user who opened the change request. Reference to sys_user table. Example: '681ccaf9c0a8016400b98a4e52c54f82' |
| `test_plan` | string | No | Test plan for validating the change. Example: 'Verify service connectivity, check logs for errors' |
| `department` | string | No | Department associated with the change request. Reference to cmn_department table via sys_id. Example: 'fedcba0987654321fedcba098765432' |
| `work_notes` | string | No | Internal work notes for the change (not visible to end users). Example: 'Contacted vendor support for additional guidance' |
| `approved_by` | string | No | Names or sys_ids of users who approved the change (comma-separated for multiple). Example: 'John Doe, Jane Smith' |
| `assigned_to` | string | No | The sys_id of the user assigned to implement the change. Reference to sys_user table. Example: '681ccaf9c0a8016400b98a4e52c54f82' |
| `close_notes` | string | No | Notes added when closing the change request. Example: 'Change completed successfully with no issues' |
| `description` | string | No | Detailed description of the change request. Example: 'Requires updating firewall rules to allow traffic on port 443' |
| `phase_state` | string | No | State within the current phase. Examples: 'Complete', 'In Progress', 'Pending', 'Skipped'. Use the exact state names as defined in your ServiceNow instance. |
| `review_date` | string | No | Scheduled review date for the change. Format: ISO 8601 datetime string. Example: '2024-11-30 09:00:00' |
| `subcategory` | string | No | Subcategory of the change request. Must correspond to a valid subcategory for the selected category. Example: 'Firewall' under 'Network' |
| `requested_by` | string | No | The sys_id of the user who requested the change. Reference to sys_user table. Example: '681ccaf9c0a8016400b98a4e52c54f82' |
| `justification` | string | No | Business justification for the change. Example: 'Required for compliance with new security policy' |
| `on_hold_reason` | string | No | Reason for placing the change request on hold. Example: 'Waiting for approval from security team' |
| `actual_end_date` | string | No | Actual end date and time when the change was completed. Format: ISO 8601 datetime string. Example: '2024-12-01 03:45:00' |
| `assignment_group` | string | No | The sys_id of the group assigned to the change. Reference to sys_user_group table. Example: '287e8906c61122730024e53cf3104b26' |
| `planned_end_date` | string | No | Planned end date and time of the change. Format: ISO 8601 datetime string. Example: '2024-12-01 04:00:00' |
| `service_offering` | string | No | The sys_id of the service offering related to the change. Reference to service_offering table. Example: 'b1e9c33dc61122760072455df62663d2' |
| `actual_start_date` | string | No | Actual start date and time when the change began. Format: ISO 8601 datetime string. Example: '2024-12-01 02:05:00' |
| `business_duration` | string | No | Business duration in seconds (calculated based on business hours). Example: '7200' for 2 hours |
| `calendar_duration` | string | No | Calendar duration in seconds (total elapsed time). Example: '14400' for 4 hours |
| `short_description` | string | No | Brief summary or title of the change request. Example: 'Update network configuration for DC-2' |
| `cab_recommendation` | string | No | CAB recommendation for the change. Example: 'Approved with conditions' |
| `planned_start_date` | string | No | Planned start date and time of the change. Format: ISO 8601 datetime string. Example: '2024-12-01 02:00:00' |
| `implementation_plan` | string | No | Implementation plan details describing how the change will be executed. Example: 'Step 1: Backup current config. Step 2: Apply new config. Step 3: Verify.' |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update ServiceNow Standard Change Request

**Slug:** `SERVICENOW_UPDATE_SN_CHG_REST_CHANGE_STANDARD`

Updates a standard change request in ServiceNow using its sys_id. Use this action when you need to modify an existing standard change request, such as updating its description, changing the assigned user or group, modifying dates, updating state or phase, or adding implementation and test plans. This is a PATCH operation that updates only the provided fields while preserving all other existing values on the record. This action uses the PATCH method, which means only fields included in the request will be modified. Fields not provided will retain their current values.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `risk` | string | No | Risk level of the standard change request. Valid values: 'low', 'medium', 'high', 'critical'. Example: 'low' |
| `phase` | string | No | Current phase of the standard change request workflow. Example: 'Requested', 'Approved', 'Scheduled', 'Implementation', 'Review', 'Closed' |
| `state` | string | No | Current state of the standard change request. Common values: -5=Cancelled, -4=On hold, -3=Rejected, -2=Pending, -1=Draft, 1=Initiating, 2=Pending, 3=Open, 4=In Progress, 5=Under Review, 6=Scheduled, 7=Implemented, 8=Verified, 9=Closed. Note: State transitions may require appropriate permissions and workflow conditions. |
| `active` | string | No | Boolean indicating if the standard change request is active. Use 'true' to activate or 'false' to deactivate. Example: 'true' |
| `impact` | string | No | Impact level of the standard change request. Typical values: 1=Critical, 2=High, 3=Medium, 4=Low. Example: '2' |
| `reason` | string | No | Reason for the standard change request. Example: 'Performance optimization required' |
| `sys_id` | string | Yes | The unique system ID (sys_id) of the standard change request to update. This is a 32-character hexadecimal string that uniquely identifies the standard change request. Example: '543a39de47410200e90d87e8dee4908a' |
| `vendor` | string | No | Vendor associated with the standard change request. Example: 'ACME Corporation' |
| `cmdb_ci` | string | No | The sys_id of the Configuration Item (CI) associated with the standard change request. Reference to cmdb_ci table. Example: 'ci1234567890abcdef1234567890ab' |
| `company` | string | No | The sys_id of the company associated with the standard change request. Reference to core_company table. Example: 'com1234567890abcdef1234567890ab' |
| `category` | string | No | Category classification of the standard change request. Must be a valid category defined in the change management configuration. Example: 'Software' or 'Hardware' |
| `comments` | string | No | Comments visible to end users about the standard change request. Example: 'Maintenance window: 2AM-4AM UTC' |
| `location` | string | No | The sys_id of the location associated with the standard change request. Reference to cmn_location table. Example: 'loc1234567890abcdef1234567890ab' |
| `priority` | string | No | Priority level of the standard change request. Typical values: 1=Critical, 2=High, 3=Standard, 4=Low, 5=Planning. Example: '2' |
| `work_end` | string | No | Work end date and time for the standard change. Format: YYYY-MM-DD HH:MM:SS or ISO 8601 format. Example: '2024-12-15 04:00:00' |
| `po_number` | string | No | Purchase order number associated with the standard change request. Example: 'PO-2024-12345' |
| `test_plan` | string | No | Test plan for the standard change request describing how the change will be tested before and after implementation. Example: 'Verify application starts successfully and database connections work' |
| `actual_end` | string | No | Actual end date and time of the standard change. Format: YYYY-MM-DD HH:MM:SS or ISO 8601 format. Example: '2024-12-15 03:45:00' |
| `department` | string | No | The sys_id of the department associated with the standard change request. Reference to cmn_department table. Example: 'dept1234567890abcdef1234567890ab' |
| `work_notes` | string | No | Internal work notes for the standard change request (not visible to end users). Use this for technical details and progress updates. Example: 'Applied config changes to all servers' |
| `work_start` | string | No | Work start date and time for the standard change. Format: YYYY-MM-DD HH:MM:SS or ISO 8601 format. Example: '2024-12-15 02:00:00' |
| `assigned_to` | string | No | The sys_id of the user to assign the standard change request to. Reference to sys_user table. Example: 'usr1234567890abcdef1234567890ab' |
| `change_plan` | string | No | Change plan details for the standard change request. Example: 'Update configuration files and restart services' |
| `close_notes` | string | No | Notes to add when closing the standard change request. Include any final comments, lessons learned, or completion status. Example: 'Change completed successfully. No issues encountered.' |
| `description` | string | No | Detailed description of the standard change request explaining what needs to be changed and why. Example: 'Update connection pooling settings in production database to improve performance' |
| `phase_state` | string | No | State within the current phase of the workflow |
| `subcategory` | string | No | Subcategory classification of the standard change request. Must be a valid subcategory within the selected category. Example: 'Operating System' or 'Database' |
| `actual_start` | string | No | Actual start date and time of the standard change. Format: YYYY-MM-DD HH:MM:SS or ISO 8601 format. Example: '2024-12-15 02:05:00' |
| `backout_plan` | string | No | Backout plan describing the procedure to back out of the standard change. Example: 'Execute revert script and notify team' |
| `expected_end` | string | No | Expected end date and time of the standard change. Format: YYYY-MM-DD HH:MM:SS or ISO 8601 format. Example: '2024-12-15 04:00:00' |
| `requested_by` | string | No | The sys_id of the user who requested the standard change. Reference to sys_user table. Example: 'usr987654321fedcba9876543210zyxw' |
| `justification` | string | No | Business justification for the standard change request. Example: 'Improve system performance and reduce downtime' |
| `rollback_plan` | string | No | Rollback plan describing how to revert the standard change if issues occur. Example: 'Restore from backup and restart previous version' |
| `expected_start` | string | No | Expected start date and time of the standard change. Format: YYYY-MM-DD HH:MM:SS or ISO 8601 format. Example: '2024-12-15 02:00:00' |
| `on_hold_reason` | string | No | Reason for placing the standard change request on hold. Example: 'Waiting for vendor approval' |
| `review_outcome` | string | No | Outcome of the standard change review. Example: 'Success', 'Failed', 'Partial' |
| `review_comments` | string | No | Comments from the standard change review. Example: 'All tests passed successfully' |
| `assignment_group` | string | No | The sys_id of the group to assign the standard change request to. Reference to sys_user_group table. Example: 'grp1234567890abcdef1234567890ab' |
| `service_offering` | string | No | The sys_id of the service offering associated with the standard change request. Reference to service_offering table. Example: 'svc1234567890abcdef1234567890ab' |
| `short_description` | string | No | Brief summary or title of the standard change request. Example: 'Update database configuration for production servers' |
| `cab_recommendation` | string | No | CAB recommendation for the standard change. Example: 'Approved', 'Rejected', 'Approved with conditions' |
| `implementation_plan` | string | No | Implementation plan describing the steps to implement the standard change. Example: '1. Backup current config, 2. Apply new settings, 3. Restart service' |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update sn chg rest change task

**Slug:** `SERVICENOW_UPDATE_SN_CHG_REST_CHANGE_TASK`

Updates an existing change request task in ServiceNow using the Change Management REST API. Use this action when you need to modify an existing task associated with a change request, such as updating its status, changing assignment, adding work notes, or marking it complete. This action sends a PATCH request to the Change Management API, allowing partial updates of the task fields. Only include the fields you want to update in the request - fields not included will retain their current values. Note: The task must already exist within the specified change request. If the change request or task doesn't exist, a 404 error will be returned.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `state` | string | No | Current state of the task. Common values: -5=Cancelled, -4=On hold, -3=Rejected, -2=Pending, -1=Draft, 1=Open, 2=Work In Progress, 3=Pending, 4=Complete |
| `comments` | string | No | Public comments on the task (visible to end users) |
| `priority` | string | No | Priority level of the task (e.g., '1' for critical, '2' for high, '3' for moderate, '4' for low, '5' for planning) |
| `actual_end` | string | No | Actual end date and time when the task was completed (ISO 8601 format) |
| `work_notes` | string | No | Internal work notes for the task (visible to IT staff only) |
| `assigned_to` | string | No | sys_id of the user assigned to the task |
| `close_notes` | string | No | Notes added when closing the task |
| `description` | string | No | Full description of the task |
| `task_sys_id` | string | Yes | The unique system ID (sys_id) of the task to update within the change request. This is a 32-character hexadecimal string that uniquely identifies the task. Example: 'cd820c7a833bf210dd2dc2dfeeaad333'. The task must exist within the specified change request, or a 404 error will be returned. |
| `actual_start` | string | No | Actual start date and time when the task began (ISO 8601 format) |
| `expected_end` | string | No | Expected end date and time of the task (ISO 8601 format) |
| `change_sys_id` | string | Yes | The unique system ID (sys_id) of the change request containing the task to update. This is a 32-character hexadecimal string that uniquely identifies the change request. Example: '46e9b4afa9fe198101026e122b85f442'. The change request must exist, or a 404 error will be returned. |
| `expected_start` | string | No | Expected start date and time of the task (ISO 8601 format) |
| `on_hold_reason` | string | No | Reason the task is on hold |
| `assignment_group` | string | No | sys_id of the group assigned to the task |
| `short_description` | string | No | Brief summary or title of the task |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update SD-WAN Trouble Ticket

**Slug:** `SERVICENOW_UPDATE_SN_IND_TSM_SDWAN_TICKET_TROUBLETICKET`

Updates an existing trouble ticket in ServiceNow using the Service Operations Workspace Trouble Ticket Open API. Use this action when you need to modify an existing trouble ticket, such as updating its state, changing assignments, adding notes, or modifying the resolution details. This action sends a PATCH request to the sn_ind_tsm_sdwan trouble ticket API, allowing partial updates of the record fields. Only include the fields you want to update in the request. Fields not included will retain their current values. This modifies the record data, but changes can be reverted by calling this action again with corrected values. This action is specifically for the Service Operations Workspace / Service Management SD-WAN integration's trouble ticket management functionality.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | The unique identifier (sys_id or record ID) of the trouble ticket to update. This is a 32-character hexadecimal string that uniquely identifies the trouble ticket record. Example: '1c741bd70b2322007518478d83673af3' |
| `state` | string | No | Current state of the trouble ticket. Common values vary by workflow but typically include: 'Open', 'In Progress', 'On Hold', 'Resolved', 'Closed', 'Cancelled'. The exact state values depend on your ServiceNow configuration. |
| `category` | string | No | Category or classification of the trouble ticket. Example categories: 'Network', 'Hardware', 'Software', 'Security'. The exact categories depend on your ServiceNow configuration. |
| `priority` | string | No | Priority level of the trouble ticket. Typical values: 1 = Critical (service down), 2 = High (major impact), 3 = Medium (moderate impact), 4 = Low (minor impact). The exact priority values depend on your ServiceNow configuration. |
| `close_code` | string | No | The resolution code for closing the trouble ticket. Common values: 'Resolved', 'Closed/Resolved', 'Closed/Cancelled', 'Not Resolved', 'Escalated'. The exact values depend on your configuration. |
| `work_notes` | string | No | Internal work notes about the trouble ticket. These notes are only visible to users with appropriate roles and are not visible to end users or customers. Use this for technical details and updates. Example: 'Investigated the issue and identified root cause as faulty switch' |
| `assigned_to` | string | No | Sys_id of the user assigned to handle the trouble ticket. This is the 32-character hexadecimal string that identifies the user. Example: 'usr789xyz012abc345def678ghi901' |
| `description` | string | No | Full detailed description of the trouble ticket, including symptoms, impact, and any relevant background information. Example: 'Users unable to access the corporate network since 9 AM' |
| `subcategory` | string | No | Subcategory of the trouble ticket for more specific classification. Example subcategories: 'Firewall', 'Router', 'Switch', 'VPN'. The exact subcategories depend on your ServiceNow configuration. |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response. Invalid fields are ignored. If not specified, all fields are returned. Example: 'number,short_description,state,assigned_to' |
| `assignment_group` | string | No | Sys_id of the group assigned to handle the trouble ticket. This is the 32-character hexadecimal string that identifies the group. Example: 'grp456def789ghi012jkl345mno678' |
| `resolution_notes` | string | No | Notes documenting how the trouble ticket was resolved. These are typically added when closing the ticket and describe the solution. Example: 'Replaced faulty switch and connectivity restored' |
| `short_description` | string | No | Brief summary or title of the trouble ticket. This describes the issue or request in a concise manner. Example: 'Network connectivity issue in DC1' |
| `sysparm_display_value` | string ("true" | "false" | "all") | No | Determines the type of data returned in the response. 'false': Returns actual database values (sys_ids for references, numeric values for choices). 'true': Returns display values (names for references, text labels for choices). 'all': Returns both display and actual values. |
| `sysparm_exclude_reference_link` | boolean | No | Set to true to exclude Table API links for reference fields in the response. Use this to reduce response size when reference links are not needed. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Trouble Ticket

**Slug:** `SERVICENOW_UPDATE_SN_IND_TSM_SDWAN_TROUBLETICKET`

Updates an existing trouble ticket in ServiceNow using the Trouble Ticket Open API. Use this action when you need to modify an existing trouble ticket, such as updating its state, changing assignments, adding notes, modifying dates, or updating the resolution details. This action sends a PATCH request to the Trouble Ticket Open API, allowing partial updates of the record fields. Supported ticket types include Case, Incident, Problem, and ChangeRequest. Only include the fields you want to update in the request. Fields not included will retain their current values. This is a destructive operation in that it modifies data, but the changes can be reverted by calling this action again with corrected values.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | The unique identifier of the trouble ticket to update. This can be the sys_id or the display number of the ticket. Example: '1' or 'CAS0010001' |
| `state` | string | No | Current state of the trouble ticket. Common values vary by ticket type but typically include: 1=New/Open, 2=In Progress, 3=On Hold, 4=Resolved, 5=Closed, 6=Cancelled. Use the numeric string value corresponding to the desired state. |
| `impact` | string | No | Impact level of the trouble ticket. Typical values: 1=High, 2=Medium, 3=Low. Use the numeric string value corresponding to the impact level. |
| `cmdb_ci` | string | No | Sys_id of the Configuration Item associated with the trouble ticket |
| `urgency` | string | No | Urgency level of the trouble ticket. Typical values: 1=High, 2=Medium, 3=Low. Use the numeric string value corresponding to the urgency level. |
| `category` | string | No | Category or classification of the trouble ticket |
| `comments` | string | No | Comments visible to end users regarding the trouble ticket |
| `priority` | string | No | Priority of the trouble ticket. Typical values: 1=Critical, 2=High, 3=Moderate, 4=Low. Use the numeric string value corresponding to the priority level. |
| `caller_id` | string | No | Sys_id of the user who reported the issue |
| `close_code` | string | No | Code indicating how the trouble ticket was resolved |
| `escalation` | string | No | Escalation status of the trouble ticket |
| `work_notes` | string | No | Internal work notes for the trouble ticket (not visible to end users) |
| `assigned_to` | string | No | Sys_id of the user assigned to handle the trouble ticket |
| `close_notes` | string | No | Notes added when closing the trouble ticket |
| `description` | string | No | Full description of the trouble ticket |
| `hold_reason` | string | No | Reason for placing the trouble ticket on hold |
| `resolved_at` | string | No | Timestamp when the trouble ticket was resolved (format: YYYY-MM-DD HH:MM:SS) |
| `resolved_by` | string | No | Sys_id of the user who resolved the trouble ticket |
| `subcategory` | string | No | Subcategory of the trouble ticket |
| `ticket_type` | string ("Case" | "Incident" | "Problem" | "ChangeRequest") | Yes | The type of trouble ticket to update. Valid values: 'Case', 'Incident', 'Problem', 'ChangeRequest'. Example: 'Case' |
| `assignment_group` | string | No | Sys_id of the group assigned to the trouble ticket |
| `short_description` | string | No | Brief summary or title of the trouble ticket |
| `business_resolution` | string | No | Business resolution description |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update table by

**Slug:** `SERVICENOW_UPDATE_TABLE_BY_ID`

Updates an existing record in a specified ServiceNow table by its sys_id using the Table API. Use this action when you need to modify specific fields of an existing record, such as updating the short_description, changing the state, reassigning the record, adding close_notes, or modifying any other table field. Only the fields specified in record_data are updated — all other fields retain their current values. This action sends a PATCH request to the ServiceNow Table API. This action modifies data but the changes can be reverted by calling this action again with the corrected values. This is an idempotent operation — calling it multiple times with the same parameters produces the same result.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the record to update. This is a 32-character hexadecimal string. Example: '3877ccb6833ff210dd2dc2dfeeaad375' |
| `table_name` | string | Yes | The name of the table containing the record to update. Examples: 'incident', 'problem', 'change_request', 'task', 'sys_user'. |
| `record_data` | object | No | Field-value pairs to update on the record. Only the specified fields are updated; all other fields retain their current values. For 'incident' table, common fields include: 'short_description', 'description', 'urgency' (1-3), 'impact' (1-3), 'priority', 'assignment_group', 'assigned_to', 'category', 'state', 'close_notes', 'work_notes'. For reference fields (like 'assigned_to'), use the sys_id of the referenced record, or set sysparm_input_display_value=true to use display values. Example: {'short_description': 'Updated via API', 'urgency': '2', 'impact': '2'} |
| `sysparm_view` | string ("desktop" | "mobile" | "both") | No | UI view that determines which fields are returned. |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response. Invalid fields are ignored. If not specified, all fields are returned. Example: 'number,short_description,state,assigned_to' |
| `sysparm_display_value` | string ("true" | "false" | "all") | No | Determines the type of data returned in the response. 'false': Returns actual database values (sys_ids for references, numeric values for choices). 'true': Returns display values (names for references, text labels for choices). 'all': Returns both display and actual values. |
| `sysparm_input_display_value` | boolean | No | Set to true if providing display values (e.g., user names) instead of sys_ids in record_data for reference fields. When false (default), reference fields must contain sys_ids. |
| `sysparm_exclude_reference_link` | boolean | No | Set to true to exclude Table API links for reference fields in the response. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update table by id2

**Slug:** `SERVICENOW_UPDATE_TABLE_BY_ID2`

Updates an existing record in a specified ServiceNow table using its sys_id with the provided field values. This action uses the PUT method which replaces the entire record with the provided data. Only fields included in the record_data will be updated; unspecified fields retain their current values. Use this action when you need to modify specific fields of an existing record, such as updating the short_description, state, assignment, or other attributes of an incident, change request, or other table records. Note: This is a destructive operation in that it modifies data, but changes can be reverted by calling this action again with corrected values. For partial updates, consider using PATCH semantics where only the fields you want to change are included in record_data.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system ID (sys_id) of the record to update. This is a 32-character hexadecimal string that uniquely identifies the record. Example: '1c741bd70b2322007518478d83673af3' |
| `table_name` | string | Yes | Name of the ServiceNow table to update the record in (e.g., 'incident', 'problem', 'change_request', 'task', 'sys_user'). The table must exist in the ServiceNow instance and the user must have write permissions. |
| `record_data` | object | No | Field-value pairs to update in the record. This replaces the entire record with the provided data. For 'incident' table, common fields include: 'short_description', 'description', 'urgency' (1-3), 'impact' (1-3), 'priority', 'assignment_group', 'assigned_to', 'category', 'state'. For reference fields (like 'assignment_group' or 'assigned_to'), use the sys_id of the referenced record, or set sysparm_input_display_value=true to use display values. Example: {'short_description': 'Updated via API', 'state': '2'} |
| `sysparm_view` | string ("desktop" | "mobile" | "both") | No | UI view options for ServiceNow table API |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response (e.g., 'number,short_description,state'). Invalid fields are ignored. If not specified, all fields are returned. |
| `sysparm_display_value` | string ("true" | "false" | "all") | No | Display value options for ServiceNow table API responses |
| `sysparm_input_display_value` | boolean | No | Set to true if providing display values (e.g., user names) instead of sys_ids in record_data for reference fields. When false (default), reference fields must contain sys_ids. |
| `sysparm_exclude_reference_link` | boolean | No | Set to true to exclude Table API links for reference fields in the response. When false (default), reference fields include a 'link' property pointing to the API endpoint. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update table incident

**Slug:** `SERVICENOW_UPDATE_TABLE_INCIDENT`

Updates an existing incident record in ServiceNow using the Table API. Use this action when you need to modify an existing incident, such as updating its state, changing assignments, adding work notes, updating priority/urgency, or modifying any other incident field. This action sends a PUT request to the Table API endpoint for the incident table. Note: Only include the fields you want to update in the request. Fields not included will retain their current values. This operation modifies data but changes can be reverted by calling this action again with corrected values.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `state` | string ("1" | "2" | "3" | "4" | "5" | "6" | "7" | "8" | "9") | No | Incident state values in ServiceNow |
| `impact` | string | No | Impact level of the incident (1=High, 2=Medium, 3=Low). Indicates the effect on the business or users. |
| `sys_id` | string | Yes | The unique system ID (sys_id) of the incident to update. This is a 32-character hexadecimal string that uniquely identifies the incident record. Example: '13e7c0fa833ff210dd2dc2dfeeaad3fc' |
| `urgency` | string | No | Urgency level of the incident (1=High, 2=Medium, 3=Low). Indicates how quickly a response is needed. |
| `category` | string | No | Category or classification of the incident (e.g., 'network', 'hardware', 'software', 'database'). |
| `priority` | string ("1" | "2" | "3" | "4" | "5") | No | Incident priority values in ServiceNow |
| `caller_id` | string | No | Sys_id of the user who reported the incident. |
| `work_notes` | string | No | Internal work notes visible only to support staff (not visible to end users). Use for documenting investigation progress, actions taken, and resolution steps. |
| `assigned_to` | string | No | Sys_id of the user assigned to handle the incident. Example: 'usr789xyz012abc345def678ghi901' |
| `close_notes` | string | No | Notes added when closing the incident, typically explaining the resolution. |
| `description` | string | No | Detailed description of the incident, including steps to reproduce, error messages, and any relevant context. Example: 'Users in Building A are unable to access the internal network since 9am' |
| `resolved_at` | string | No | Timestamp when the incident was resolved (format: YYYY-MM-DD HH:MM:SS). |
| `subcategory` | string | No | Subcategory of the incident (e.g., 'router', 'firewall', 'wifi'). |
| `contact_type` | string | No | Method of contact (e.g., 'phone', 'email', 'self-service', 'chat'). |
| `sysparm_view` | string ("desktop" | "mobile" | "both") | No | UI view to determine which fields are returned in the response. If not specified, returns fields from the default view. |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response (e.g., 'number,short_description,state'). Invalid fields are ignored. If not specified, all fields are returned. |
| `assignment_group` | string | No | Sys_id of the group assigned to the incident. Example: 'grp456def789ghi012jkl345mno678' |
| `short_description` | string | No | Brief summary or title of the incident (visible to end users). This should be a concise description of the issue. Example: 'Network connectivity issue in Building A' |
| `sysparm_display_value` | string ("true" | "false" | "all") | No | Determines the type of data returned in the response. 'false': Returns actual database values (sys_ids for references, numeric values for choices). 'true': Returns display values (names for references, text labels for choices). 'all': Returns both display and actual values. |
| `sysparm_input_display_value` | boolean | No | Set to true if providing display values (e.g., user names) instead of sys_ids in the request body for reference fields. When false (default), reference fields must contain sys_ids. |
| `sysparm_exclude_reference_link` | boolean | No | Set to true to exclude Table API links for reference fields in the response. Recommended to set to true to reduce response size. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update table record

**Slug:** `SERVICENOW_UPDATE_TABLE_RECORD`

Updates an existing record in a specified ServiceNow table using the Table API. Use this action when you need to modify an existing record in any ServiceNow table (e.g., incident, problem, change_request, task). Only the fields specified in record_data will be updated; all other fields retain their current values. This is a destructive operation in that it modifies data, but changes can be reverted by calling this action again with corrected values. Note: For the ServiceNow Table API, both PUT and PATCH methods function identically - only specified fields are updated.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `sys_id` | string | Yes | The unique system identifier (sys_id) of the record to update. This is a 32-character hexadecimal string. |
| `table_name` | string | Yes | The name of the table containing the record to update (e.g., 'incident', 'problem', 'change_request', 'task', 'sys_user'). |
| `record_data` | object | Yes | Field-value pairs to update in the record. Only specified fields will be updated; fields not included will retain their current values. Available fields depend on the table schema. For 'incident' table, common updateable fields include: 'short_description', 'description', 'urgency', 'impact', 'priority', 'assignment_group', 'assigned_to', 'category', 'state', 'work_notes', 'comments'. For reference fields (like 'assignment_group' or 'assigned_to'), use the sys_id of the referenced record, or set sysparm_input_display_value=true to use display values instead. Example: {'short_description': 'Updated via API', 'state': '2'} |
| `sysparm_view` | string ("desktop" | "mobile" | "both") | No | UI view to determine which fields are returned in the response. If not specified, returns fields from the default view. |
| `sysparm_fields` | string | No | Comma-separated list of fields to return in the response (e.g., 'number,short_description,state'). Invalid fields are ignored. If not specified, all fields are returned. |
| `sysparm_display_value` | string ("true" | "false" | "all") | No | Determines the type of data returned in the response. 'false': Returns actual database values (sys_ids for references, numeric values for choices). 'true': Returns display values (names for references, text labels for choices). 'all': Returns both display and actual values. |
| `sysparm_input_display_value` | boolean | No | Set to true if providing display values (e.g., user names) instead of sys_ids in record_data for reference fields. When false (default), reference fields must contain sys_ids. |
| `sysparm_exclude_reference_link` | boolean | No | Set to true to exclude Table API links for reference fields in the response. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Upload Attachment to ServiceNow Record

**Slug:** `SERVICENOW_UPLOAD_ATTACHMENT`

Uploads a file as an attachment to a specified record in ServiceNow. Use this action when you need to attach files to ServiceNow records (e.g., incidents, problems, change requests) using the raw binary upload endpoint (/api/now/v1/attachment/file). The file content is sent as raw binary data with the Content-Type header reflecting the file type. Common use cases: - Attach documents or screenshots to incident reports - Upload evidence files to problem records - Add files to change requests for documentation This action permanently modifies a live ServiceNow instance — the attachment cannot be recovered once deleted.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `content` | string | No | Inline file content as a string. Use this OR 'file_content' field, not both. The content will be encoded as UTF-8 bytes for upload. |
| `file_name` | string | Yes | Name to give the attachment file (e.g., 'report.pdf', 'screenshot.png'). |
| `table_name` | string | Yes | Name of the ServiceNow table to attach the file to (e.g., 'incident', 'problem', 'change_request'). |
| `content_type` | string | No | MIME type of the content. Defaults to 'text/plain' if not specified. Only used when 'content' field is provided. |
| `file_content` | object | No | File content to upload via S3. FileUploadable object where 'name' is the filename to use in ServiceNow. Use this OR 'content' field, not both. |
| `table_sys_id` | string | Yes | Sys_id of the record in the table to attach the file to. This is the unique identifier of the record. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |