> 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/cli/for-devops-and-administrators/automate.md).

# Automate with Devolutions CLI

Use Devolutions CLI in CI pipelines and scripts: sign in without a prompt, install it on build agents, read JSON results, and run without questions.

Devolutions CLI works the same in a pipeline as in your terminal: sign in once, then pass `devo://` references to `devo secret run`. A few things change when nobody is there to answer: the sign-in can't open a browser, the results must be read by a script, and nothing may wait for a prompt. These pages cover each one.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Sign in from a CI pipeline</strong></td><td>Use an application key or an API key from a protected variable or file, never as an argument.</td><td><a href="/cli/for-devops-and-administrators/automate/ci-sign-in.md">Sign in from a CI pipeline</a></td></tr><tr><td><strong>Install Devolutions CLI on build agents</strong></td><td>Extract one archive, keep each job's configuration separate, and clean up the background process.</td><td><a href="/cli/for-devops-and-administrators/automate/install-on-runners.md">Install Devolutions CLI on build agents</a></td></tr><tr><td><strong>Read results as JSON</strong></td><td>Get the same envelope from every command, for successes and errors.</td><td><a href="/cli/for-devops-and-administrators/automate/json-output.md">Read results as JSON</a></td></tr><tr><td><strong>Run without prompts</strong></td><td>Fail instead of waiting, answer prompts in advance, and confirm changes with <code>--yes</code>.</td><td><a href="/cli/for-devops-and-administrators/automate/non-interactive.md">Run without prompts</a></td></tr></tbody></table>


---

# 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/cli/for-devops-and-administrators/automate.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.