Get started

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 and go to the Draft view to edit the flow.
  2. Add level steps, build conditions, assign terminal steps, and configure actions according to your needs.
  3. Publish your flow to make it available in production.
  4. Set up WebSDK or MobileSDK integration that will handle the whole verification process.
  5. Review verification results.

πŸ“˜

Note

While setting up an applicant workflow, avoid using the same verification level twice. Instead, to prevent your verification logic from conflicts, create separate flows.

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

To add a level node:

  1. Set up a verification level.
  2. Right-click anywhere on the canvas and select Level step.
  3. Specify the name of the node and select a level that you have configured at step 1.
  4. Click Choose next level to continue building your flow by adding such nodes as Level step, Condition, Action, and Terminal step.

🚧

Important

All verification levels must use the same WebSDK version.

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 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 decline or approve applicants. You can also use both at the same time.
  2. Set up a logical condition IF, IF NOT, OR, OR NOT and add necessary values in accordance with your scenario. For example, you can use blocklists 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 the Level step, Action, and Terminal step.

Assign terminal steps

A terminal step node can direct applicants to the manual review or block them automatically with the final rejection decision. Applicants may be terminated due to non-compliant personal data. Applicants who got a final rejection will not be allowed to even upload documents.

To set up a terminal node:

  1. Select the type of the terminal step, which can be Final reject or Manual review.
  2. Specify the corresponding assignment:
    1. For the final review, select a rejection tag.
    2. In case of manual review, select a moderator who will conduct the review.

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:
    1. Tag β€” to assign a tag (or several tags) to the applicant.
    2. Note β€” to leave a note in the applicant profile.
    3. Risk level β€” to set a risk level.
  2. Proceed with the next step if necessary or leave as it is for defining the end of the flow.

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, click the kebab menu and select Version history.

Publish your flow and go live

When the whole logic is built and tested, don’t 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 for passing verification in SDK.

Review verification results

Once the check is performed, you'll receive a webhook with the verification status.

To review results via applicant profiles, go to the Applicants page, select an applicant, and check on Summary, which is a comprehensive report that includes applicant data, checks results, and uploaded documents.