On this page

Jump to any section using the links below

Custom fields in Hubhus allow you to store structured information and use it to control automations, workflows, and notifications. This article explains how custom fields behave inside automations, how action listeners respond to field changes, and what limitations you should be aware of.

Understanding how custom fields interact with automations

Hubhus supports two systems that react to field changes:

1. Automations

   • Runs every 60 seconds

   • Can evaluate multiple conditions

   • Can combine status, fields, and timing

   • Good for multi-step flows

2. Action listeners

   • Trigger immediately when a field changes

   • Only react to direct changes

   • Ideal for real-time notifications or integrations

Most custom fields can be used in both systems, but the behaviour differs.

Field-based triggers in automations

Automations can check any custom field using conditions such as:

• “Field equals X”

• “Field changed”

• “Field contains value”

• “Field is not empty”

Typical use cases:

• Send an email when a checkbox changes

• Assign a user when a select field changes

• Move a lead to a new status when a numeric value updates

Since automations run in intervals, they are suitable when timing is not critical.

Using action listeners on custom fields

Action listeners run immediately when a field value is updated. They are ideal when you need a fast reaction, such as:

• Notifying someone in real time

• Triggering an integration

• Updating related data structures

• Reacting to documents, uploads, or checklists

Action listeners are best for simple, direct triggers. They do not support delays or multi-step logic.

Limitations and important considerations

Some limitations apply when using custom fields as triggers:

• Certain relational fields cannot be used directly in action listeners

• A change must come from a save event; previewing or editing without saving will not trigger anything

• Automations only trigger again if “Max fires per order” allows multiple executions

• Select fields should use the slug value for logic

• Large JSON/data fields should be used carefully; listeners detect changes, but complex comparisons may require helper fields

If a trigger does not fire, always confirm:

• Whether the event has triggered before

• Whether the field actually changed

• Whether the automation exceeded its trigger limit

Workarounds for complex logic

If your workflow requires conditions that are too complex for action listeners, consider these patterns:

1. Use a helper select field

Convert multiple conditions into a single select field that triggers your action.

2. Use automations for final evaluation

Let the action listener store a marker field; let the automation evaluate the full rule.

3. Use a status change as the trigger

Status changes are universally supported and easy to chain.

4. Use JSON/data fields combined with automations

Store structured data and create automation rules that monitor simple flags or totals.

Summary

Custom fields can drive powerful, flexible automations.
Use action listeners when you need instant reactions, and automations when you need multi-step logic, delays, or combined conditions. For advanced workflows, helper fields or chained automations can simplify complex logic while keeping triggers reliable.

? Common searches

automation setup • workflow automation • automate process • automation rules • trigger automation

? Also known as

workflow • automatic process • triggered action • rule

Related articles

How to add custom fields to booking forms
How to calculate values and format numbers in templates
How to format dates and calculate time differences
How do I create custom fields?
How do I manage SELECT fields and dropdown options?