On this page

Jump to any section using the links below

Workflows in Hubhus are created by combining automations, action listeners, statuses, and communication templates into clear, multi-step processes. This article introduces the fundamentals of designing structured workflows that guide leads from start to finish.

Workflow design patterns

A workflow is a sequence of steps that a lead goes through.
Typical workflow patterns in Hubhus include:

1. Linear workflows

A simple progression such as:
New → Contacted → Quote Sent → Follow-Up → Closed

Used in:

• Sales funnels

• Consultation flows

• Support processes

2. Branching workflows

Different paths depending on select-field values, conditions, or customer choices.

Examples:

• Commercial vs. private

• High-priority vs. normal

• Region or product type

• Passed vs. failed checklist

3. Event-driven workflows

Steps triggered by actions such as:

• Booking created

• File uploaded

• Address updated

• Form submitted

Useful for:

• Service visits

• Inspection tasks

• Coordinated field operations

4. Mixed workflows

Combining status steps, field logic, and time delays for more advanced flows.

Chaining automation rules

Automations can be connected to form multi-step sequences.

A chained workflow typically looks like:

1. Status changes → fire automation A

2. Automation A sends email → waits → updates field

3. Field change triggers automation B

4. Automation B performs next step

5. And so on…

Automation chaining is essential for:

• Follow-up sequences

• Staged customer communication

• Document requests

• Multi-step service processes

• Automated handovers between teams

Make sure each automation:

• Has clear conditions

• Only fires when needed

• Has the correct “Max. fires per order” setting

Email sequences

Email sequences are built using:

• Automations

• Delays

• Conditions (@if logic)

• Status or field changes

Common patterns:

1. Multi-step nurturing sequence

• Email 1: Confirmation

• Wait 24h

• Email 2: Information / preparation

• Wait 48h

• Email 3: Final reminder

2. Pre-visit communication

• Booking created → send confirmation

• Wait a set time → send preparation instructions

• Day before event → send reminder SMS

3. Post-visit follow-up

• Event completed → send satisfaction message

• File uploaded → send report

• Wait → send invoice link

Sequences ensure consistency and reduce manual workload.

Status-based workflows

Statuses are central to workflow design.
They represent where a lead is in the process and determine what should happen next.

Status-driven workflows often include:

• Automations that fire when status becomes X

• Notifications when status changes

• Required fields that unlock the next step

• Views filtered by status

• Pipelines that provide visual structure

Examples:

• When status changes to Quote Sent → start follow-up automation

• When status changes to Awaiting Documents → send upload page

• When status changes to Completed → trigger closing actions

Statuses keep workflows organized and predictable.

Testing and debugging workflows

Testing is a crucial part of building workflows.

1. Use a dedicated test lead

Update fields, trigger statuses, and create bookings to observe workflow behavior.

2. Check automation history

Inside the lead’s History, you can see:

• Which automations fired

• What messages were sent

• Delays that are pending

• Previous executions that might block triggers

• Action listener activity

3. Review “Max. fires per order”

If an automation only fires once, this setting is often the reason.

4. Use the editor test tools

• Press CTRL+K (Windows) or CMD+K (Mac) to search placeholders

• Preview content inside the editor

• Check field API names

• Verify @if/@else logic

5. Test booking and event workflows

If bookings trigger your workflow, create test events and verify:

• Availability logic

• Event metadata

• Field updates

• Status transitions

Learning outcome

After reading this, you should understand:

• The main workflow design patterns in Hubhus

• How to chain automations together

• How to design email sequences

• How status changes drive process flow

• How to properly test and debug multi-step workflows

Related articles

Understanding action listeners
What is automation in Hubhus?
What is the Hubhus API?
How does the calendar system work?
Understanding booking forms