Similar to relative date fields, relative person fields allow you to dynamically select users based on their roles or relationships within your automation steps.
Relative person fields allow you to:
Automate processes that depend on specific user roles.
Increase the accuracy and relevance of your automations.
Ensure that tasks and actions are assigned to the correct individuals based on dynamic criteria.
Automation Steps Recap
In an automation setup, there are three main steps:
When
This step defines the trigger event for the automation. It could be related to tasks, budgets, deals, or invoices.
Check if
This optional step adds an additional layer of precision, ensuring the automation executes only under specific conditions.
Then
This final step defines the action to be taken once the conditions are met, achieving the desired outcome.
What are Relative Person Fields?
Relative person fields allow you to dynamically select persons from previous related steps within an automation. You can choose relative persons from all previous related steps within the person selection fields.
List of Possible Relative Person Fields
List of Possible Relative Person Fields
Tasks
User who triggered an automation
Manager of the user who triggered an automation
Creator (Only in the trigger step)
Creator’s manager (Only in the trigger step)
Assignee
Assignee’s manager
Project manager
Deals
User who triggered an automation
Manager of the user who triggered an automation
Creator (Only in the trigger step)
Creator’s manager (Only in the trigger step)
Owner
Owner’s manager
Budgets
User who triggered an automation
Manager of the user who triggered an automation
Creator (Only in the trigger step)
Creator’s manager (Only in the trigger step)
Project manager
Invoices
User who triggered an automation
Manager of the user who triggered an automation
Creator (Only in the trigger step)
Creator’s manager (Only in the trigger step)
Where to Find Relative Person Fields?
Users currently have access to this feature in:
Check if (condition) Step: Available for all attributes of type “person” such as Creator, Assignee, Owner, and the person custom fields.
Create Task Action: Available in the Assignee and Subscribers fields.
Update Task Action: Available in the Assignee and Subscribers fields.
Send Email Action: Available in the To, Cc, and Bcc fields.
Practical Application
Let's consider a practical example to illustrate how relative person fields can be used to dynamically assign tasks in your automation.
Example Scenario: Task Management Automation
When: A task is created.
Check if: The task priority has been changed to high.
Then: Assign the task to the manager of the user who triggered the automation if the priority is high.
