> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/deployr/1.1/reference/step-definitions/install-multiple-applications.md).
# Install multiple applications
The Install multiple applications step will install a list of applications in the order that they are specified. This list of applications can be configured on the step itself:
Multiple applications can also be installed using a task sequence variable. You can specify the prefix for that list with a default of "Applications":
This list can be set via a Run PowerShell script step or a web service call. An example PowerShell script that specifies the content IDs and versions of four applications that should be installed:
```powershell
# Install my list of apps
$tsenvlist:Applications = @("d7775b33-9cfe-4fcd-b3a2-dc129cfc769e:1",
"c2032a9a-d15a-4275-97a2-e317a84f3437:1",
"2ae9d965-e89f-4e10-89e1-e55caeda997b:1",
"ebe17300-286a-4bf2-a172-aa8a4d64b186:1")
```
---
# 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://documentation.2pintsoftware.com/deployr/1.1/reference/step-definitions/install-multiple-applications.md?ask=&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.
