Building workflows in Hubhus

Modified on Tue, 5 May at 11:04 AM

Building workflows in Hubhus

A workflow in Hubhus is the combination of statuses, automations, and communication templates that guide a lead from first contact to final outcome. Build it once and every lead follows the same reliable path — confirmations go out, reminders fire on time, and nothing falls through the cracks.

TL;DR

Design your status pipeline first. Then add automations that fire on each status change. Chain automations for multi-step sequences. Test on a dedicated test lead and check History to see what fired and when.

Build your first workflow in 5 steps

1

Map your status pipeline — define each step the lead should pass through (e.g. New → Contacted → Scheduled → Completed → Won)

2

Create automations that fire when a lead enters each status — send a confirmation, assign a person, or update a field

3

Add delays between actions for follow-up sequences (e.g. send confirmation → wait 24h → send preparation email → wait until day before → send reminder SMS)

4

Test on a dedicated test lead — trigger status changes, create bookings, and verify each automation fires correctly

5

Open the lead's History tab to see which automations fired, what was sent, and what's pending — the ultimate debugging tool

Automations: Campaign settings → Automations  ·  Statuses: Campaign settings → Statuses  ·  Test history: Open lead → History tab
Read more

Workflow design patterns

  • Linear — simple progression: New → Contacted → Quote Sent → Closed. Good for sales funnels and support.
  • Branching — different paths based on select-field values (e.g. commercial vs private, region, product type).
  • Event-driven — steps triggered by booking created, file uploaded, form submitted. Good for service visits.
  • Mixed — combines status steps, field logic, and delays for advanced multi-phase processes.

Common email sequence patterns

  • Pre-visit: Booking created → send confirmation → wait → send preparation instructions → day before → send SMS reminder
  • Post-visit: Event completed → send satisfaction message → file uploaded → send report → wait → send invoice link
  • Nurturing: Email 1 → wait 24h → Email 2 → wait 48h → Email 3 (final)

Debugging checklist

  • Is the automation active? Check it's enabled, not paused.
  • Has "Max. fires per order" already been reached for this lead?
  • Did the lead enter the trigger state after the automation was created? (Automations don't fire retroactively.)
  • Are filters too narrow? Check that the lead actually meets all filter conditions.
  • Check the lead's History tab — it shows every automation that fired and every pending delay.

Common searches

workflow setup • build workflow • automation sequence • email sequence • status driven • chained automations • test automation

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article