How do I automate actions based on status changes?
Status changes are one of the most powerful automation triggers in Hubhus. When a lead moves to a new stage — New → Contacted, Quote sent → Accepted — you can automatically send emails, update fields, assign users, and more.
TL;DR
Campaign Settings → Automations → New automation rule. Choose trigger type "When status changes to X". Add conditions and actions (send email, set field, assign person). Chain actions with delays for multi-step flows. Keep "Max fires per order" high if the same status may be re-entered.
Get started in 4 steps
Go to Campaign Settings → Automations → New automation rule. Set the trigger to "When status changes" and select one or more target statuses.
Add optional conditions to narrow scope — e.g. only run for leads with a specific field value, assigned person, or region.
Add actions: Send email, Send SMS, Set field value, Set assigned person, Delay. Chain multiple actions to build a full workflow sequence for that status change.
Set "Max fires per order/lead" appropriately. If the status can be re-entered (e.g. a lead returns to "Contacted"), increase this to allow multiple triggers. Save and test with a real lead.
Read more⌄
Typical use cases for status-based automations
- Notify assigned salesperson when a lead becomes "Ready for quote"
- Send customer a "Quote sent" email with the PDF attached
- Trigger a 3-day follow-up sequence when a quote is not accepted
- Send internal Hubhus message when a lead is moved to a closing stage
- Set a "follow_up_date" field when a lead enters "Waiting for documents"
Adding conditional logic
Within the automation, use conditions to make actions conditional:
- Only send email if
%assigned_person_email%is set - Only notify team if lead is from a specific region
- Only continue if no booking has been created yet
Best practices
- Name statuses clearly — automations are easier to maintain when the status name describes the stage.
- Avoid multiple overlapping rules for the same status — consolidate into one with conditional branches.
- Use delays before emails to avoid sending immediately after noisy manual status updates.
- Always test with a dummy lead before activating on production.
Common searches
status change automation • automate on status • trigger email status change • when status changes 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