> For the complete documentation index, see [llms.txt](https://docs.empowergpt.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.empowergpt.ai/workflows/introduction-to-workflows.md).

# Introduction to Workflows

### Introduction to Workflows

Build reliable, AI-driven automations by connecting AI, enterprise data, integrations, and custom logic into multi-step **Workflows**—made up of reusable **Blocks**.

<div data-with-frame="true"><figure><img src="https://2192711725-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fc2KRGWrkyRO0iZN5Lyeg%2Fuploads%2FZOgnKVrNUz085WegcfhI%2Fimage.png?alt=media&amp;token=430ddf5e-d09a-4d25-b87f-9c7887e8cadc" alt=""><figcaption></figcaption></figure></div>

### What are Workflows?

**Workflows** in **EmpowerGPT** let you design end-to-end automations that run a process from start to finish — without manual copy/paste between tools.

If you already use EmpowerGPT for:

* **Chat** (interactive conversations),
* **Agents / Assistants** (specialized AI helpers),
* **Enterprise knowledge** (governed access to internal content),
* **Integrations** (connecting business systems),

then **Workflows** is the orchestration layer that ties these capabilities together into a repeatable automation.

### What are Blocks?

A workflow is built from **Blocks**. Each Block performs one job—like triggering a run, calling an AI agent, transforming data, branching based on conditions, requesting approval, or pushing results into an external system.

Typical workflow building blocks include:

1. **Trigger Block** – Defines how and when the workflow starts. Every workflow begins with a trigger, such as a manual run, scheduled event, incoming email, or webhook.
2. **Logic Blocks** – Add custom logic to control how the workflow executes. Logic blocks include **Conditions**, which determine which path the workflow should follow based on defined rules, and **Loops**, which repeat a set of actions for multiple items.
3. **Agent Block** – Brings AI capabilities into the workflow. The Agent can follow instructions, analyze information, generate content, make decisions based on the provided context, and use available tools or integrations to perform tasks.
4. **Output Block** – Defines the information returned when the workflow completes.


---

# 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.empowergpt.ai/workflows/introduction-to-workflows.md?ask=<question>&goal=<user_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.