> For the complete documentation index, see [llms.txt](https://documentation.astera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.astera.com/workflows/run-workflow.md).
# Run Workflow
The *Run Workflow* task lets the user integrate a workflow within a workflow. It works on the concept of a nested workflow. You can therefore execute multiple workflows within one workflow.
1. First, we will drag-and-drop the *Run Workflow* object from the Toolbox. Right-click on the object’s header and select *Properties* from the context menu.
{% hint style="info" %}
**Note:** This object is present only in the Workflow Tasks section of the Toolbox in a workflow designer.
{% endhint %}
This will open the *Start Workflow Job Properties* window.
*Path:* Browse the file path of the workflow that needs to be executed.
2. Select a file path from an existing workflow.
3. Click *Next* and you will be taken to the *General Options* screen.
4. Once done, click *OK*, and the *Run Workflow* object will be configured.
{% hint style="info" %}
**Note:** If you are using a project that contains workflows, you can simply drag-and-drop a .wfs document to the workflow designer and it will create a pre-configured *Run Workflow* object.
{% endhint %}
With this, we conclude the configuration and working of the *Run Workflow* object in Astera.
---
# 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.astera.com/workflows/run-workflow.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.
