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

# Automation

- [About Automation](https://docs.devolutions.net/powershell-universal/automation/about.md): Run scripts, schedule jobs, and execute ad-hoc commands in PowerShell Universal terminals across configured environments and alternate credentials.
- [Scripts](https://docs.devolutions.net/powershell-universal/automation/scripts.md): Create and configure PowerShell scripts in PowerShell Universal, covering parameters, run-as credentials, comment-based help, and job statistics.
- [Parameters](https://docs.devolutions.net/powershell-universal/automation/scripts/parameters.md): Generate PowerShell Universal job input forms automatically from script param blocks, supporting types like DateTime, PSCredential, File, and ValidateSet.
- [Jobs](https://docs.devolutions.net/powershell-universal/automation/jobs.md): Track PowerShell Universal jobs, inspect output and statuses, configure output guardrails and sensitive-data redaction, and invoke jobs from scripts, apps, and REST.
- [Schedules](https://docs.devolutions.net/powershell-universal/automation/schedules.md): Schedule PowerShell Universal scripts with simple intervals, CRON expressions, one-time runs, or continuous jobs, including run-as accounts and conditions.
- [Run schedules with PowerShell](https://docs.devolutions.net/powershell-universal/automation/schedules/run-schedules-with-powershell.md): Use Invoke-PSUSchedule to trigger an existing PowerShell Universal schedule immediately, using the same execution path as the admin console.
- [Terminals](https://docs.devolutions.net/powershell-universal/automation/terminals.md): Open in-browser PowerShell terminals in PowerShell Universal, targeting environments and run-as credentials with configurable history and timeouts.
- [Tests](https://docs.devolutions.net/powershell-universal/automation/tests.md): Run and review Pester test suites directly within PowerShell Universal, tracking historical results for individual test files and full test runs.
- [Triggers](https://docs.devolutions.net/powershell-universal/automation/triggers.md): Trigger PowerShell Universal scripts automatically on events like job completion, server startup, user login, git sync, or computer status changes.
- [Workflows](https://docs.devolutions.net/powershell-universal/automation/workflows.md): Chain scripts and AI prompts into multi-step PowerShell Universal workflows using the Workflow and PSUItem variables to pass data between activities.


---

# 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.devolutions.net/powershell-universal/automation.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.
