How to set up automations

Modified on Tue, 5 May at 9:30 PM

How to set up automations

Automations in Hubhus create automated workflows that respond to events, check conditions, and execute actions — sending emails, changing statuses, assigning users, and more.

TL;DR

Access: Campaign settings → Automation → New trigger event. Every automation has: (1) Trigger — what event starts it (lead created, status set, field changed, etc.). (2) Requirements — optional conditions that must be true (status, field value, email sent, etc.). (3) Actions — what happens (send email/SMS, set status, assign person, HTTP request, etc.). (4) Execution timing — when/what days actions run, whether criteria must re-apply at execution. Limit max fires per lead to prevent loops.

Get started in 4 steps

1

Choose the trigger event

Go to Campaign settings → Automation → New trigger event. Give it a descriptive name. Choose the event: Lead is created, Status set to, When the value of a field has changed, On follow-up, Calendar events, On action button click, On visit at page, Another trigger is pulled, On the date/time specified in a field, etc. For field changes: configure when it triggers (from empty, from non-empty, to empty, to non-empty). Set trigger time (immediately / after X min/hours/days). Set max fires per lead to prevent repeats.

2

Set requirements (conditions)

Click Edit requirements. Filter which leads should trigger the automation. Available conditions: Status (is/was/was not), Assigned person, Field value (filled/empty/specific value), Select field value, Email sent/not sent/opened, Subscription status (to avoid sending to unsubscribed), Calendar events, Automation history (was/was not triggered by another), Web page visits, Origin, Custom placeholder expressions (e.g. @if(%postal_code% == 2000){1}@endif). Always add requirements to prevent unwanted execution.

3

Add actions

Click + Add action. Available actions: Send email (select template, configure To/CC/BCC/From), Send SMS, Set status, Set reason, Assign person / Auto assign person, Add comment, Create follow-up, Set field value (text, select), Submit HTTP request (API integration), Anonymize. Each action can be individually activated/deactivated without deleting. Add multiple actions per trigger when they logically belong together.

4

Set execution timing

Click Edit execution time. Set: which days (any / weekdays / specific days), time window (from–to, e.g. 08:00–18:00 to avoid sending at night). Choose whether requirements must apply both at trigger time and at execution time (safer) or only at trigger time (fires regardless of later changes). Monitor automation performance via Show log counts.

Read more

Common automation scenarios

  • Welcome email: Trigger: Lead is created. Req: Email is filled. Action: Send welcome email
  • Status change notification: Trigger: Status set to "Won". Action: Send email + add comment
  • Auto assignment: Trigger: Field "Product Interest" changed. Req: Not assigned. Action: Auto assign person
  • Re-engagement drip: Trigger: On date in field. Req: Status is "Cold". Action: Send re-engagement email
  • Booking invitation: Trigger: Status set to "Ready to book". Action: Send email with @bookingFormUrlPublic[form-id]
  • Chained sequences: Use "Another trigger is pulled" event to chain automations

Troubleshooting

  • Not firing: Check trigger is Active; verify max fires per lead not exceeded; check triggering scenarios
  • Actions not executing: Check action is Active; review execution time window; check requirements at execution time
  • Wrong leads triggered: Add more specific requirements; check field value conditions
  • Duplicates / loops: Set max fires per lead; add "Must not have been triggered by" requirement; use delays

Common searches

automation setup • workflow automation • automate process • trigger automation • automatic email • automation rules • trigger event

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article