> 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/what-are-workflows.md).
# What are Workflows?
*Workflow* enables automated and repeated execution of a sequence of tasks, such as running a program, sending an email, uploading a file, running a transfer setting or batch, executing some SQL code, and many others. The tasks run according to some predefined path and follow the custom logic that controls under which circumstances specific paths should be activated.
Workflows make it easy to visualize and implement complex sequences of tasks because pieces of a workflow can be used like ‘building blocks’. These building blocks can be pasted into a different workflow, or even into the same workflow, which allows you to quickly replicate tasks, or even sequences of tasks, with similar properties. Workflow tasks can run sequentially as well as simultaneously.
Objects can be added to a workflow in several ways, such as direct drag-and-drop of files from your local machine, drag-and-drop of tables or views from the built-in Data Source Browser, or by adding an object from the Toolbox.
### Workflow Tasks
There are multiple options present in the *Workflow Tasks* tab within the Toolbox.
These options are:
Decision
EDI Acknowledgment
File System
File Transfer
OR
Run Dataflow
Run Program
Run SQL File
Run SQL Script
Run Workflow
Send Mail
In subsequent articles, we will look at what each of these objects do.
---
# 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/what-are-workflows.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.