> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zenoo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Build Your First Flow

> Create a verification flow from scratch in Zenoo Studio — add check nodes, configure them, test with sample data, and view results.

# Build Your First Flow

This guide walks you through creating a basic verification flow in Zenoo Studio. By the end, you will have a working flow that verifies a person's identity, screens them against sanctions lists, and returns a result.

## What you'll learn

* How to create a new project and flow in Studio
* How to add and configure check nodes in the visual builder
* How to connect nodes to build a verification sequence
* How to test your flow with sample data
* How to read the results

## Before you start

Make sure you have:

* A Zenoo Studio account with admin or editor permissions
* At least one verification provider connected (see [Connect Providers](/guides/studio/connect-providers))
* Access to the staging environment for testing

## Create your flow

<Steps>
  <Step title="Create a new project">
    From the Studio dashboard, click **New Project**. Give it a name (e.g., "Customer Onboarding") and select the project type — **Person Verification** for KYC or **Company Verification** for KYB.

    Each project acts as a container for related flows. You might have one project per product line or customer segment.
  </Step>

  <Step title="Open the flow builder">
    Inside your new project, click **Create Flow**. The visual flow builder opens with a blank canvas and a **Start** node already placed.

    The flow builder has three areas:

    * **Canvas** (center) — where you arrange and connect nodes
    * **Node palette** (left sidebar) — available check types you can drag onto the canvas
    * **Configuration panel** (right sidebar) — settings for the selected node
  </Step>

  <Step title="Add an identity verification node">
    From the node palette, drag **Identity Verification** onto the canvas. Connect it to the **Start** node by dragging from the Start output port to the Identity input port.

    Click the node to open its configuration:

    * **Provider** — select your identity verification provider
    * **Document types accepted** — choose which ID documents to accept (passport, national ID, driving license)
    * **Liveness check** — toggle on to require a selfie with liveness detection
  </Step>

  <Step title="Add a screening node">
    Drag a **Screening** node onto the canvas and connect it after the Identity Verification node.

    Configure the screening node:

    * **Provider** — select your screening provider (e.g., WorldCheck)
    * **Databases** — select PEP, Sanctions, and Adverse Media
    * **Match threshold** — set the minimum match score to flag (e.g., 80%)

    <Tip>
      Start with a lower threshold (70-80%) during testing to see more matches. You can tighten it before going live.
    </Tip>
  </Step>

  <Step title="Add a decision node">
    Drag a **Decision** node after the screening node. This is where the flow determines the outcome.

    The decision node evaluates all upstream check results:

    * **All checks pass, no screening hits** — auto-approve
    * **Screening hits found** — route to Case Management for manual review
    * **Check failures** — route to Case Management or reject automatically
  </Step>

  <Step title="Connect the end nodes">
    Add **Approved** and **Review Required** end nodes. Connect the Decision node's outputs to the appropriate end nodes.

    Your flow should now look like: Start, Identity Verification, Screening, Decision, with branches to Approved and Review Required.
  </Step>

  <Step title="Save and test">
    Click **Save** in the top toolbar. Then click **Test Flow** to open the test runner.

    Enter sample data:

    * **First name** and **Last name**
    * **Date of birth**
    * **Country**

    Click **Run Test**. Studio executes the flow using your staging provider credentials and displays the results in real time.
  </Step>

  <Step title="Review results">
    The test runner shows each node's result:

    * A green checkmark for nodes that passed
    * A yellow warning for nodes that flagged issues (screening hits)
    * A red cross for nodes that failed

    Click any node to see its detailed output — identity match score, screening hit details, document authenticity results.
  </Step>
</Steps>

## What happens when issues are found?

When a flow routes someone to "Review Required," Zenoo automatically creates a **case** in Case Management. The case includes:

* The person's details as a case entity
* All check results as required checks
* Any screening hits as alerts

Your compliance team picks up the case from there. See [How Do Cases Work?](/guides/case-management/understand-cases) for details.

## What's next?

<Columns cols={2}>
  <Card title="Verify a Company" icon="building" href="/guides/studio/verify-a-company">
    Build a KYB flow with registry checks, director extraction, and multi-entity screening.
  </Card>

  <Card title="Screen for Sanctions" icon="shield-halved" href="/guides/studio/screen-for-sanctions">
    Deep dive into screening configuration — databases, thresholds, and interpreting match results.
  </Card>

  <Card title="Connect Providers" icon="plug" href="/guides/studio/connect-providers">
    Add and configure external verification providers.
  </Card>

  <Card title="Go-Live Checklist" icon="clipboard-check" href="/guides/studio/go-live-checklist">
    Make sure everything is production-ready before launch.
  </Card>
</Columns>