---
title: "Create a discovery action | Lansweeper Platform"
slug: "create-a-network-discovery-action"
description: "Create a discovery action to define what Lansweeper discovers, how often discovery runs, and where the scan originates across your network."
status: "update"
updated: 2026-09-25T08:17:12Z
published: 2026-09-25T08:17:12Z
canonical: "docs.lansweeper.com/create-a-network-discovery-action"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lansweeper.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Create a discovery action

Discovery actions are a key part of Lansweeper Discovery. They define what is discovered, how often discovery runs, and where the process originates. Configuring these actions correctly ensures you build a complete and accurate IT and OT asset inventory.

:::(Info) (Other discovery methods have their own actions)
The IT Agent and Cloud Discovery use their own actions. For those, see [Define when IT Agent Discovery runs](/docs/create-an-it-agent-discovery-action) and [What is Cloud Discovery?](/docs/what-is-cloud-discovery).
:::

## Why configure discovery actions?

A discovery action defines the scope of what will be discovered and ensures the process runs correctly with the right access. Specifically, a discovery action lets you:

- **Define a scan target**: Choose which assets to discover based on the IP range, subnet, or Active Directory OU.
- **Control coverage**: Refine the results by setting inclusions and exclusions to prevent scans from overlapping or wasting resources.
- **Run under the proper context**: Each action uses an assigned sensor and associated credentials to query assets securely.
- **Ensure discovery happens consistently**: Actions determine when and how discovery tasks are launched within your deployment.

Without setting up discovery actions, your Network Discovery deployment won’t know where to look or what to include or exclude.

## Prerequisites

- An installed hub and sensor for either [Windows](/docs/install-network-discovery-windows), [Linux](/docs/install-network-discovery-linux), or [Mac](/docs/install-network-discovery-macos)
- [Discovery credentials](/docs/create-discovery-credentials) created

## Create a discovery action

1. In your site, go to **Discovery > Actions > Create action**.
2. Select **Agentless > Create**.
3. Enter a **Name** and an optional description, then select **Next step**.

### Add targets and exclusions

Create targets to specify where you want discovery to occur.

1. Select **Create target**.
2. Select either:

   - **Custom (IP, Host, or SCCM)**. Enter the respective information.
   - **Active Directory**. Enter a name, select what to discover, enter the Domain DNS name and ADSI path, select a LDAP protocol and a port.
3. Select **Create**.

Exclude IP addresses or ranges you don’t want to discover. This prevents redundant discovery and duplicate data if multiple actions overlap.

1. Select **Create exclusion**.
2. Enter one or more IP addresses or ranges.
3. Select **Create**.

Select **Next step.**

### Add a trigger

This will determine when discovery will occur.

1. Select **Create trigger**.
2. Select either:

   - **Instant** to run at a scheduled time on select days. Enter the name, time, and days you prefer.
   - **Recurring** to run at repeated hourly intervals. Enter a name and specify how often you want your discovery to run.
3. Select **Create**.
4. Select **Next step**.

### Assign a sensor

This will specify which sensor your discovery action applies to.

1. Select one or multiple sensors from the list.
2. Select **Next step**.

### Enable advanced options

Advanced options are optional. You can leave them all disabled and continue to the next step.

1. Optionally, enable **AI usage tracking** to collect AI-related usage signals during discovery, such as AI tools, services, and infrastructure. This doesn’t include the content of AI conversations. For more information, see [Enable AI usage tracking](/docs/enable-ai-usage-tracking).
2. Optionally, enable **Ping hosts before scanning**.
3. Select **Next step**.

### Assign a credential

Each discovery action must use credentials to query targets. You can assign multiple credentials, which will be tried in order until one succeeds.

:::(Info) (Set up credentials first)
If you have not already, [create discovery credentials](/docs/create-discovery-credentials).
:::

1. Select one or multiple credentials from the list.
2. Drag the credentials to reorder them. Credentials are attempted in the order shown, so put the most commonly successful credentials at the top to speed up scanning.
3. Select **Next step**.

:::(Warning) (Only the first 10 credentials are used)
A discovery action uses only the first 10 credentials in the list. Any credentials after the first 10 aren’t used.
:::

### Create the action

Now that you’ve entered all the required information, you can create your action.

1. Optionally, select the **Start this action after clicking 'Save and finish'** checkbox.
2. Select **Save and finish**.