Your AI team, working in ServiceNow
ServiceNow is a cloud-based enterprise platform that helps organizations automate and manage digital workflows across IT, HR, customer service, and operations.
Start your companyWhat your team can do in ServiceNow
172 tools to work with, connected with an API key.
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.
Attaches a file to a specified record in a ServiceNow table. This action sends the file as a raw binary request body with its MIME Content-Type 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. Deprecated: use SERVICENOW_UPLOAD_ATTACHMENT instead.
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. Note: this action is NOT idempotent. Calling it on a change request with no active conflict check running returns a 400 error ("Conflict for change request could not be cancelled"), not a success response. If the change request doesn't exist, a 404 error is returned instead.
Determines whether two named CI actions are compatible according to ServiceNow CI Lifecycle Management rules. The legacy ci1 and ci2 inputs represent action names, not CIs.
Determines whether the specified requestor's lease has expired for a named CI action applied to a configuration item (CI). The sys_id input identifies the CI, not a lease record.
Determines whether CIs of a specified class are prohibited from transitioning from one operational-state label to another. True means the transition is restricted.
Posts an empty request to the documented Service Catalog checkout endpoint for the authenticated user's current cart. With one-step checkout ServiceNow saves the cart and returns the request number and request ID. With two-step checkout it returns cart order status and the information needed to complete checkout instead. The legacy cart_id input is unsupported by the documented operation and is rejected if supplied.
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.
Sends a non-committing simulation request to the enhanced ServiceNow IRE query endpoint. Legacy data is normalized to the documented ``items`` payload, and the source is sent as ``sysparm_data_source``. The queryEnhanced endpoint only determines proposed operations and never commits CMDB changes.
Creates a new record in a specified ServiceNow table with the provided field values. The response contains the created record, subject to the requested field selection and view.
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.
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.
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.
Adds a named CI action to one or more configuration items (CIs). The ci input is a comma-separated list of CI sys_ids, and requestor_id identifies the workflow or registered operator.
Registers the authenticated non-workflow user as a CI Lifecycle Management operator. The endpoint accepts no request body or query parameters and returns a requestor ID.
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.
Inserts one record with the supplied fields into classname through the ServiceNow Table API, not the CMDB Instance API. When classname is a CMDB class table, this directly creates a CI record without CMDB Instance API relation handling.
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.
Creates a Linux server configuration item in the ServiceNow cmdb_ci_linux_server table with the supplied attributes. The response can be restricted to selected fields.
Assigns pre-defined or user-defined data classifications to existing dictionary entries. Use this action when you need to classify sensitive or confidential table columns according to your organization's data governance policies. This action classifies Dictionary [sys_dictionary] entries (table.column metadata) β not individual records β by assigning them one or more Data Classification [data_classification] labels such as 'Public', 'Internal', 'Confidential', or custom labels defined on the instance. Requires the admin or data_classification_admin role.
Removes all data classifications from one or more Dictionary [sys_dictionary] entries. This endpoint operates on table-column metadata, not arbitrary records. Prefer ``dictionary_entries``; the deprecated ``sys_id`` input is treated as one dictionary entry.
Submits incoming data to a specified ServiceNow import staging table for transformation into a target table. Although the request accepts a list of items, ServiceNow processes only the first record in a POST containing multiple records.
Creates a new incident in ServiceNow with supplied incident fields, including urgency, impact, state and caller. The response can be restricted to selected fields.
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 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.
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.
Creates one record through the ServiceNow Table API, not the TMF Trouble Ticket Open API. The ticket_type selects the target table, and the supplied optional fields are sent as table columns. The action returns the Table API result.
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.
Posts to an order guide's checkout_guide endpoint. The current implementation sends a variables object, while ServiceNow documents an items array containing each catalog item's sys_id, quantity, and variables; this action preserves the existing variables wire shape. This operation has side effects. When two-step checkout is disabled, ServiceNow adds the requested items to the cart and returns the cart contents. When two-step checkout is enabled, it checks out the items and returns a request number and request sys_id.
Creates a new ServiceNow incident using the Table API, with a required short description and optional incident and assignment fields. The response can be restricted to selected fields. Deprecated: use SERVICENOW_CREATE_INCIDENT instead.
Creates a ServiceNow interaction, then updates its short description and context table through the Table API because the Interaction create endpoint ignores those two fields. Returns the updated interaction record.
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 through the ServiceNow Change Management API with a short description and optional description, affected CI, and reason. Emergency changes bypass the Assess state but still require the Authorize state; this action creates the request and does not approve or implement it.
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. Note: At least two packages must be specified for a batch install operation.
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.
Inserts a new record into a specified ServiceNow table using the Table API and returns the selected record fields. Response field selection can restrict which identifiers are returned. Deprecated: use SERVICENOW_CREATE_A_RECORD instead.
Inserts one record in the ServiceNow sc_category table through the Table API, not a TMF Catalog Management endpoint. name is mapped to title, parent_id is mapped to parent, and the Table API response is projected into category fields.
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.
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.
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. Deprecated: use SERVICENOW_DELETE_ATTACHMENT_BY_ID instead.
Deletes any ServiceNow attachment by its sys_id through the general Attachment API; this action has no CSM-specific behavior. Deprecated: use SERVICENOW_DELETE_ATTACHMENT_BY_ID instead.
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.
Removes a named CI action from one or more configuration items through the supported CI Lifecycle Management API. sys_ids is a comma-separated list of CI sys_ids, and requestor_id identifies the workflow or registered operator.
Deprecated and disabled because it previously hard-deleted a statemgmt_ci_actions record through the Table API. Use SERVICENOW_DELETE_CI_LIFECYCLE_ACTION instead. The replacement uses the supported CI Lifecycle Management API to remove a named action from selected CIs.
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. Deprecated: use SERVICENOW_DELETE_INCIDENT_BY_ID instead.
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 and may delete a Service Catalog shopping cart using its sys_id. ServiceNow documents this endpoint as deleting the specified cart and its contents. The exact deletion capability depends on the caller's role: ``catalog_admin`` can delete cart items, while ``admin`` can also delete the emptied cart. This is destructive and irreversible.
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. Deprecated: use SERVICENOW_DELETE_A_RECORD instead.
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. Deprecated: use SERVICENOW_DELETE_INCIDENT_BY_ID instead.
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.
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.
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. Deprecated: use SERVICENOW_GET_ATTACHMENT_LIST instead.
Retrieves activity records from the ServiceNow ActivitySubscription API. Requests can specify a stream and paginate using limit and offset; the default limit is 25.
Retrieves activity subscription facets for a specified ServiceNow activity context and context instance. An HTTP 400 response is returned as a result with no facets.
Requests a prediction from a named ServiceNow Agent Intelligence solution, optionally supplying input field values. The response may include a predicted value and confidence score.
Retrieves data classification records from the ServiceNow data_classification table. Use limit and offset to paginate through the records.
Retrieves configuration items associated with an application service in ServiceNow CMDB, identified by its sys_id. Use it to explore service components for impact analysis or change management; the request supports field selection, display options, and limit/offset pagination.
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. Deprecated: use SERVICENOW_GET_ATTACHMENT_BY_ID instead.
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. Deprecated: use SERVICENOW_GET_ATTACHMENT_FILE instead.
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 change scheduling information for a specific ServiceNow configuration item and requested duration. The response may include worker and schedule information.
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 scheduling information for a ServiceNow change request. The response may include schedule slots or an asynchronous worker response while schedule calculation is in progress.
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.
Returns the active CI Lifecycle Management actions associated with a configuration item (CI), identified by the CI's sys_id. Returns no_active_action when none are active.
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 records from the ServiceNow sc_cat_item table through the Table API, not the Cloud Services Catalog API. It forwards encoded-query, field-selection, pagination, display-value, view, and query-category parameters.
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 [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.
Retrieves a ServiceNow user's directly granted and inherited roles for reviewing role assignments and troubleshooting access. Specify a user by sys_id or user sys_id. The legacy sys_id key is accepted as an alias for user_sysid.
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. Deprecated: use SERVICENOW_GET_TABLE_INCIDENT_BY_ID instead.
Retrieves a specific ServiceNow incident by sys_id using the Table API. The response contains a limited set of incident fields, including state, priority, caller and assigned user. Deprecated: use SERVICENOW_GET_TABLE_INCIDENT_BY_ID instead.
Retrieves incidents from the ServiceNow incident table with optional encoded filtering, pagination and field selection. Returned records are limited to the tool's supported incident 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 Performance Analytics scorecards and indicator details from the Analytics Hub, optionally filtering by indicator UUID and including scores. Supports page and per-page parameters.
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.
Lists records from a specified ServiceNow table; it does not retrieve a single record by sys_id. Supports filtering via sysparm_query, field selection, pagination, query categories, domain controls, 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. Deprecated: use SERVICENOW_GET_RECORDS instead.
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.
With table_name, lists records from that ServiceNow table. Without table_name, lists available table schemas from GET /api/now/doc/table/schema. 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. Deprecated: use SERVICENOW_GET_RECORDS to list records from a specified table.
Retrieves the current status of a ServiceNow shared library upload by upload ID. Use it to check whether an upload is still in progress, has completed, or has failed. This is a read-only operation.
Retrieves the full ServiceNow change request record for the supplied sys_id, including provider fields beyond the commonly used typed fields in the schema.
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 emergency change requests from ServiceNow with encoded-query filtering, field selection, pagination, and display value options. Returned records lacking either sys_id or number are omitted, so field selections should include both.
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 standard change requests from ServiceNow with query filtering, field selection, pagination, and display value options. Projected records are retained even when the selected fields exclude sys_id or number.
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.
Lists records from a specified ServiceNow table using the Table API; despite its name, this action does not accept a record sys_id or retrieve a single record. 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. Deprecated: use SERVICENOW_GET_RECORDS instead.
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.
Lists user records from the ServiceNow sys_user table for tasks such as finding active users or users in a department. Supports encoded-query filtering, field selection, limit/offset pagination, and actual, display, or both value formats. This is a read-only operation.
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. Deprecated: use SERVICENOW_CREATE_SERVICENOW_IMPORT_INSERTMULTIPLE instead.
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.
Returns predictions for multiple ServiceNow Predictive Intelligence solutions. Requires ``solution_names`` and exactly one input mode: ``input_maps``, or ``input_table`` together with ``input_filter``. Deprecated request filters remain accepted for compatibility but are not sent to ServiceNow.
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 ServiceNow attachments, with an encoded query to filter by attachment properties and a limit on the number returned. File content must be downloaded separately using the sys_id or download link. Deprecated: use SERVICENOW_GET_ATTACHMENT_LIST instead.
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.
Lists ServiceNow incident records using the Table API, with encoded-query filtering, field selection and a configurable result limit. Results can include state, priority, assignment, timestamps and SLA information. Deprecated: use SERVICENOW_GET_INCIDENTS instead.
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.
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.
Sends a non-committing simulation request to the ServiceNow IRE query endpoint. Legacy class and attribute inputs are normalized to the documented ``items`` payload, and the source is sent as ``sysparm_data_source``. No insert or update is committed by this endpoint.
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.
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.
Starts retrieval of an update set from a remote instance through the ServiceNow CICD Update Set API. It sends the source update-set sys_id plus a remote-instance record sys_id or instance ID as query parameters. The response reports execution status and progress; successful request acceptance does not mean retrieval has already finished.
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 an automated test suite using ServiceNow's CI/CD Pipeline API, identified by sys_id or name. The response may contain a progress identifier for monitoring; a failed operation can also be returned in the result.
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 an operational-state label for one or more configuration items (CIs). Requires CI sys_ids and a workflow-context or registered-operator requestor ID.
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.
Posts without a request body to the documented Service Catalog submit_order endpoint for the authenticated user's current cart. ServiceNow checks out the cart according to the instance's one-step or two-step checkout configuration. One-step checkout creates a request and returns its ID and number; two-step checkout can instead return checkout status and details. Legacy cart and body inputs are rejected if supplied.
Submits a Service Catalog producer item with optional variables to create a record in ServiceNow. The response can include the created record's sys_id, table name and number.
Populates an application service through the deprecated CSDM population endpoint. ``population_method`` selects ``cmdb_group_based``, ``discovery``, or ``tag_list`` and supplies that method's required inputs. ServiceNow recommends the replacement SG Services ``POST /sg_services/app_service/populate`` endpoint instead.
Updates basic details and relationships through the deprecated CSDM endpoint. ServiceNow accepts ``basic_details`` containing ``name`` and ``environment`` plus a ``relationships`` object. Legacy ``name`` and ``environment`` inputs are mapped into ``basic_details``; unsupported legacy fields are never sent. ServiceNow recommends the replacement SG Services ``POST /sg_services/app_service/update`` endpoint instead.
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 a specific ServiceNow CMDB configuration item by class and sys_id using the Table API. It sends the supplied attributes, including supported custom fields, in a PATCH request.
Sends a request to drop an agent from an Agent Chat conversation. Sends the Interaction record sys_id as ``interaction_id`` in the JSON body. The endpoint applies only to third-party interactions and requires the ``awa_integration_user`` role.
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 a ServiceNow incident by sys_id using the Table API. Supports selected fields including state, assignment, work notes, priority, urgency, close notes and resolved time. Deprecated: use SERVICENOW_UPDATE_INCIDENT_BY_ID instead.
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 OpenFrame interaction record identified by sys_id. The selected record fields are sent under interaction.additionalParams, and the response reports the provider's SUCCESS or FAILURE status.
Partially updates one Incident [incident] record through the ServiceNow Table API, not the TMF Trouble Ticket Open API. It sends only the supplied fields and passes display-value, reference-link, and field-selection options as query parameters.
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.
Evaluates an order guide without placing an order. It sends the supplied guide variables to ServiceNow's submit_guide endpoint and returns the catalog items that match the needs described by those values. An empty list means no items matched.
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 by sys_id using the ServiceNow Change Management API. It sends a partial update for supported fields such as description, assignment, priority, implementation plan, and schedule.
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. Deprecated: use SERVICENOW_UPDATE_TABLE_RECORD instead.
Updates an existing record in a specified ServiceNow table by sys_id using PUT and the provided field values. Response options can select fields and control display values. Deprecated: use SERVICENOW_UPDATE_TABLE_RECORD instead.
Updates an existing ServiceNow incident by sys_id using the Table API. Supports selected fields including state, assignment, priority, urgency, work notes and closure details. Deprecated: use SERVICENOW_UPDATE_INCIDENT_BY_ID instead.
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.
Partially updates one record by sys_id through the ServiceNow Table API, not the TMF Trouble Ticket Open API. ticket_type selects sn_ind_tsm_sdwan_case, incident, problem, or change_request, and only supplied fields are included in the PATCH.
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.
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.
Nothing matches that.
More in It operations
See them all βiLert is an incident response platform for managing alerts, on-call schedules, escalations, incidents, and status pages.
8 toolsβ LLinode provides cloud infrastructure APIs for compute, networking, storage, Kubernetes, databases, DNS, and account operations.
418 toolsβ RRemote Retrieval automates the logistics of managing equipment returns, providing efficient tracking and management of laptop and monitor returns.
7 toolsβ RRootly is an AI-native incident management platform that automates workflows and collaboration, integrating with Slack, PagerDuty, and other tools toβ¦
6 toolsβ TTailscale is a secure networking platform for managing tailnets, devices, users, DNS, access policies, services, and other network administrationβ¦
15 toolsβ