---
title: "Build a Deploy Flow"
description: "Connect lead events, waits, calls, validation rules and follow-up messages."
url: "https://documentation.verbatik.com/deploy/flows/"
---

# Build a Deploy Flow

Connect lead events, waits, calls, validation rules and follow-up messages.

**Flows** in the Deploy section coordinate actions around contacts and calls. They are separate from an agent’s **Conversation Flow**, which controls the dialogue inside one call.

## Create a Flow

1. Open **Flows**, choose a template or start a blank draft, and name the workflow.
2. Select each step on the visual canvas to edit **Node settings**. Use the outline when navigating a larger canvas.
3. Configure the trigger in **Start when**: a contact is created, a segment is entered, a webhook arrives or manual enrollment occurs. Add a source filter when the workflow should listen only to a particular form/source.
4. Connect the outcomes of each step. Give failure, unknown, denied-consent and timeout branches an explicit destination.
5. In **Flow settings**, set timezone, permitted calling hours/days, contact re-entry policy, cooldown and maximum run duration.
6. Choose **Save draft**, run **Test flow**, review validation issues, then **Publish**. Later edits remain draft changes until **Publish changes**.

## Available steps

| Step | Configure |
| --- | --- |
| Trigger | Event, source and segment rules |
| Delay | Wait in seconds |
| Condition | All/any rules against contact/event/outcome fields |
| Call | Published voice agent, source number, task, call wait and analysis wait |
| SMS | Messaging source number and message with approved variables |
| Wait for event | Callback/reply event and timeout |
| Update contact | Add/remove tags |
| End | Completion label |

A ten-second delay schedules the next eligible time. Calling windows, worker availability, account gates and capacity can postpone execution; it is not a guaranteed ten-second dial SLA.

## Publish and enroll

Complete resource choices on every call/SMS step. Use **Enroll a contact** only after the published Flow is active. For a form, save the Flow and use its generated webhook configuration; keep the webhook secret on your own server. Changing a published Flow creates a new version; active runs keep their recorded version.

The test simulation previews branching without certifying real carrier delivery. Production call/SMS steps still require their services to be enabled, valid sender/source resources and the relevant consent. Current production outbound/SMS gates must be activated before these actions can run.

## Operate

Inspect runs and steps for pending, waiting, completed, blocked, failed, cancelled or uncertain results. Resolve the blocked reason rather than repeatedly reenrolling the same person. Preserve completed-action receipts when recovering a run; a completed appointment or SMS must not be repeated because a later step failed.