> For the complete documentation index, see [llms.txt](https://bugrecon.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bugrecon.gitbook.io/docs/features-list/automation.md).

# Automation

Automation lets you **auto-run scan types after subdomain discovery**. When new subdomains are found (for example from a subdomain scan or CertStream), BugRecon can automatically queue follow-up scans so you don't have to trigger them manually.

![Automation](https://1075470145-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV2n4UTcrS4SHhY2NTi0v%2Fuploads%2Fgit-blob-f36cdb838cf8aea28a777e9fbcba90e941700076%2Fautomation.png?alt=media)

## What you can do

* **Configure automation** in **Settings → Automation**. Use the toggles to choose which scan types run automatically after subdomain discovery:
  * **Port scan** - Automatically run a port scan on newly discovered subdomains
  * **HTTP scan** - Automatically run an HTTP scan
  * **Subdomain scan** - Automatically run a subdomain scan (e.g. for recursive discovery)
  * **Leaks scan** - Automatically look for leaks
  * **Vulnerability scan** - Automatically run a vulnerability scan
  * **URL scan** - Automatically discover URLs
  * **Basic auth scan** - Automatically run basic authentication checks
  * **Screenshot scan** - Automatically capture screenshots
  * **Domain takeover scan** - Automatically check for takeover risks
  * **JavaScript scan** - Automatically scan JavaScript files
  * **Wildcard to CertStream** - Automatically add newly discovered wildcard domains to CertStream monitoring
* **Track automation jobs** in the **Queue** module: jobs triggered by automation show **Automation** as their origin (as opposed to manually queued jobs).

Automation applies when subdomains are discovered in your workflows (e.g. after a subdomain scan or when CertStream detects a new certificate). Combined with [Tasks](/docs/features-list/modules/tasks.md) (scheduled scans) and [CertStream](/docs/features-list/modules/certstream.md), you can build a fully automated reconnaissance pipeline.

## Scan cascade

When new subdomains appear, BugRecon can automatically queue a **scan cascade** - a chain of follow-up scans. You configure which scan types run via the toggles; the platform then runs them in sequence (port → HTTP → vulnerability → leaks → URL → basic auth → screenshot → takeover → JavaScript). Newly discovered wildcard domains can also be added to CertStream automatically for recursive coverage.

## Availability

Automation is available for **Premium** and **Enterprise** only. Free and Basic plans do not have access to automation functionality.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://bugrecon.gitbook.io/docs/features-list/automation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.