All Collections
Automations
Attribute Mentioning in Automations
Attribute Mentioning in Automations

Create advanced Actions by mentioning attributes in your Automations

Nataša Brocić avatar
Written by Nataša Brocić
Updated over a week ago

Definition

When creating an Automation, you will come to find that for each Action there is an option to add text with attributes in the rich text field of the selected Action. That can be accomplished in:

  • Message field for Send Slack message Action

  • Comment field for Create a comment Action

  • Description field for Create Task Action

  • Description field for Update Task Action

In those fields, you can mention attributes or custom fields from all PREVIOUS linkable steps (Trigger and Condition).

Example:

Attributes in Productive are associated with data or objects such as projects, deals, tasks and so on, therefore, mentioning involves referencing attributes like Project/Budget owner, Task list, Last actor and many more.

Once the Automation is triggered and completed, instead of the mentioned attribute the user will see its true value.

Example:

Check Deal {Deal ID} for more info.

translates to:
Check Deal 5244 for more info.

List of attributes

Attributes that can be mentioned:

TASK

DEAL

BUDGET

  • ID

  • Number

  • Slack link

  • Creator

  • Project

  • Status

  • Title

  • Start date

  • Due date

  • Initial estimate

  • Worked time

  • Remaining time

  • Assignee

  • Last actor

  • Task List

  • Custom fields

  • ID

  • Number

  • Slack link

  • Creator

  • Status

  • Name

  • Probability

  • Revenue

  • Owner

  • Company

  • Lost reason

  • Custom fields

  • ID

  • Number

  • Slack link

  • Creator

  • Project

  • Status

  • Name

  • Owner

  • Company

  • Percentage used

  • Custom fields

How it works

Simply click on the {} in the description/message/comment field and select the attribute you would like to mention:

The number next to the attribute defines the object tied to the attribute. In this case, 1 Owner is tied to the DealDeal created Trigger:

so when we mention the Owner in the task, it will be the owner of the Deal created.


Here is an example of the task created automatically - underlined red is the attribute Owner:

Did this answer your question?