---
title: Workflows with AI in XOS | XOS
description: Workflows in XOS: connect flows on one canvas, started by a schedule, an app event, a form or a webhook. With an AI block, templates and a company library.
url: https://xos.prozessx.com/en/modules/workflows/
---

# Build once. Runs by itself.

Connect triggers, conditions, AI blocks and actions in your apps and XOS modules into one flow.

[Book a demo →](https://xos.prozessx.com/en/book-a-demo/)[Sign up](https://xos.prozessx.com/signup)

In short: Workflows in XOS: connect flows on one canvas, started by a schedule, an event in an app, a form or a webhook. With an AI block, templates and a company library.

As of November 12, 2026 · ProzessX

A trigger starts the flow, the line runs through step and condition to the result. Sample view, simplified.

Knowledge and data

## Build processes that start and run on their own.

Included From the Pro plan, no add-on package

Requirement From the Pro plan. In the Beginner plan, XOS shows an upgrade card, existing workflows are kept.

[Book a demo →](https://xos.prozessx.com/en/book-a-demo/)[All prices](https://xos.prozessx.com/en/pricing/)

## What this module handles for you.

01

### Five ways to start

A workflow starts with a click, on a schedule, on an event in a connected app, through a form or via a webhook.

02

### Schedules without cron

You set the schedule with dropdowns: every few minutes or hours, with a time zone. You never see cron syntax.

03

### Blocks for logic and AI

With condition, branch, filter, merge and set fields, you control the flow.

04

### Actions in apps and XOS

A block can run an action in a connected app or in an XOS module, for example create a task or a contact.

05

### Templates and company library

Start from a template or share a finished workflow with your organization. Sharing saves a copy, later changes do not affect copies already taken over.

06

### Test and trace

You test each block on its own, without running the whole flow.

Sample process

### From email to task.

An example of how a workflow runs in daily work.

Choose a template or describe in the editor what should happen

Set a schedule or an event as the trigger

Check the blocks and test them one by one

Activate the workflow

See in the history what each run did

In the editor, too: an assistant in the editor builds and changes the workflow based on your description. It first checks which blocks and app actions exist, and it does not make any up.

## Related modules.

[WorkplacesOne workspace for files, team and agents.](https://xos.prozessx.com/en/modules/workplaces/)[Knowledge baseStore and approve company knowledge and use it in the chat.](https://xos.prozessx.com/en/modules/work-drives/)

## Frequently asked questions.

Are there still routines?

No. Routines have been replaced, Workflows are the only automation in XOS.

Who can see and change workflows?

Workflows are a tool for the whole organization. Actions in apps run with the permissions of the person who created the workflow.

## See Workflows in your daily work.

[Book a demo →](https://xos.prozessx.com/en/book-a-demo/)[Sign up](https://xos.prozessx.com/signup)