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

# Workflows: Configure Operational Behaviors & Automations

Workflows let you define how recurring operations behave and automate responses to key activities across the platform.

They are available across core services like Payments, Ledger, and Credit allowing you to individually design how service-specific operations execute. For example, you can define how a payment flow is routed, how a credit check is performed, or how the ledger should record balance updates.

In addition to these **service-level flows**, you can also create **automation workflows** that respond to system activity. These are useful for orchestrating cross-service reactions, such as sending an alert when a customer hits a credit threshold, triggering a task when a new entity is created, or updating account details after a role change.

All workflows are created using a visual builder in the Console, making it easy to design logic without writing code.

<div data-full-width="true"><figure><img src="https://1792085566-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkIq1PGbSmC3vQR1DFPNM%2Fuploads%2Fgit-blob-7da8453f3324a809b377451bd0eebadae2b17846%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure></div>

***

#### **Service Workflows**

Service workflows define how a system service behaves during execution. These workflows determine internal logic such as:

* Which providers to call
* What validation rules to apply
* What data to fetch or ignore

Examples:

* **Payments:** Define execution paths, provider selection, fraud checks
* **Credit:** Decide which credit bureaus to consult, scoring logic
* **Ledger:** Define rules for how and when accounts are credited or debited

#### 2. **Automation Workflows**

Automation workflows respond to events that have already happened. These workflows allow operational teams to define what should happen next across services like task creation, notification, or account updates.

Examples:

* **Role Change:** Reassign tasks when an employee leaves a team
* **Risk Closure:** Automatically close tasks linked to blocked customers
* **Create Account:** Generate an account when a new entity is onboarded

***

### Key Features

<table><thead><tr><th width="188.671875"></th><th></th></tr></thead><tbody><tr><td><sub><strong>Visual Canvas</strong></sub></td><td>Use the drag-and-drop canvas to build logic flows using triggers, conditions, and actions.</td></tr><tr><td><sub><strong>Triggers and Actions</strong></sub></td><td><ul><li>Internal events (like <code>EmployeeDeactivated</code>, <code>EntityCreated</code>)</li><li>Custom HTTP triggers or webhooks (future support)</li><li>Task actions (create, assign, update)</li><li>Account or wallet creation</li><li>Notifications</li></ul></td></tr><tr><td><sub><strong>Execution Controls</strong></sub></td><td><ul><li>Conditional logic</li><li>Branching and parallel execution</li><li>End nodes and pause/resume behavior</li></ul></td></tr><tr><td><sub><strong>Templates</strong></sub></td><td>Start faster using prebuilt workflow templates or create your own. Templates are reusable and save time on repetitive logic.</td></tr></tbody></table>

XYB Workflows are designed for:

* **Operations Leads** who want to reduce manual work and improve reliability
* **Compliance Teams** who need to enforce process-level rules
* **Case Managers** who handle onboarding, KYC, or customer tasks
* **Business Analysts** looking to prototype and validate improvements

Learn more about:

[Building Blocks of a Workflow](/xyb-console/workflow-management/building-blocks-of-a-workflow.md)

[Automation Tutorial](/xyb-console/workflow-management/automation-tutorial-employee-offboarding-handoff.md)

[Payment Workflows](/xyb-platform-1/xyb-payments/payment-workflows-and-automations/payment-workflow-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.xyb.co/xyb-console/workflow-management.md?ask=<question>&goal=<endgoal>
```

`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.