All tutorials

Azimea Academy · Full walkthrough

Flows: build an automation without activating it

Create a draft flow with an explicit source, audience, waiting step and email. Review the saved structure and its requirements without enrolling contacts or activating delivery.

2:54Audio: EnglishCaptions: English
Free to watch. No account needed.

What you will see

  • Create a draft flow with an explicit source, audience, waiting step and email.
  • Review the saved structure and its requirements without enrolling contacts or activating delivery.

Transcript

An automation connects a starting event or decision with a sequence of steps.

We will build a small follow-up draft, review its audience, add a delay and an email, then organize the result with a tag.

The workflow will remain unpublished throughout this demonstration.

The trigger defines how people enter the workflow. Run now provides an explicit starting decision, while schedules and events serve

other use cases. We will choose the manual trigger for this example and give the workflow a name that describes its purpose.

Creating the draft opens the canvas and its step library. The diagram makes the order of the workflow visible, while the inspector

holds the settings for the selected step. We can build and review the sequence before publishing a live version.

Selecting the starting node reveals the manual trigger and its current publication state.

A draft cannot be started as a live workflow. This separation gives us room to review the audience and the actions before any contact

is allowed to enter the sequence.

An audience step defines who is considered when this manually started workflow runs.

Contacts, saved segments, and an uploaded list support different selection needs.

Review that choice deliberately alongside sending permission, rather than assuming that every stored contact should receive the same

follow-up.

A delay controls when the next step becomes available to each contact.

We will use a one-day duration here. The other wait modes can align the sequence with a particular time or an event, depending on what

the follow-up is meant to achieve.

The email step links to a saved template. We will search for the demonstration welcome email and select it for this path.

The live workflow uses a copy of the content at publication, so later template edits need a deliberate publication review before they

reach live messages.

A tag records a useful label as the contact reaches this point in the workflow.

We will use a name that relates to the follow-up. Keep labels understandable to the team because they can later support organization

and audience selection beyond this single diagram.

The complete path should read as a coherent sequence, a trigger, an audience, a delay, and the intended actions.

Review outstanding issues and sender requirements before publishing.

We will keep this demonstration as a draft without starting a live run or sending a message.

The follow-up draft now demonstrates the structure and settings of a small automation.

Before using the sequence with a real audience, review its entry criteria, timing, email content, and exit behavior together.

Publish only after those decisions match the experience you intend to create.