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

# Overview

***

Workflows define the structured sequence of steps a user follows during identity verification, letting organizations design tailored verification journeys. A journey can include welcome screens, consent forms, document capture, selfie and liveness checks, and authenticity validations.

The **Workflow Builder** makes designing those journeys simple and intuitive: a visual, drag-and-drop interface where administrators build and customize workflows directly from the admin platform. It pairs a **Node Library** of predefined steps with a **Canvas** for arranging and connecting them, plus a workflow header to name, save, preview, and configure each workflow. The result is seamless, compliant, and flexible verification experiences built without backend dependencies.

### Key capabilities

| Capability                                                                | What it does                                                                          |
| ------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
| [No code workflow creation](/workflow-builder/build-a-workflow.md)        | Build workflows by dragging and dropping nodes from the Node Library onto the canvas. |
| [Flexible flow design](/workflow-builder/build-a-workflow.md)             | Connect nodes with handlers and edges to define sequential or conditional paths.      |
| [Node configuration](/workflow-builder/node-library.md)                   | Configure each node's elements, transitions, and settings through the Node Editor.    |
| [Workflow preview](/workflow-builder/customize-preview-and-save.md)       | Simulate the user journey directly from the UI before deploying.                      |
| [Workflow import](/workflow-builder/manage-workflows.md)                  | Import existing workflows via JSON to replicate or migrate across environments.       |
| [Branding customization](/workflow-builder/customize-preview-and-save.md) | Customize header content, footer content, and global CSS.                             |

### Core concepts

The Workflow Builder is a visual canvas for designing verification journeys. You add nodes from the left panel and configure each one as part of the flow. The interface has five primary areas plus the connectors that join nodes.

| Area             | Purpose                                                                                                                                                  |
| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Node Library     | All available workflow components, grouped by category (Pages, Verification steps, Failed Verification handlers, Utilities). Drag nodes onto the canvas. |
| Connection Guide | Visual reference for the handler types used to connect nodes.                                                                                            |
| Canvas           | The workspace where nodes are arranged and connected to define sequential steps and conditional branches.                                                |
| Node Editor      | Configure the selected node's properties, settings, and elements.                                                                                        |
| Workflow Header  | Name and edit the workflow, save, preview, and open additional settings.                                                                                 |

Two elements connect the flow:

* **Connectors** — Dotted lines that represent the transition from one step to the next.
* **Handlers** — Connection points (dots) on each node that define outcomes or paths (for example, Success, Failure, or Error) and connect to subsequent nodes.

#### Connection guide

The Connection Guide is a visual reference for the handler types that connect nodes. Handlers define how a workflow transitions based on user actions or verification outcomes.

| Handler                  | Description                                                                |
| ------------------------ | -------------------------------------------------------------------------- |
| Input                    | Indicates the incoming connection to a node.                               |
| On Next / On Success     | Represents the transition when a step completes successfully.              |
| On Check Resolution Fail | Triggered when the device camera resolution does not meet the requirement. |
| On Fail                  | Represents the path followed when verification fails.                      |
| On Error                 | Triggered when a system or processing error occurs.                        |
| Default                  | The default transition when no specific condition is defined.              |
| Disabled                 | An inactive handler that cannot be used.                                   |

#### Example workflow

A typical verification journey connects a consent/instructions page to document and selfie capture, then routes to an outcome screen based on the result.

```mermaid
flowchart LR
    A["Form<br/>(consent & instructions)"] -->|On Next| B["Photo ID<br/>(scan & OCR)"]
    B -->|On Success| C["Selfie Capture<br/>(liveness)"]
    C -->|On Success| D["Success"]
    C -->|On Fail| E["Failure"]
    C -->|On Error| F["Error"]
```

{% hint style="info" %}
This diagram is an illustrative example using real Workflow Builder nodes and handlers. Your actual journeys can be simpler or more complex, including components.&#x20;
{% endhint %}


---

# 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.1kosmos.com/workflow-builder/overview.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.