Journey
A Journey is a reusable workflow that defines the structure, sequence, and logic for automating multi-step processes across departments. Created and managed by admins, a journey includes phases and activities. Examples: New Employee Onboarding, Employee Exit, Department Transfer, and so on.
Journey Request
A Journey Request is an individual execution instance of a Journey. Each request is associated with a specific target user. Journey Owners can track the Journey request throughout its lifecycle, monitoring progress, assigning tasks, and addressing bottlenecks. A Journey Request represents a live, in-motion workflow instance.
Journey Template
Journey Templates are pre-built configurations to support common employee transitions and cross-functional processes. They serve as a starting point for admins, allowing them to reuse existing components instead of building each Journey from scratch.
Phase
A phase is logical grouping of activities that break a Journey into manageable stages based on timelines or triggers. They improve clarity and can be executed sequentially or conditionally. As an organization, you can define custom phases in your Journeys to align with your unique processes and workflows.
Activity
An Activity is an individual task or action, a collection of which make up each phase of a Journey. They represent the actual work that needs to be completed and can be assigned to specific stakeholders. Journeys support different types of activities, including tickets, simple tasks, form-filling tasks, and email activities.
Conditions
Conditions allow you to tailor Journeys for different employee cohorts by dynamically including or skipping phases and activities. You can define conditions based on attributes like location, department, or role—for example, assigning different tasks for remote vs. on-site employees or for tech vs. non-tech roles.
Triggers
Triggers determine when a phase or activity should begin, based on events like the completion of a previous phase or a specific time relative to Journey attributes—such as a joining date. They help configure complex workflows, ensuring alignment with your organization's processes.
Stakeholder
Stakeholders are the individuals responsible for completing specific activities within a Journey. They include dynamically assigned individuals based on the context of the Journey—for example, a new hire, reporting manager, buddy, and so on.
