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

# Workflows

> Automate multi-step messaging journeys triggered by user behavior.

Workflows automate behavior-based communication using queue-driven execution.

For the full MailerPath workflow library, see [Workflow Library by State](/documentation/core-functionalities/workflows/predefined-workflows-by-state).

## Ownership and customization model

MailerPath designs and controls workflow logic, trigger architecture, execution flow, and safety rules across the workflow catalog.

You can relax and let MailerPath run these workflows for you end to end. If you want, you can still tailor approved parameters and message content while MailerPath keeps the core workflow structure managed.

Client-configurable areas:

* Timing overrides (for example delay and send-time mode)
* Priority override score
* Workflow email templates and copy

## How Execution Works

1. Trigger conditions place items in workflow\_queue.
2. Worker claims due queued rows safely.
3. Execution records are created per queue item.
4. Email action is rendered and sent.
5. Queue and execution status are finalized.

Current behavior in phase one:

* Primary action is email send execution.
* Worker runs in-process with polling.
* Row-level locking prevents duplicate claims in multi-instance setups.

## Statuses You Will See

Workflow queue:

* queued
* processing
* completed
* expired
* failed

Workflow execution:

* queued
* executing
* completed
* failed
* cancelled
* skipped

## Skip And Failure Scenarios

Typical skip reasons:

* contact has no email
* contact is unsubscribed

Typical failure reasons:

* missing default template
* provider not configured
* provider send errors

## Operational Best Practices

1. Keep templates workflow-safe and variable-safe.
2. Validate sender provider config before enabling high-volume triggers.
3. Monitor failed queue items and retry trends.
4. Use event quality checks to reduce noisy triggers.