---
title: ServiceNow Actions
description: "## Actions for ServiceNow - ***Create ServiceNow Assets (IRE API)***. Creates one or more new configuration items (CIs) in ServiceNow. - ***Create/Update ServiceNow Assets (IRE API)***. Creates one or more new configuration items (CIs) in ServiceNow. If the one or…"
url: "https://lucidum.io/docs/servicenow-actions/"
updated: "2026-07-16"
category: Actions / List of Actions / S
---

# ServiceNow Actions

## Actions for ServiceNow

- ***Create ServiceNow Assets (IRE API)***. Creates one or more new configuration items (CIs) in ServiceNow.
- ***Create/Update ServiceNow Assets (IRE API)***. Creates one or more new configuration items (CIs) in ServiceNow. If the one or more of the CIs already exist, this action updates the existing CIs.

## Use Cases

Below are the possible use cases for the ServiceNow actions:

- ***Create ServiceNow Assets (IRE API)***. You could use this action to create a new CI in ServiceNow for previously unknown assets that were discovered by Lucidum.
- ***Create/Update ServiceNow Assets (IRE API)***. You could use this action to update asset records when a user is offboarded, to prevent unauthorized access.

## Prerequisites

Before you can execute the actions for ServiceNow, you must create a ServiceNow user account with the following roles:

- itil
- rest_api_explorer
- web_service_admin

