> 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/faqs/workflows/what-is-a-workflow-in-astera.md).
# What is a Workflow in Astera?
Workflow is a process orchestrated to run a sequence of tasks such as running a program, sending an e-mail, executing a SQL query, etc. The tasks are executed according to a pre-defined order, following a custom logic which decides what path must be activated under what conditions.
You can also specify what should happen at each step if a task runs successfully or returns an error in a workflow. You can also route the workflow by using a Boolean condition suitable to your scenario. You can even nest another workflow or a dataflow within your workflow.
Once designed, a workflow can be deployed on the server and scheduled to run automatically as per the specified time and frequency.
To create a workflow in Astera, go to the menu bar at the top and select File > New > Workflow.
---
# 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/faqs/workflows/what-is-a-workflow-in-astera.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.
