> 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/cloud/concepts/advanced-concepts/scripts.md).

# Scripts

Automate Devolutions Cloud tasks with PowerShell scripts to provision entries, export data, and extend PAM workflows.

Scripts in the Devolutions Cloud platform automate operations such as provisioning entries, exporting data, or extending PAM workflows. In Devolutions Cloud, you can configure a PowerShell entry that runs a script with securely injected credentials, or use the PowerShell script export type to export entries as JSON or CSV through a generated script.

For deeper automation, administrators rely on Devolutions PowerShell and its Devolutions Cloud-specific cmdlets to create or update entries, manage vaults, and integrate with CI or ITSM pipelines. This makes it practical to script tasks like nightly inventory exports, bulk permission changes, or PAM provider maintenance without exposing secrets in script code.

#### Related topics

* [Configure a PowerShell entry in Devolutions Cloud](/cloud/knowledge-base/how-to-articles/configure-a-powershell-entry-in-devolutions-cloud.md)
* [PowerShell script export type](/cloud/web-interface/help-and-tools/export/powershell-script-export-type.md)
* [Devolutions PowerShell with Devolutions Cloud](https://docs.devolutions.net/powershell/devolutions-cloud-powershell)


---

# 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/cloud/concepts/advanced-concepts/scripts.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.