Understanding action listeners
This guide covers understanding action listeners.
On this page
Jump to any section using the links below
Action listeners let Hubhus react instantly to changes on a lead, an event, a file, or a field.
Unlike automations—which run on a timed schedule—action listeners fire in real time and are ideal when something must happen immediately.
This article gives you a simple Getting Started overview.
What are action listeners?
Table of Contents
- What are action listeners?
- Difference from automation rules
- Field-based triggers
- Limitations and workarounds
- 1. No delays
- 2. They fire every time the event occurs
- 3. Limited multi-step flows
- 4. Avoid heavy logic
- Best practices
- 1. Use listeners for real-time actions
- 2. Keep logic light
- 3. Combine with automations
- 4. Use filters to control when it triggers
- 5. Test using the Editor
- Learning outcome
Action listeners are rules that trigger the moment something changes, such as:
A field value is updated
A select field changes
A file is uploaded
A customer submits a form
A booking/event is created
A checklist is completed
They are used to create fast, reactive workflows without waiting for the automation cycle.
Examples of what an action listener can do:
Send an instant email or SMS
Notify internal users
Trigger an integration
Update fields or statuses
Create new related data
Difference from automation rules
Although both automations and action listeners perform actions, they operate differently:
Action listeners
Run instantly
Are event-driven
Fire directly when a lead or event changes
Best for real-time reactions (notifications, integrations, confirmations)
Automations
Run on a schedule (typically every 60 seconds)
Support delays, waiting logic, and chained steps
Best for reminders, timed workflows, and multi-step processes
Use action listeners for speed.
Use automations for timing.
Field-based triggers
Action listeners can watch for changes on:
Standard fields (email, phone, name, etc.)
Custom fields (API-based fields)
Select fields
Status
Files
Events
Checklists
Relations
Examples of simple use cases:
When zipcode changes → assign region
When customer uploads a file → notify internal team
When status becomes “awaiting booking” → send booking link
When a checklist is submitted → move to next workflow step
Limitations and workarounds
Action listeners are powerful, but they differ from automations in a few ways:
1. No delays
Action listeners cannot “wait” or run after a delay.
If you need timing logic → use an automation.
2. They fire every time the event occurs
Action listeners do not have a “max fires” limit like automations.
If the field changes again, the listener fires again.
3. Limited multi-step flows
For more complex workflows (multi-step sequences), combine:
Action listener → to trigger immediately
Automation → to perform delayed or sequential actions
4. Avoid heavy logic
Listeners should do quick actions.
If the workflow becomes complex, move the logic into an automation instead.
Best practices
1. Use listeners for real-time actions
Examples:
“Customer uploaded images → notify reviewer”
“Lead address updated → calculate distance instantly”
“New booking created → assign resource immediately”
2. Keep logic light
Listeners should perform simple tasks quickly.
3. Combine with automations
A classic pattern:
Listener fires instantly when the event happens
Automation handles delayed reminders or follow-up steps
4. Use filters to control when it triggers
Ensure the listener only runs under the right conditions.
5. Test using the Editor
Just like with templates:
Use CTRL+K / CMD+K to search placeholders
Review field API names
Use lead history to verify when listeners fire
Learning outcome
After reading this, you should understand:
What action listeners are
How they differ from automations
When to use listeners vs. automations
How field-based triggers work
Limitations and best practices for reliable workflows
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