Attributes are distinct properties, such as the deal creator's name or deal ID, budget number, or the exact name of the project to which a task belongs, that are linked to triggers that provide critical data for an Automation. Moreover, Attributes are essential when defining a Condition.
For example, when creating an automation related to updating a task (trigger), selecting an attribute such as task assignee ensures that the automation is executed precisely when tasks are assigned to specific individuals.
Adding an attribute as a mention, rather than manually entering its details in your message, ensures that your automated messages or tasks are correct and consistent. It also saves time and reduces the likelihood of errors, resulting in greater work efficiency!
List of Attributes by Trigger
TASK TRIGGER ATTRIBUTES | DEAL TRIGGER ATTRIBUTES | BUDGET TRIGGER ATTRIBUTES |
|
|
|
Mentioning Attributes in Automations
In your automation journey, each action offers the option to incorporate attributes within specific rich text fields:
For the Send Slack message action: In the Message field
For the Send email action: In the Message and Subject fields
For the Create a comment action: In the Comment field
For the Create task action: In the Description field
For the Update task action: In the Description field
These fields allow you to mention attributes from both the trigger and the conditions you previously added.
For instance, if your trigger involves creating a deal (see below), you can include attributes like the Deal ID, Number, Creator, Status, Name, Owner, Company, Probability, Revenue, and Lost reason in the task description field within your action.
How to Mention an Attribute
Type "{" or click on "+" in the description/message/comment field and select the attribute you would like to mention.
Tip: When referencing attributes, note the numbers displayed in the dropdown menu! These numbers correspond to specific objects linked with the attributes.
For instance, "1 Project" refers to the Project defined in the first step (the trigger), while "2 Project" refers to the Project specified in the second step (the action of creating a new task).
