How do I automate actions based on status changes?
This article explains how to set up status-based automations and how to control what happens when a lead reaches a specific status.
On this page
Jump to any section using the links below
Automating actions when a status changes
Status changes are one of the most powerful automation triggers in Hubhus. When a lead moves from one stage to another — for example New → Contacted or Quote sent → Accepted — you can automatically trigger emails, assign a user, update fields, or perform multi-step workflows.
This article explains how to set up status-based automations and how to control what happens when a lead reaches a specific status.
1. Using status-based automation triggers
Table of Contents
To create an automation that runs when a status changes:
Open the relevant campaign
Go to Automations
Click New automation
Set the trigger type to “When status changes”
Select one or more statuses that should activate the rule
You can trigger on:
A single status (e.g., When status becomes “Contacted”)
Any of several statuses (e.g., “Quote sent” OR “Reminder needed”)
Leaving a status (detecting movement out of a stage)
Status triggers run immediately when the status is updated.
2. Building multi-step workflows
Status changes often represent a major step in a customer journey. Automations allow you to chain actions to build multi-step flows.
Example workflow when status becomes “Quote sent”:
Wait 5 minutes
Send the customer a confirmation email
Update a field (e.g., “follow_up_date = today + 3 days”)
After 3 days, if no response → send reminder
Assign lead to correct team or user
Notify internal staff via email or Hubhus message
You can add as many steps as needed.
3. Adding conditional logic (Optional but powerful)
You can add conditions inside an automation to run actions only in certain situations.
Examples:
Only send email if
%assigned_person_email%existsOnly run if a select field has a specific value
Only continue if the customer has no booked events
Only run if a custom JSON field contains items
Only notify staff if the lead is from specific region
This prevents unwanted triggers and ensures the workflow reacts only when appropriate.
4. Status change notifications
Hubhus automations are ideal for internal notifications — especially when a lead needs attention immediately after a status update.
Typical examples:
Notify a salesperson when a lead becomes “Ready for quote”
Send internal message when “Customer accepted offer”
Alert support when status becomes “Waiting for documents”
Notify manager when a lead is moved to a closing stage
Notifications can be sent via:
Email
SMS
Internal “Message” action
Updates to fields for dashboard filters
5. Best practices
✔ Name statuses clearly so automations are easy to understand
✔ Keep “Max. fires per order” higher if the same status may reoccur
✔ Avoid sending multiple emails if users often toggle statuses
✔ Use conditions to prevent accidental triggers
✔ Always test with a dummy lead before going live
✔ Use delays to avoid sending emails immediately after noisy updates
Summary
Status-based automations let you trigger workflows exactly when a lead reaches an important stage.
You can:
Trigger emails
Assign users
Update fields
Run multi-step workflows with delays
Send internal notifications
Build structured processes around your lead pipeline
This is one of the most efficient ways to automate your customer journey in Hubhus.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article