Branching paths
Condition workflow paths on contact fields, tags, or previous step results.
WorkflowsWaits, branches, and run history
Email workflows with guardrails
Design lifecycle sequences with waits, branches, manual approvals, webhook steps, tags, and run history while every message still flows through Sendix delivery controls.
- Manual-run ready
- Waits, branches, and tags
- Webhook and email steps
- Run history for debugging
workflow canvasrun_01HX
Trigger
user.created
Wait
10m
Email
welcome_v2
Branch
plan == pro
Workflow runs
Composable lifecycle flows, never a black box.
Design the graph, then watch each run resolve step by step with delivery state attached.
01
Trigger
Define the trigger
Start from a manual run today and evolve toward event or scheduled triggers as they mature.
02
Steps
Compose steps
Combine email sends, waits, branches, tags, and webhook actions on one canvas.
03
Control
Wait and branch
Schedule pauses and condition paths on contact fields without hiding state from operators.
04
Run history
Inspect each run
Review every run, step result, queued message, and retry state before scaling up.
Controls
Automation you can reason about.
Each block keeps the workflow graph and mail delivery state close enough for teams to debug.
Wait controls
Schedule pauses between steps without hiding state from the operations view.
Webhook steps
Call your app as part of a lifecycle flow and retain full run history.
Delivery native
Workflow emails still use the same domains, queues, templates, and events.
Run state
Every run, inspectable.
Step results, queued messages, and retry state stay visible so operators debug instead of guess.
Read the guiderun_01HX
trigger.manualcomplete
wait.10mscheduled
email.welcomequeued
webhook.crmpending
Guided enablement
Adopt lifecycle automation with the right guardrails.
Automations share the same domains, queues, templates, and events as the rest of Sendix, so workflow emails stay accountable.
FAQ
Questions before you automate a lifecycle.
Short notes for teams evaluating Sendix automations for production sequences.
Are automations production autonomous?
The current posture is guided enablement with manual-run readiness. The model is built to support event and schedule triggers as they mature.
Do workflow emails use templates?
Yes. Automation email steps can point at Sendix templates so versioning and previews stay centralized.
Can I debug a single run?
Yes. Run history is a main surface so teams can inspect step state instead of guessing.
Ready to send your first email?
25,000 emails free every month. No credit card required. Upgrade only when you outgrow the free tier — and we will let you know when that time comes.
Managed SaaS platform · Native SMTP engine · SOC 2 in progress