Xentral adapts to you

Just open the Flows app in Xentral. You’ll find active workflows, logs, and the editor (if enabled). For step-by-step help, head over to our Help Center.

Anything that follows clear if-then logic and can be controlled through the Xentral API. From follow-up emails, task creation, and stock alerts to automatic status changes, write-offs, and syncing your inventory to systems like Shopify. If a process runs on rules, you can map it in Flows.

No. The workflow editor is built for everyday users. You build automations with drag-and-drop directly in the Xentral interface. No code, no IT ticket.

The library contains over 70 ready-made workflows you can activate with one click. Use "Add Flow" to import a template.

With "Create Flow," you start with a blank workflow and build it from scratch in the editor.

Library workflows can also be used as templates and adapted to your processes directly in the editor.

You'll find the Flows app in the Xentral main menu under "Automations." That's where you'll see all active workflows, logs, and the editor. For now, only users with admin rights can make edits. If you don't see the editor, reach out to your Customer Success Manager or create a support ticket. Step-by-step guides are available in the Help Center and in the Xentral Connect manual at connect.xentral.com.

Using the module is free across all plans. Going forward, billing will be purely usage-based, measured by job executions. Every service package includes a monthly volume. The bigger your package, the bigger your included volume. Stay within it and you pay nothing extra. If you go over, a small overage fee applies per 1,000 job executions. You'll find the exact pricing in the current terms and conditions.

Until September 2026, usage is completely free, even beyond your included volume. Use this time to see how many job executions your automations actually generate. Ahead of the billing start, you'll get a dashboard that shows your usage and included volume transparently.

A job execution is one complete run of a workflow. We don't count individual nodes or components inside a flow separately. That's a deliberate difference from tools like n8n or Make.com, which sometimes bill at the component level.

Yes. You can deactivate individual elements or entire flow groups and let the workflow run in log-only mode, without triggering any real actions. On top of that, you can test each element individually using "Test," including with mocked values. If you want a fully isolated environment, use the Xentral staging instance. Flows are always tied to their instance, so staging flows have no effect on production data.

The Flow editor gives you the Xentral API connector along with standard data structures and operators. External API connectors, REST connectors, webhook triggers, and mapping tables are deliberately not enabled here, to keep complexity in the editor low.

For external connections, custom webhooks, complex nested flows, or data mapping, you need full access to the Xentral Connect backend. That access is available to our certified partners and to customers on the Scale package. For logistics integrations, there's also the Carrier Integration Service.

At the moment, all Flows are provided directly by us and are therefore free to use. In the future, there will also be Flows built by external developers, which may be available for a fee.

Flows are built for deterministic, rule-based processes. Classic if-then logic. They're reliable, fast, and cheap to run. AI agents take on tasks that need human interpretation, like understanding an incoming email or matching unstructured information. The two complement each other. Anything you can solve with rules belongs in Flows. Anything that needs context understanding is handled by an AI agent.

By using Xentral Flows, you agree to the following terms:

• Responsibility for individual processes: All workflows created with Xentral Flows or imported from the library are customer-specific customizations outside the standard Xentral service scope and fall under your responsibility.
• Partner implementations: If a Flow has been created or modified by a certified Xentral partner, the partner carries the responsibility.
• Support & consulting: Individual Flows are not covered by regular Xentral support. Assistance with creation, adjustments, or troubleshooting is available as paid consulting through the Xentral Solution Engineering team.
• Liability & system impact: Xentral takes no responsibility for how individual Flows function or their effects on the overall system, particularly performance degradation caused by resource-intensive processes.
• API usage: Many Flows rely on the Xentral API. Above-average API usage may incur additional costs in the future.
• Safeguarding system stability: Xentral reserves the right to deactivate Flows that endanger the stability of the overall system, including without prior notice.

Yes. You can find the Help Center article on Xentral Flows here: help.xentral.com. We continuously update the documentation whenever new features are released.

Certified Xentral users and partners can access a more powerful version of the editor, with deeper customization and integration capabilities.

Yes, fully automatically.

Yes. The API that Xentral Flows use to communicate with your Xentral instance is versioned, ensuring your Flows remain stable and reliable after updates.

Yes. Custom fields can also be used and integrated within Flows.

At the moment, all Flows are provided by us and are therefore free to use. In the future, Flows built by external developers will also be available, some of which may be paid.

No. The predefined workflows provided by Xentral are available to all customers without restrictions and can be activated without partner support. Custom Flows depend on access to the Workflow Editor, which will be available to customers starting with the Premium (Success) S package.

After completing the required certification, customers can also use the Workflow Editor independently without the need for a partner.

Yes. Anything that the Xentral API supports can also be automated using Flows.