Unsendbox logo
Get started
← Return to root

Workflows

Build a multi-step campaign, enroll contacts, and follow each step from the dashboard, an MCP client, or the Unsendbox CLI.

Workflow, campaign, sequence

These are the same object. The dashboard page is titled Sequences, the models and the API call it a sequence, and the CLI command is sequence. A workflow is multi-step and enrolls contacts over time. A broadcast is a single campaign run that sends one template revision to a saved audience in one pass. Each workflow step references a published template revision, and an active sequence pins those revisions so a change to the template does not alter contacts already moving through it.

Build and run a workflow

Dashboard routes: /dashboard/sequences and /dashboard/sequences/$sequenceId.

  1. 01Open Sequences to see every sequence with its status.
  2. 02Create a sequence, which starts in draft.
  3. 03Open the sequence to see its workflow graph, the enrollments table, and the stats rail.
  4. 04Use Enroll contacts to bulk-enroll an audience into the sequence.
  5. 05Activate the sequence to start executing steps, and pause it when you need to stop new work.
  6. 06Follow delivery from the stats rail, which counts enrollments by Active, Paused, Completed, and Bounced, and engagement by Sent, Opened, and Clicked.

Sequence statuses

Lifecycle of a sequence.

  • draftBeing built. Steps do not execute.
  • activeExecuting steps for enrolled contacts.
  • pausedExecution is halted and can be resumed.
  • archivedRetired and no longer runnable.

Trigger types

How contacts arrive in a sequence.

  • manualContacts are enrolled by hand or in bulk from the dashboard.
  • apiContacts are enrolled through the API or the CLI.
  • eventContacts are enrolled in response to an ingested workflow event.

Enrollment statuses

Where one contact stands inside a sequence.

  • activeMoving through the sequence.
  • pausedHeld in place and resumable.
  • completedReached the end of the sequence.
  • unsubscribedOpted out, so no further steps run.
  • bouncedDelivery bounced, so the contact stops receiving steps.
  • errorStopped on an unrecoverable error.

Step execution statuses

Whether a step ran for one enrollment, and what its effect did.

  • pendingExecution status: the step is waiting to run.
  • executedExecution status: the step ran.
  • skippedExecution status: the step was skipped.
  • failedExecution status: the step failed.
  • queuedEffect status: the send was queued.
  • acceptedEffect status: the provider accepted the send.