Skip to main content

What Is a Workflow Made Of?

Understand the core building blocks that make up an ANVL workflow.

Lauren Baird avatar
Written by Lauren Baird
Updated this week

Primary Role: Workflow Manager
Learning Focus: Learn
Where: Workflow Editor


🎯 Why This Matters

Understanding the basic parts of a workflow makes it easier to design, edit, and troubleshoot workflows without breaking flow or usability.


🧩 The Core Building Blocks

Every workflow is made up of four main components:


📝 1. Questions

Questions are the core content of the workflow.

They define:

  • What information is collected

  • How users respond (yes/no, text, checklist, photos, etc.)

Questions can:

  • Capture data

  • Trigger routing logic

  • Drive Stops or Interventions


🔀 2. Routes

Routes define how users move from one question to the next.

There are two main types:

  • Default routes – the standard path forward

  • Rule-based routes – conditional paths based on responses

Every question must have one Default route.


🟢 3. Nodes

Nodes are special points in the workflow that control start, end, and post-completion behavior.

Common nodes include:

  • Start Node – where the workflow begins

  • End Node – completes the workflow

  • Notes Node – enables Notes after completion

  • Back to Dashboard Node (optional) – returns users to the app while keeping the workflow open

Nodes shape how and when the workflow begins, ends, and is reviewed.


🗂️ 4. Workflow Sections (Categories)

Workflow sections (categories) group questions into logical sections.

They:

  • Help users understand where they are in the workflow

  • Appear as breadcrumbs during completion

  • Organize the completed workflow and print view

Sections affect usability and review, not routing or reporting.


How These Pieces Work Together

  • Questions collect information

  • Routes control flow

  • Nodes manage start, end, and notes

  • Sections organize the experience

All four work together to create a workflow that is usable, testable, and reviewable.

Did this answer your question?