> For the complete documentation index, see [llms.txt](https://docs.halosecurity.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.halosecurity.com/docs/platform/automations/target-automations.md).

# Target Automations

Automatically manage targets.

{% hint style="info" %}
These rules and actions can used to configure your [automations](https://app.halosecurity.com/user/settings/automations/) with the **Target** type.
{% endhint %}

## Rules

Add rules too match targets based on the following criteria.

<details>

<summary>Rule Types</summary>

Each type has a variety of value options with details provided in the add rule modal.

* Risk Score
* Date
* Created Date
* Scan
* IP
* Domain
* Technology
* Technology Category
* Country
* Name
* Hostname
* Scan Frequency
* Issue Count
* Issue Id
* Issue Name
* Issue Severity
* Issue Department
* Service
* Port
* Has HTTP Redirect
* HTTP Location
* Tag
* Whois Organization
* Firewall Product
* Issue Name
* Issue Severity
* Issue Department
* Technology
* Technology Category
* HTTP Response Code

</details>

## Actions

The following actions are supported:

* **Tags - Sync**: Matching targets will have the selected tag(s) added. For targets that do not match the rules, the selected tag(s) will be removed.
* **Tags - Add**: Matching targets will have the selected tag(s) added.
* **Tags - Remove**: Matching targets will have the selected tag(s) removed.
* **Archive Target:** Matching targets will be [archived](/docs/platform/targets/managing-targets.md#archiving-targets).
* **Scan Policy**: Matching targets will have the selected [scan policy](/docs/platform/targets/scan-policies.md) applied.
* **Scan Frequency**: Matching targets will have the selected scan frequency applied.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.halosecurity.com/docs/platform/automations/target-automations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.