> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/dokumentation/automation/workflows.md).

# Workflows

Create, start, share and monitor workflows (flows) in the flow designer: triggers, actions, variables, modifiers, filters, webhooks and error notification.

**Path:** sidebar → **"Automation" → "Workflows"**

A **flow** consists of a **trigger** (what starts the process), **actions** (what happens) and optionally **conditions** (when something happens). You build flows via drag & drop in the **flow designer**.

## The flow list

* **"Create Flow"** creates a new flow.
* Filters: "Running flows", "Stopped flows", "My flows", "Shared with others", "Shared with me". Sort by modification or creation date, list or tile view.
* Menu per flow: "Open", "Rename", "Insights" (logs), "Clone" (copy), "Share" and "Remove" (delete; **deleted flows cannot be restored**).
* When **sharing**, you choose with whom (by email, scope or domain) and which rights apply: "Read", "Start", "Stop".

## Building a flow

1. **"Create Flow"** → open the flow. The designer opens in full screen.
2. On the left, you choose components:
   * **Utilities**, e.g. Filter, Converter, Timer, Scheduler, Webhook, HTTP and Tasks,
   * **Applications**, e.g. equipme, Microsoft, email and many more.
3. Drag a **trigger** onto the canvas, e.g. "New Employee" from the equipme connector, a schedule (Scheduler) or a webhook.
4. Add actions and connect the components.
5. On the right, you configure the selected component. You connect accounts via **"Connect account"**.
6. **Start** the flow. A flow that has been saved but not started does not run.

In the designer you will also find undo/redo, zoom, align, logs and, in the menu, "Rename", "Share", "Change Description" and export as SVG/PNG or print.

## Passing data between components

* **Variables:** Use the variable picker to use values from previous components, e.g. the name of a new employee in an email.
* **Modifiers:** Click an inserted variable to transform it, e.g. convert text to uppercase, shift a date, divide a number, filter, join or sum lists. Modifiers can be chained.

## Logic

* **Filters:** Only let data through if a condition is met, e.g. "Contains", "Equal", "Not Equal", "Greater/Less Than", "Range" or "Is Not Empty". You combine multiple conditions with "And".
* **Scheduling:** Start flows once, recurringly or at fixed times.
* **Webhooks:** A webhook trigger provides a URL through which other systems start the flow. If you respond later with your own response component, turn off "Immediate Response".
* **HTTP:** Call any interface with GET, POST, PUT or DELETE.
* **Approvals and follow-up questions:** You integrate human decisions via approval requests ("Equipme Approval" module) or web forms ("Forms" module) (see [equipme connector](/dokumentation/automation/connectors/equipme.md)).

## Finding errors

* **Logs** in the designer or **"Insights"** show every execution with status, components, timestamp, message and error.
* **Getting notified of errors:** Add the **"OnError"** trigger and connect it, e.g., with "SendEmail". The trigger checks regularly and only reports errors that were actually logged. The flow must be started.

## Examples

* **Creating new employees from the HR system:** see [equipme connector](/dokumentation/automation/connectors/equipme.md).
* **Approval process:** with the "Equipme Approval" module, e.g. new order request → approval by the supervisor → decision → order. To do this, enable "Custom approval" under [Configuring approvals](/dokumentation/procurement/approval-settings.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hub.equipme.io/dokumentation/automation/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.