Workflow builder

A visual editor for designing identity flows without code.

Instead of asking engineers to write code, a risk or product team drags steps onto a canvas, connects them, and sets what happens at each decision.

A no-code canvas for composing verification steps, branches, and decision outcomes into deployable flows. A branch is a point where the flow splits depending on a result, and a decision outcome is the final result, such as approve, decline, or review.

A workflow builder typically offers several building blocks:

• Steps, such as document capture, selfie, liveness check, and data checks.
• Conditions, such as sending a case down a different path if a score is low.
• Outcomes, such as approve, decline, or send to manual review.
• Settings, such as thresholds and which providers to call.

A team typically uses it like this:

1. They design the flow on the canvas.
2. They test it in a safe environment, called a sandbox, with fake data.
3. They review and approve the change.
4. They deploy it, and the change takes effect without a software release.

Good tools add controls around the changes:

• Version history, so a team can compare and roll back changes.
• Approvals, so a second person reviews important changes.
• Audit records, so the company can show who changed what and when.

A workflow builder sits next to terms that are easy to mix up:

• Orchestration is the runtime that executes the flows the builder creates.
• Rules engine applies if-then logic, which the builder lets teams configure visually.
• Decisioning engine produces the approve, decline, or review outcome at the end of the flow.