For details on creating a user in ServiceNow, see [https://docs.servicenow.com/bundle/tokyo-platform-administration/page/administer/users-and-groups/task/t_CreateAUser.html](https://docs.servicenow.com/bundle/tokyo-platform-administration/page/administer/users-and-groups/task/t_CreateAUser.html)

For details on assigning roles to a user, see [https://docs.servicenow.com/bundle/tokyo-platform-administration/page/administer/users-and-groups/task/t_AssignARoleToAUser.html](https://docs.servicenow.com/bundle/tokyo-platform-administration/page/administer/users-and-groups/task/t_AssignARoleToAUser.html)

## Workflows

- [Creating a new Configuration and a new Action](https://lucidum.io/docs/overview-of-actions#workflow_for_creating_configurations_and_actions_in_lucidum)
- [Cloning an Existing Action](https://lucidum.io/docs/overview-of-actions#workflow_using_clone_to_create_a_new_action)
- [Creating a new Action from the Location Results page](https://lucidum.io/docs/overview-of-actions#alternative_workflow_for_creating_an_action)
- [Editing a Configuration](https://lucidum.io/docs/overview-of-actions#workflow_for_editing_a_configuration)
- [Editing an Action](https://lucidum.io/docs/overview-of-actions#workflow_for_editing_an_action)
- [Viewing Information about an Action](https://lucidum.io/docs/overview-of-actions#viewing_information_about_an_existing_action_and_executing_an_action_on_demand)

## ServiceNow Configuration

![servicenow_config_jul13-2026.png](https://lucidum.cloud/docs/servicenow_config_jul13-2026.png)

- ***Configuration Name***. Identifier for the Configuration. This name will appear in the Lucidum Action Center.
- ***Host.***The hostname or IP address of the ServiceNow server.
- ***User name*** The user name for a user account that has read and write permissions in ServiceNow.
- ***Password**.*The password associated with ***User Name***.
- ***Client ID***. For OAuth, the account name for the ServiceNow account used by Meridian.
- ***Client Secret***. For OAuth, the account password for the for the ServiceNow account used by Meridian.
- ***Refresh Token***. For OAuth, allows Meridian to refresh the access token without entering credentials in ServiceNow.

## Create or Edit an Action

To create an action for ServiceNow:

1. In the **Create a New Action** page, in the **General**step, enter:

   ![servicenow_general_page.png](https://lucidum.cloud/docs/servicenow_general_page.png)

   - ***Description***. After saving an Action, Lucidum uses the Luci LLM to populate this field automatically. You cannot edit the value in this field.
   - ***Business Value***. After saving an Action, Lucidum uses the Luci LLM to populate this field automatically. You cannot edit the value in this field.
   - ***Action Type***. Select from the list of possible action types. Choices are:
     - *Create/Update ServiceNow Assets (IRE API)*. Use data from Lucidum to create a new ServiceNow asset.
     - *Create ServiceNow Incident*. Use data from Lucidum to create a new ServiceNow incident.
   - ***Configuration Name***. Select an action configuration from the pulldown options.
   - ***Action Name***. Identifier for the action. This name will appear in the Lucidum Action Center.
   - ***Author Comments***. Custom comments about the Action.
2. Click the **Next**(>) icon.
3. In the **Filters** page, click **Configure Filters**.

   ![filters_page.png](https://lucidum.cloud/docs/filters_page.png)
4. The **Build a Query**page appears.

   ![build_query1_updated.png](https://lucidum.cloud/docs/build_query1_updated.png)
5. In the **Build a Query**page, you define the query for the assets or users that the action will act upon.
6. Click **Next**.
7. In the **Build a Current Query**page, enter the fields, operators, and values for the query. For existing actions, the query is already loaded in this page.

   ![build_query2_updated.png](https://lucidum.cloud/docs/build_query2_updated.png)
8. For details on creating and editing queries in Lucidum, see the section on [Building Queries](https://lucidum.io/docs/building-queries).
   **NOTE**: To optimize performance, the default time range is *Current*. If you need to access historical data, contact Lucidum Customer Success for help on using historical data without affecting performance.
9. Click the **Apply** (page and pencil) icon.
10. Click the **Next**(>) icon.
11. In the **Schedule** step, enter:

    ![servicenow_new_action3.png](https://lucidum.cloud/docs/servicenow_new_action3.png)

    - ***Schedule Type***. Define the schedule for the action. Choices are:

      - ***Recurrence***. Specify a frequency for the recurring schedule.
      - ***After Data Ingestion***. The action is executed after data ingestion, which happens at least once every 24 hours and can also be triggered manually.
    - ***Do not trigger the action unless***. Specify the number of results from ***Filters*** as a prerequisite for executing the action.
12. Click the **Next**(>) icon.
13. If you selected ***Create/Update ServiceNow Assets (IRE API)*** in the **General** page, in the **Details** step, enter the following:

    ![servicenow_new_action_details_jul13-2026.png](https://lucidum.cloud/docs/servicenow_new_action_details_jul13-2026.png)

    - ***Output Fields***. For the records selected with the ***Filters*** field, specify the columns to display. When creating or editing the query, you can select these fields in the **Query Results** page > **Edit Column**button.
    - ***ServiceNow CMDB Discovery Source.*** Select from the list of values. The selected discovery source can update all CMDB tables, not just the one specified in this action. You could select Meridian to make sure up CMDB records updated by Meridian show a Meridian source.
    - ***ServiceNow CMDB CI Target Table Name***. Specify the CMDB CI table name where the new or updated asset resides.
    - ***Field mapping***. Specify how you want field values from Lucidum to map to fields in ServiceNow. For example, in Lucidum, the asset name is stored in the field "Lucidum Asset Name". In the example above, the value of "Luciudm Asset Name" will be stored in the ServiceNow field "name".
    - ***Send first IP address only***. When this option is enabled, only the first IP address of a device will be added to the ServiceNow asset. If it is disabled, all IP addresses of the device will be added to the ServiceNow asset.
    - ***Send first Mac address only***. When this option is enabled, only the first MAC address of a device will be added to the ServiceNow asset. If it is disabled, all MAC addresses of the device will be added to the ServiceNow asset.
14. If you selected ***Create ServiceNow Incident (IRE API)*** in the **General** page, in the **Details** step, enter the following:

    ![servicenow_new_action_incident.png](https://lucidum.cloud/docs/servicenow_new_action_incident.png)

    - ***Output Fields***. For the records selected with the ***Filters*** field, specify the columns to display. When creating or editing the query, you can select these fields in the **Query Results** page > **Edit Column**button.
    - ***Incident Description***. Description that you want to appear in ServiceNow.
    - ***Incident Category***. Incident category you want to assign to this incident. For details on incident categories in ServiceNow, see [https://docs.servicenow.com/bundle/xanadu-it-service-management/page/product/incident-management/reference/r_CategorizingIncidents.html](https://docs.servicenow.com/bundle/xanadu-it-service-management/page/product/incident-management/reference/r_CategorizingIncidents.html).
    - ***Incident Urgency***. The urgency you want to assign to this incident. For details on incident urgency in ServiceNow, see [https://docs.servicenow.com/bundle/xanadu-it-service-management/page/product/problem-management/concept/prioritise-problems.html](https://docs.servicenow.com/bundle/xanadu-it-service-management/page/product/problem-management/concept/prioritise-problems.html).
    - ***Incident Impact***. The impact rgency you want to assign to this incident. For details on incident urgency in ServiceNow, see [https://docs.servicenow.com/bundle/xanadu-it-service-management/page/product/problem-management/concept/prioritise-problems.html](https://docs.servicenow.com/bundle/xanadu-it-service-management/page/product/problem-management/concept/prioritise-problems.html).

## Best Practices

In ServiceNow:

- **Create a dedicated discovery source for Meridian****.** Add a new choice value to the `discovery_source` field on the CMDB (CI Class Manager → the target CI class → `discovery_source` field → Choices). A dedicated source also makes it clear in the CMDB which records came from Meridian.
- **Grant Meridian's API read access to the**`sys_choice`**table.** ServiceNow actions populates the Data Source dropdown by reading the `discovery_source` choice list from `sys_choice` first. Without this access, a newly created source (e.g., `Meridian`) won't appear in the dropdown until at least one CI already uses it. Granting `sys_choice` read lets the dropdown reflect the current choice list immediately.
- **Set the data source's priority according to how authoritative Meridian should be.** This is configured in the CMDB reconciliation / Data Source Precedence rules (per attribute and CI class) and controls what happens when Meridian and another source (e.g., Tanium) both provide values:

  - **Rank Meridian*****higher*** if it should be the source of truth. Meridian values will overwrite those from lower-priority sources.
  - **Leave Meridian*****lower*** for enrich-only behavior. Meridina will update fields not already owned by a higher-priority source.