Create an automated lifecycle workflow
Build a visible journey from a customer event to waits, conditions, and approved channel actions.
See it in Leado
What you’ll achieve
- An approved lifecycle journey with a verified entry event, deliberate timing, consent-aware channel actions, and observable run states.
Follow the workflow
-
1
Open Actions → Workflows
Create a workflow and give it a name tied to its business purpose.
-
2
Choose the trigger
Select the customer or commerce event that should start the journey, such as a product added to cart.
-
3
Add timing and conditions
Use waits and branch rules to prevent messages from arriving too quickly or after the customer has already converted. Define stop conditions and whether repeated qualifying events should create another journey.
-
4
Add channel actions
Insert email, SMS, web push, or onsite actions supported by the connected workspace. Use saved assets where practical.
-
5
Review every path
Check entry criteria, consent, stop conditions, destinations, empty branches, and the total journey duration.
-
6
Test before activation
Keep the workflow inactive while validating a traceable event and every linked asset. After activation, use workflow run detail to review entry, current step, branch, delivery, completion, and failure states.
Verify your work
- A traceable test event satisfies the trigger exactly once
- Every branch has an intentional action, wait, completion, or stop outcome
- Workflow run detail records the expected step sequence without an external send during draft testing
If something doesn’t look right
No run starts
Verify the workflow is active, the event belongs to the selected workspace, and trigger conditions match its fields.
A contact enters repeatedly
Inspect re-entry rules, duplicate source events, and conversion stop conditions.
A step fails
Open the run detail and resolve consent, sender, destination, linked-draft, or provider readiness before retrying.
Limitations and safeguards
Automation depends on timely source events, usable identity, channel consent, and configured providers; a workflow cannot recover activity the source never recorded.