> 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/da/automatisering/about.md).

# Om automatisering

Kør scripts, planlæg jobs, og udfør ad hoc-kommandoer i terminaler i PowerShell Universal på tværs af konfigurerede miljøer og alternative legitimationsoplysninger.

### Kør scripts

De kan køre [scripts ](/powershell-universal/da/automatisering/scripts.md)i PowerShell Universal. PowerShell Universal integrerer tæt med PowerShell-værten for at levere en brugergrænseflade til param-blokke, udlæse detaljerede objekter, vise fremskridt og endda lade brugeren give feedback.

### Planlæg jobs

De kan planlægge jobs, så de [kører kontinuerligt](/powershell-universal/da/automatisering/schedules.md#continuous), [på bestemte tidspunkter ](/powershell-universal/da/automatisering/schedules.md#cron)eller endda [når hændelser indtræffer](/powershell-universal/da/automatisering/triggers.md) inden for PowerShell Universal-platformen.

### Ad hoc-kommandoer

Kør ad hoc-kommandoer i [terminaler ](/powershell-universal/da/automatisering/terminals.md)i et hvilket som helst af Deres konfigurerede miljøer og, eventuelt, som alternative legitimationsoplysninger.


---

# 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/da/automatisering/about.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.