> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/documentation/automations/actions-in-rewst/workflows-actions.md).
# Workflows actions
## Available workflows actions
The **Workflows** actions accordion menu contains any existing workflows in the workflow list for the related child organization. This actions menu is what powers Rewst's [subworkflow](https://docs.rewst.help/documentation/workflows/different-types-of-workflows#subworkflow) functionality, by letting you reuse existing workflows as individual tasks in a more broadly scoped integration.
The available actions in this submenu will be different for each of your child organizations. Each time you create a new workflow, the list will grow.
An example of an org's Workflows action accordion menu
Unpacking a Crate will also add the workflows in that Crate to the Workflows actions accordion menu. You'll gain many of the common automations our team has pre-built workflows for, and can use them to build your own custom workflows.
The parameters tab of a workflows task
Note that most workflows actions will use [input variables](/documentation/automations/workflows/data-input-and-output-input-variables-and-context-variables.md). If present, these will appear in the **Parameters** tab of the task.
---
# 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.rewst.help/documentation/automations/actions-in-rewst/workflows-actions.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.
