---
title: Workflow Setup
subtitle: Configure your first OrcaPulse workflow correctly
slug: documentation/workflow-setup
---

# Workflow Setup

This guide explains how to configure a workflow in the current OrcaPulse product based on the features that are present in the codebase today. It follows the real workflow builder, the current workflow model, and the validation rules used before activation.

## What workflow setup includes

- Workflow name and description
- Step ordering
- Execution delay
- Day and night mode
- Duplicate lead protection
- Inbound and recall settings
- CRM sync, webhook sync, messaging, and AI call steps
- Workflow simulation before launch

## Create the workflow shell

Start with a clear workflow name, a short purpose, and a narrow launch scope.

- Use a name tied to the real lead source or automation goal.
- Add a useful description so future edits are easier.
- Keep version one focused on one job instead of trying to model every path.

## Choose your step types

The workflow builder currently supports these core step types:

- SMS: Uses an SMS template and a sending number.
- Email: Uses an email template and configured provider.
- WhatsApp: Uses a WhatsApp account and an approved template.
- AI Call: Uses an assistant and a configured phone number.
- Wait: Adds time between actions.
- CRM Sync: Uses a CRM connection and sync-direction configuration.
- Webhook Sync: Uses a webhook integration and webhook direction.

## Configure execution settings

Review the workflow-level settings before activation.

- Execution delay
- Day and night mode
- Start and end hour
- Prevent duplicate leads

These settings matter because they shape execution even before individual step configuration begins.

## Configure inbound and recall behavior

Use inbound and recall settings when your workflow needs more than a simple one-pass execution path.

- Use inbound settings when live incoming traffic should follow a specific workflow behavior.
- Use recall settings when retries or repeat contact logic are part of the design.
- Keep the first launch simple if these paths are not needed yet.

## Connect the required resources

Before activating the workflow, make sure each step has the resources it needs.

- SMS template and number
- Email template and provider
- WhatsApp account and approved template
- AI assistant and phone number
- CRM connection
- Webhook integration

## Build the step order

Keep the first version small and testable.

- Start with one action
- Add waits only where timing matters
- Keep downstream sync steps explicit
- Avoid unnecessary branching in version one
- Name steps clearly so the sequence is readable later
- Duplicate steps only when the repeated path is still easy to understand

## Validate before activation

Activation should only happen after step configuration is complete.

- Check that every required field is filled for every step type.
- Confirm templates, assistants, numbers, CRM connections, and webhooks already exist.
- Run workflow simulation with a realistic lead sample.
- Fix configuration errors before the first live launch.

## Next steps

After workflow setup, continue into testing, execution monitoring, and refinement using live results.