Why Workflows Replaced Campaigns and Triggers

Older versions of the platform split automation across two tools: Triggers, which reacted to events, and Campaigns, which ran timed sequences. Workflows merge both into one builder, and the older tools are retired. If you inherited an old setup or find tutorials that mention them, this explains how things map across.

What changed

• You can no longer create new Campaigns or Triggers, and they are no longer supported.
• The Campaigns and Triggers tabs are gone from the navigation. Everything lives under Automation > Workflows.
• Anything a Campaign did, such as timed emails and texts, a Workflow can do with a trigger followed by Wait and Send actions.

Why Workflows are better

• One builder: the start event and the sequence of steps sit together on one canvas.
• Branching: If/Else conditions let you personalize paths by tag, field, source, or reply.
• Visibility: each contact has an execution log, so you can see what happened and why.
• Testing: you can run a test contact through the flow before publishing.
• More building blocks: math, date formatting, webhooks, code, and AI steps are available only here.

Workflows also cover events the old tools never did, including order and payment events, opportunity changes, notes, and media events.

Rebuilding an old automation

1. Create a workflow and add the trigger that matches the old Trigger's event.
2. Add filters to narrow it the same way.
3. Add the actions the Campaign used, in order, using Wait steps for the delays.
4. Use Add to Workflow if you want contacts flowing between several workflows.
5. Test, then publish and switch the old setup off.

If you still see Campaign references

Treat instructions that tell you to "add to campaign" as "add to workflow", and the Add to Campaign bulk action as the Add to Workflow bulk action.

Good to know: Rebuild one automation at a time and run both versions side by side briefly, but make sure contacts can't receive duplicate messages from each.