Use Custom Fields in Automations

You can use Custom Fields in each step of your Automations.

Feature availability and limits vary by plan and user role. Learn more

Trigger Automations using Custom Fields 

You can trigger Automations using Custom Fields including:

  • Custom Field changes: When a Custom Field changes, take action. 
  • Date Custom Field arrives: When the date Custom Field arrives, take action.

In the below example, the Automation is triggered by the Paid? Custom Field being set to paid:

Screenshot of an Automation using the Custom field changes trigger.

In the below example, the Automation is triggered on the Invoice due date:

Screenshot of an Automation using the Date Custom Field arrives trigger.

Filter by Custom Fields in Conditions

Use Custom Fields in your Automation Conditions to filter when Automations should run on your tasks.

In the below example, the Automation only runs on tasks where the Paid? Custom Field is set to Not Paid:

Screenshot of an Automation using a Custom Field condition. 

Set Custom Fields in Automations

You can set Custom Fields in Automation Actions including:

  • Set Custom Field: Use this dedicated action to set any available Custom Fields on the trigger task.
  • Create a task: You can set any available Custom Fields as each task is being created.
  • Create a subtask: You can set any available Custom Fields as each subtask is being created.

In the below example, the Automation sets the Invoice ID Custom Field using a combination of text and the dynamic variable of the task ID:

Screenshot of an Automation using the Set Custom Field action.

You can set one or more Custom Fields as tasks or subtasks are being created:

Screenshot of the option to set Custom Fields during task or subtask creation.