Understanding action listeners
Action listeners let Hubhus react the moment something happens on a lead - a field update, a file upload, a form submission, a booking. Automations are for work that should run before or after something has happened (delays, schedules, sequences).
TL;DR
Action listeners trigger the moment something changes. They can send emails/SMS, update fields, notify users, and trigger integrations. No delays - use Automations when you need timing before/after an event, reminders, or multi-step sequences. Listeners fire every time the event occurs (no "max fires" cap). Use conditions to prevent over-firing. Choose based on timing, not on whether you need email/SMS.
4 things to know
What triggers an action listener
Any change to a lead can be a trigger: a field value changes, a select option is picked, a file is uploaded, a form is submitted, a booking is created, a checklist is completed, a relation is added. You specify exactly which field or event type to watch.
What actions can be performed
Send email, send SMS, notify internal user, set a field value, change status, trigger integration/webhook, create related data. Keep the action list short — listeners are for quick, focused reactions.
Listeners vs. Automations
Action listeners: run when something happens - immediate. Ideal for instant confirmations, field updates, notifications, integrations.
Automations: run before or after something has happened - ~60s cycle, delays, chained steps, reminders, sequences.
Both can send email/SMS. Classic pattern: listener reacts immediately → automation handles timed follow-up.
Key limitations
No delays - if you need timing before/after an event, use an Automation. No "max fires" cap - if the field changes 10 times, the listener fires 10 times. Use conditions to prevent duplicate or unwanted triggers. Keep each listener focused; multi-step timed workflows belong in Automations.
Read more⌄
Common use cases
- Customer uploads images → notify reviewer instantly
- Lead address changes → recalculate and assign region
- New booking created → send confirmation SMS immediately
- Zipcode changes → auto-assign to correct regional team
- Checklist submitted → move lead to next status
- Status becomes "awaiting booking" → send booking link email
Creating an action listener
Go to Campaign settings → Action listeners → New listener. Configure:
- Trigger: which field/event type to watch
- Conditions: optional filters (only fire if field X == Y)
- Actions: email, SMS, set field, webhook, etc.
Best practices
- Keep each listener focused on one action — don't pile on logic
- Add conditions to prevent firing on unrelated changes
- Check lead history to verify when listeners fired
- Use CTRL+K / CMD+K in actions to find the right placeholder
Common searches
action listener • instant trigger • field change trigger • listener vs automation • real-time notification
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