How it works › Configuration

Automations

Automations allow actions to be performed on records automatically—without any user involvement. They always belong to a specific dataset and are created through its context menu, via the “Automate” option.

Each automation consists of three parts: a trigger, a condition, and an action.

The trigger defines when the automation fires. Currently available options include: immediately when the date and time stored in a property value is reached, or a specified amount of time before or after that moment. The same applies to state changes—immediately after, or a specified amount of time after the change.

The condition defines when the automation should actually execute. Currently, this is a specific state the record must be in at the time the trigger fires.

The action defines what happens. Currently available options are:

• send a notification—via email or push, with a custom message. Values from the record can be inserted into the message using curly braces and the property name, e.g. {Name};
• change the record’s state;
• archive the record;
• move the record to trash;
• HTTP request—send the record's data to a specified URL via a POST request.

Example: if a task’s deadline has passed by more than a day and the record is still in the “In progress” state—send a notification to the manager.