ServiceNow

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Retrieves a specific email record from ServiceNow's Email

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.

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)

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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, field selection via sysparm_fields, and pagination via sysparm_limit and sysparm_offset. This action performs a GET request and is read-only.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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/.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.