Building a Campaign Workflow

From Target Audience to Chained Activities

Go to Marketing Automation → Create.

Campaign Setup

1. Target Model – which type of record this campaign runs against (e.g. Contacts, Leads).
2. Filter – a domain deciding which records are eligible to enter (e.g. only contacts tagged "Newsletter" who haven't purchased yet).
3. Unicity – optionally restrict so the same contact can't enter the same campaign twice.

Adding Activities

Each activity is either a Mailing (send an email template) or a Server Action (any automated backend action — e.g. add a tag, create an activity for a salesperson). Every activity after the first has:

• Trigger – what causes this step to fire: beginning of workflow, a fixed time after another activity, or a response to a previous mailing (opened / not opened / clicked / not clicked / replied / not replied / bounced).
• Send After – the delay (hours/days/weeks/months) after the trigger condition is met.

This is what creates branching: two activities can both be children of the same mailing, one triggered on "Mail: opened" and the other on "Mail: not opened" — each participant only proceeds down the branch matching what they actually did.

Example Workflow

1. Activity 1 (trigger: beginning of workflow) – Welcome email, sent immediately.
2. Activity 2 (trigger: Mail opened on Activity 1, after 2 days) – Product highlight email.
3. Activity 3 (trigger: Mail not opened on Activity 1, after 3 days) – A re-send with a different subject line.
4. Activity 4 (trigger: Mail clicked on Activity 2, after 1 day) – Notify the salesperson via server action — this lead is engaged.

Validity Duration

Set how long an activity's trigger condition stays "open" for evaluation (e.g. "not opened after 3 days" needs a window to actually wait those 3 days before deciding not-opened is true) — this is handled automatically per activity, but is worth understanding when a workflow seems to be waiting longer than expected.