--- updatedAt: 2026-09-24T12:16:19.000Z agentTools: projectIndex: https://docs.sumsub.com/llms.txt --- # Get started with Workflow Builder Use Workflow Builder to set up verification steps no-code. Build custom verification logic with no-code and integrate with Sumsub easily: 1. Navigate to [Workflow Builder](https://cockpit.sumsub.com/checkus#/sdkIntegrations/applicant-workflows/flow) and [set the canvas type](https://docs.sumsub.com/sumsub/docs/get-started-with-workflow-builder#define-flow-type). 2. [Add level steps](https://docs.sumsub.com/sumsub/docs/get-started-with-workflow-builder#add-level-step), [build conditions](https://docs.sumsub.com/sumsub/docs/get-started-with-workflow-builder#build-conditions), [set up review steps](https://docs.sumsub.com/sumsub/docs/get-started-with-workflow-builder#set-up-review-steps), and [configure actions](https://docs.sumsub.com/sumsub/docs/get-started-with-workflow-builder#configure-actions) according to your needs. 3. [Create multiple versions](https://docs.sumsub.com/sumsub/docs/get-started-with-workflow-builder#create-multiple-versions-of-your-workflow) of your flow and test them. 4. [Publish your flow](https://docs.sumsub.com/sumsub/docs/get-started-with-workflow-builder#publish-your-flow-and-go-live) to make it available in production. 5. Set up [WebSDK](https://docs.sumsub.com/sumsub/docs/web-sdk) or [MobileSDK](https://docs.sumsub.com/sumsub/docs/mobile-sdk) integration that will handle the whole verification process. 6. [Review verification results](https://docs.sumsub.com/sumsub/docs/get-started-with-workflow-builder#review-verification-results). # Define flow type With Workflow Builder, you can create flows based on two types of [verification levels](https://docs.sumsub.com/sumsub/docs/configure-verification-levels#configure-verification-steps): **Standard** and **Applicant actions**. Depending on your choice, you'll need to set up your verification flows in the corresponding tabs. To start building a verification flow: 1. Go to [Workflow Builder](https://cockpit.sumsub.com/checkus#/sdkIntegrations/applicant-workflows/flow) and select **Active workflow**. 2. Navigate to either the **Standard** or **Additional check (Action)** tab, depending on the type of your initial step. 3. Go to the **Draft** view. 4. Proceed to [add the level step](https://docs.sumsub.com/sumsub/docs/get-started-with-workflow-builder#add-level-step). # Add level step A level node always goes first and is always required to start your workflow, as it will be responsible for initiating a process of collecting information about your applicants. Without this node, the verification flow will not run. You can map a level node to any **Standard** verification level that obtains necessary information about your applicants, such as, for example: * Country/State * Age * Gender * IP address * Data from applicant documents * Data from Questionnaire * Metadata * Other details: high-risk applicants, large transactions * Internal fraud score results * External databases results * Company type You can also start your verification flow with an **Applicant action** verification level that requires additional verification: * [Liveness check](https://docs.sumsub.com/sumsub/docs/liveness) * [Questionnaire](https://docs.sumsub.com/sumsub/docs/questionnaire) * [Payment method check](https://docs.sumsub.com/sumsub/docs/payment-method-check-advanced) To add a level node: 1. Set up a [verification level](https://docs.sumsub.com/sumsub/docs/verification-levels). 2. In Workflow Builder, navigate to either the **Standard** or **Additional check (Action) **tab, depending on the type of your initial step. The first type fits for general applicant verification; the second type is usually used to initiate additional checks based on suspicious applicant actions. 3. Right-click anywhere on the canvas and select **Level step**. 4. Specify the name of the node and select a level that you have configured at step 1. 5. Click **Choose next level** to continue building your flow by adding such nodes as [Level step](https://docs.sumsub.com/sumsub/docs/get-started-with-workflow-builder#add-level-step), [Condition](https://docs.sumsub.com/sumsub/docs/get-started-with-workflow-builder#build-conditions), [Action](https://docs.sumsub.com/sumsub/docs/get-started-with-workflow-builder#configure-actions), and [Terminal step](https://docs.sumsub.com/sumsub/docs/get-started-with-workflow-builder#assign-terminal-steps). ### Important - While setting up an applicant workflow, you cannot use the same verification level more than once within a single workflow. If a level is already used, it becomes unavailable for selection. To avoid conflicts in your verification logic, structure your workflow using conditional nodes and separate branches. - If two levels are configured in the workflow one after another, the system will transfer both approved and rejected applicants to the next level, resetting the verification state. At the second level, rejected applicants may become approved if they meet this level’s requirements. To prevent this, you can add a [conditional node]() between the levels that checks the applicant’s status and allows only approved applicants to pass through. - All verification levels must use the same [WebSDK version](https://docs.sumsub.com/sumsub/docs/web-sdk). # Build conditions A conditional node is an optional node directing applicants further down the flow, depending on the specified criteria. For example, you may want to ask applicants from the USA and Canada to go through identity verification, and by that check, you obtain information about their age, country, and so on. Then you decide to decline applicants whose age is less than 16, and for the rest cases, you need to additionally direct applicants to different checks, depending on their country. To set up a conditional node: 1. Select whether to approve or reject applicants. 2. Set up a logical condition `IF`, ` IF NOT`, `OR`, `OR NOT`, `IS IN`, and `EQUALS` and add necessary values in accordance with your scenario. For example, you can use [blocklists](https://docs.sumsub.com/sumsub/docs/workflow-builder-best-practises#auto-reject-fraudsters) to form a list of suspicious applicants and auto-reject each of them by defining a condition. 3. Add a new conditional branch for another group of applicants, depending on the obtained information. 4. For every branch, proceed with the next step, which can be: [Level step](https://docs.sumsub.com/sumsub/docs/get-started-with-workflow-builder#add-level-step), [Action](https://docs.sumsub.com/sumsub/docs/get-started-with-workflow-builder#configure-actions), [Terminal step](https://docs.sumsub.com/sumsub/docs/get-started-with-workflow-builder#assign-terminal-steps). ## Condition data types When you set a condition, you can start typing in the value field to search for applicant data or functions, or enter a value manually. An icon next to each item shows its data type: {` `} ## Condition specifics These are implementation details and behaviors to be aware of when configuring Workflow builder conditions. {`
Expand to view additional details on logical conditions, variables, and regular expressions.

