> For the complete documentation index, see [llms.txt](https://docs.diaflow.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.diaflow.io/getting-started/lets-start-with-the-basics/how-a-workflow-works.md).
# How a workflow works
A **workflow** is a process divided into **three parts**.
You can refer to the [**Workflow Builder**](/workflow-builder/overview.md) section for more information.
A **Workflow** is a set of connected steps.
It takes an input, processes it, and returns a result.
## How a Workflow works
A Workflow usually has 3 parts:
* **Trigger:** starts the flow with an input
* **Nodes:** process the data step by step
* **Output:** shows the final result
For example, a Workflow can receive a file, analyze it with AI, and return an answer.
{% hint style="info" %}
Tip: Use **@** to refer to the previous node's output.
{% endhint %}
### Next steps
* Learn the basic building block in [How a Component works](/getting-started/lets-start-with-the-basics/how-a-node-works.md).
* Build an example in [Creating your first Workflow](/getting-started/lets-start-with-the-basics/creating-your-first-workflow.md).
* Explore more in [Flows](/workflow-builder/overview.md).
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.diaflow.io/getting-started/lets-start-with-the-basics/how-a-workflow-works.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.