---
title: Splunk Actions
description: "## Actions for Splunk - ***Send Webhook***. Sends a custom set of Lucidum data to Splunk. ## Use Cases Below are the possible use cases for the ***Send Data***action: - If you want to run Lucidum “headless”, you can send…"
url: "https://lucidum.io/docs/splunk-actions/"
updated: "2025-09-24"
category: Actions / List of Actions / S
---

# Splunk Actions

## Actions for Splunk

- ***Send Webhook***. Sends a custom set of Lucidum data to Splunk.

## Use Cases

Below are the possible use cases for the ***Send Data***action:

- If you want to run Lucidum “headless”, you can send relevant data to Splunk on a regular schedule.
- You can send data to Splunk for storage, analysis, and threat response.

## Prerequisites

To execute Splunk actions, you must:

- Configure a user account in Splunk that has API permissions. The required parameters are described in the instructions for creating a Lucidum Connector for Splunk. For details, see [https://lucidum.io/docs/splunk/](https://lucidum.io/docs/splunk/).
  **NOTE**: The specified account should have **read and write**permissions.

## 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)

## Splunk Configuration

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

- ***Configuration Name.*** Identifier for the Configuration. This name will appear in the Lucidum Action Center.
- ***Splunk Webhook URL**.*The URL that Splunk will use to receive data from Lucidum. For example, https://http-inputs-lucidum.splunkcloud.com/services/collector.
- ***Header Key***. The “key” part of a key:value pair to include in the webhook header. The default value is **Authorization**. This “key” allows to send credentials for basic HTTP authentication for Splunk.
- ***Header Key Value***. The “value” part of a key:value pair to include in the webhook header. This “value” allows to send credentials for basic HTTP authentication for Splunk. The value will be of the format Splunk <hec-token>. To generate the token, see [https://docs.splunk.com/Documentation/Splunk/9.1.1/Data/UsetheHTTPEventCollector](https://docs.splunk.com/Documentation/Splunk/9.1.1/Data/UsetheHTTPEventCollector).
- ***Max # of Records per Payload***. The maximum number of records to send to Splunk in each action. The default value is “100”.

## Create or Edit an Action

To create an action for Jira Cloud:

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

   ![splunk_general_page.png](https://lucidum.cloud/docs/splunk_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. Select *Send Webhook*.
   - ***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 Custom Success for help on using historical data without affecting performance.
9. Click the **Apply** (page and pencil) icon.

   ![splunk_action3.png](https://lucidum.cloud/docs/splunk_action3.png)
10. Click the **Next**(>) icon.
11. In the **Schedule** step, enter:

    ![splunk_action_4.png](https://lucidum.cloud/docs/splunk_action_4.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. In the **Details** step, enter the following:

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

    - ***Output Fields***. For the records selected with the ***Filters*** field, specify the columns to include in the payload. When creating or editing the query, you can select these fields in the **Query Results** page > **Edit Column**button.
    - ***Splunk Payload Template***. The data to send to Splunk, in Jinga format. The field includes a default Jinja template that you can edit. The default template creates a JSON dictionary that include the key:value pair “event:Lucidum Vulnerability” and then additional key value pairs for each field included in the ***Output Fields*** field. For details on Jinja, see [https://jinja.palletsprojects.com/en/3.1.x/templates/](https://jinja.palletsprojects.com/en/3.1.x/templates/).
    - ***Dedupe Previous Jobs***. In this field, you specify whether you want duplicates of asset IDs (if your query is for assets) or user IDs (if your query is for users). You can specify integers starting at 0 (zero).

      - If you specify “0” (zero), Lucidum includes all the records from the query in each delivery to Splunk.
      - If you specify “1” (one), Lucidum examines the previous webhook payload and excludes records for asset IDs or user IDs that were sent in the delivery to Splunk.
      - If you specify “2” (two), Lucidum examines the last two webhook payloads and excludes records for asset IDs or user IDs that were sent in the previous two deliveries to Splunk.