Affected feature

Behavior

General expressions

You can use regular expressions to check if a field matches certain conditions. There are some of the expressions that might be useful:

  • .*[0-9].* and .*\d.* allow you to define whether a field contains a single digit number, e.g. 5.
  • .*\d+.* should be used to check if a field contains only digits—123456, but not 12345a.

When using expressions, ensure the following conditions:

  • Use the expressions for matching fields (the contains logic) in the .*\example.* format. The \example expression does not cover the entire field.
  • Code the \ symbol as \\.

IS IN , EQUALS logical conditions

These conditions are both used for comparison:

  • IS IN is used for comparing entities, such as client lists.
  • EQUALS is used for comparing specific values.

poi.validUntil.ageInYears variable

Uses negative values for future expiry dates because the value represents the difference between the current date and the expiry date.

For example, if the current year is 2026, a document expiring in 2056 has a value of approximately -30. Therefore, use the less than or equal condition with the value -30 to match documents with 30+ years of validity remaining.

`} ## Condition logic The same applicant can trigger only one condition branch at a time and will follow that scenario. Therefore, when adding a conditional node, keep the following logic in mind: * **If you create two branches with similar condition settings but different subsequent steps, only the first branch will execute**. Instead of duplicating similar condition branches, add multiple subsequent steps to the same branch. * **If you check multiple different conditions at the same time using separate branches, only one branch will be triggered and its scenario will run**. To evaluate multiple conditions at once, use `AND/OR` operators to create a combined condition within a single branch. Alternatively, for more complex cases, you can use additional conditional nodes to evaluate information step by step and define the next steps accordingly. # Set up review steps You can use the review step node to send applicants for manual review or block them automatically—for example, due to non-compliant personal data—with the final rejection decision. Applicants who got a final rejection will not be allowed to even upload documents. To set up a review step node: 1. Select the type of node, which can be **Final reject** or **Manual review**. 2. Specify the corresponding assignment: * For the final review, choose from the list of [rejection labels](https://docs.sumsub.com/sumsub/docs/receive-and-interpret-results-via-api#final-rejection-labels) as necessary. * In case of manual review, applicants are automatically assigned the **Requires action** status and queued for manual processing by compliance officers. You can also use this functionality to [create Queues](https://docs.sumsub.com/sumsub/docs/case-management#review-queues). Then you will also need to specify the tag you want to add to the applicant when configuring the action. # Configure actions An action node adds certain information to applicant profiles for further filtering. To set up an action node: 1. Add an action type that you want to be performed. You can set the following: * [Tag](https://docs.sumsub.com/sumsub/docs/review-results-in-applicant-profile#assign-tags) — to assign a tag (or several tags) to the applicant. * [Note](https://docs.sumsub.com/sumsub/docs/review-results-in-applicant-profile#manage-notes) — to leave a note in the applicant profile. * [Source key](https://docs.sumsub.com/sumsub/docs/source-keys) — to add or delete the applicant source key and change their level accordingly. * [Case](https://docs.sumsub.com/sumsub/docs/review-cases#create-cases-via-workflow-builder) — to create a case for investigation based on a specific criteria. 2. Proceed with the next step if necessary, or leave as it is for defining the end of the flow. # Transfer Action workflow into Standard workflow You can use the **Transfer node** to move applicants from an **Action **workflow to a **Standard **workflow and continue verification on a selected level. To configure the transfer: 1. In the Dashboard, open [Integrations](https://cockpit.sumsub.com/checkus/sdkIntegrations/levels/individual?limit=100) → **Workflow builder**, and open the **Action Workflow** tab. 2. Right-click anywhere on the canvas and select Transfer node. 3. In the node settings, select the verification level that applicants should be transferred to. 4. Publish the workflow. ### Note - The **Transfer node** cannot be used as a starting point in a workflow. It must be placed after another node and is used to redirect applicants to a **Standard **workflow. The node is terminal, meaning no additional nodes can be added after it. - The transfer is one-way. Applicants cannot return to the previous workflow after the transfer. - Documents submitted for the reset steps become inactive and must be provided again. # Manage Workflow nodes Some convenient management options are available for Workflow Builder nodes: * **Select, copy, and paste**: Choose any nodes and transfer their copies into another Workflow builder canvas. For example, you can reuse the required nodes across multiple keys or copy [workflow examples](https://cockpit.sumsub.com/checkus/sdkIntegrations/workflows/examples) to your own canvas. * **Organize**: Select nodes and place them in a structured, straightforward order with a single click. The following table shows how you can manage nodes using shortcuts and canvas buttons: | Action | Instructions | | :------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Select | | | Copy | | | Paste | | | Organize | Select the required sequence of nodes and click **Organize** above the selected area. | ### Note After pasting, some nodes may require additional configuration. For example, if you move nodes to another key, you might need to update the verification levels and tags used. ### Tip If you are a [Reusable KYC](https://docs.sumsub.com/sumsub/docs/reusable-kyc) partner, you can copy nodes, save them to a `.txt` file, and share it with other partners so they can paste the nodes directly into their Workflow builder canvas. # Review flow history Every time you make changes to your flow and publish it, the previous state is saved as an archived version, allowing you to revert to any of the available versions at any time. To see the available versions, in the top-right corner, open the menu and select **Version history**. # Create multiple versions of your workflow Before putting your flow into operation, you may want to improve it or create one or several alternatives. To copy your flow and experiment with changing different steps: 1. Click **Copy to Test Workflow**. 2. Switch to the [Test Workflow](https://cockpit.sumsub.com/checkus#/sdkIntegrations/applicant-workflows/test-flow) tab. 3. Change your flow as needed. 4. Click **Run flow**. 5. Click **Generate** to get the permalink to your flow. 6. Pass verification by checking every step. 7. Click **Copy to Active Workflow** to replace your previous flow. 8. Return to the [Active Workflow](https://cockpit.sumsub.com/checkus#/sdkIntegrations/applicant-workflows/flow) tab and proceed with publishing your flow. # Publish your flow and go live When the whole logic is built and tested, do not forget to save and publish your draft. The created flow will then be shown in the **Published** view. To initiate your flow from the Dashboard, click **Run** and [generate a permalink](https://docs.sumsub.com/sumsub/docs/verification-links) for passing verification in the SDK. # Review verification results Once the check is performed, you will receive the [applicantReviewed](https://docs.sumsub.com/sumsub/docs/user-verification-webhooks#applicantreviewed) webhook with the verification status. This webhook is triggered in the following cases: * Applicant completes the flow (either receives a final approval or a final rejection at any stage) * Applicant receives the [Resubmission requested](https://docs.sumsub.com/sumsub/docs/applicant-statuses) status while completing the flow To review results via applicant profiles, go to the [Applicants](https://cockpit.sumsub.com/checkus#/applicants/individual?limit=10\&page=0) page, select an applicant, and check on **Summary**, which is a comprehensive report that includes the applicant data, check results, and uploaded documents. {`
`}