What is automation in Hubhus?
Automations allow Hubhus to perform actions automatically based on specific conditions or events. They ensure that follow-ups, notifications, status updates, and workflow steps happen consistently without manual work.
On this page
Jump to any section using the links below
Automations allow Hubhus to perform actions automatically based on specific conditions or events. They ensure that follow-ups, notifications, status updates, and workflow steps happen consistently without manual work. This article explains the basics of how automations function and when to use them.
Automation concept overview
Table of Contents
An automation is a rule that Hubhus executes when certain conditions are met.
Each automation contains:
A trigger (when it should run)
Optional filters/conditions
One or more actions (what it should do)
Automations help you streamline repetitive tasks and maintain consistent workflows across campaigns.
Typical uses include:
Sending confirmation emails
Moving a lead to a new status
Reminding a customer after a delay
Assigning a resource or internal user
Updating fields
Running chained actions
Triggers vs. actions
Triggers
A trigger defines when the automation should run.
Common trigger types:
When a lead is created
When a field or select-field changes
When a status changes
When a booking is created
When a delay expires
When specific conditions become true
Triggers run periodically (normally every 60 seconds), checking if the conditions match.
Actions
Actions define what happens when the trigger fires:
Sending an email or SMS
Updating a field value
Changing status
Adding a file
Running another automation (chained flows)
Sending data to an integration endpoint
Actions execute in the order they appear in the automation.
When automation runs
Automations run on a recurring cycle and check whether their trigger conditions are met. Examples:
A “status changed” automation runs shortly after the lead enters the specified status
A “field updated” automation runs when the field value matches the rule
A “delay” automation runs once the delay timer has passed
A “booking created” automation runs when a new event is added
Each automation also has a Max. fires per order setting, which determines how many times it can run for the same lead.
If set to 1, the automation fires once and will not run again—even if the conditions later match.
Common automation patterns
1. Welcome / First-touch message
Trigger: Lead created
Action: Send email or SMS
2. Status-driven workflow
Trigger: Status changes to “Quote sent”
Action: Send follow-up after a delay
3. Reminder sequence
Trigger: Field or status indicates customer inactivity
Action: Send reminder → wait → send final message
4. Booking confirmation
Trigger: Event created
Action: Send confirmation and assign internal user
5. Internal alert
Trigger: High-priority select-field
Action: Notify team or assign specific person
Automations can also combine filters to run only under specific conditions.
Automation vs. action listeners
Although similar, automations and action listeners work in different ways:
Automations
Run on a schedule (typically every 60 seconds)
Support delays, conditions, and complex workflows
Ideal for: reminders, follow-ups, timed steps
Action listeners
Run instantly
Trigger immediately when data changes
Ideal for: instant notifications, integrations, or reacting to customer input
In short:
Use automations for timed workflows
Use action listeners for real-time reactions
Learning outcome
After reading this, you should understand:
What automations are and how they work
The difference between triggers and actions
When automations run
Common patterns used in campaigns
How automations differ from action listeners
? Common searches
automation setup • workflow automation • automate process • automation rules • trigger automation
? Also known as
workflow • automatic process • triggered action • rule
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