The canvas: a trigger at the top, steps beneath it

The act of building one, on screen. Where the trigger sits, how steps chain under it, and what a branch looks like before you turn it on.

Watch

A workflow being built: trigger, steps and a branch

What it does

What is on the canvas

The trigger sits at the top

One event starts the workflow and it is the first thing on the canvas, so you can always see what sets it running.

Steps chain downwards in order

Each step sits under the last. Reading top to bottom tells you what happens and when, without opening anything.

A branch splits the path visibly

A condition draws two routes on the canvas. You can see which customers go which way rather than working it out.

How it works

Building one

  1. Pick the trigger. The canvas opens with it in place.
  2. Add steps under it: a message, a wait, a tag, a task.
  3. Add a branch where customers should be treated differently.
  4. Leave it off until you have read it top to bottom, then switch it on.

Worth knowing

Worth knowing

  • A canvas that grows past a screen gets hard to read. Two short workflows beat one long one.
  • It is easier to build than to test. There is no substitute for running it on yourself first.
  • Switching one on affects everyone who meets the trigger from that moment. Check the trigger before the steps.

Related

Related

Workflow automation
What a workflow is, before you open the canvas.

The work you do twice
Working out which one to build first.

Email campaigns
When the thing you want is one send, not a sequence.

Build the shortest one

Log in, open the canvas, and build one trigger with one message under it. Run it on yourself.

Log in See pricing at LaunchLocal