Automation Triggers and Steps
An Automation runs on its own from Setup: it starts on a trigger you choose, then runs its steps. This reference lists everything that can start an Automation and everything its steps can do. Run History shows what each Automation did. For how Work Items, Flows, Stages, and the Work Queue fit around Automations, see Work and Automations overview.
What can start an Automation
An Automation starts in one of four ways. You pick the trigger when you configure the Automation in Setup.
Trigger | When it runs |
|---|---|
When something happens | In response to an event in Leasecake. |
On a schedule | At the times the schedule defines. |
As a critical date approaches | As a critical date, a deadline or milestone derived from the lease, comes up. Each timing row is set to Before, On, or After the key date; On runs on the key date itself, and a run that would fall on a weekend or holiday moves to the previous business day. |
On demand | When someone starts it. |
What an Automation's steps can do
An Automation is built from steps, and each step is one of the following.
Step | What it does |
|---|---|
Send a message | Sends an email, an in-app notification, a Slack message, or a webhook. |
Create or update Work Items | Creates a new Work Item or updates an existing one, putting work in front of a person or group. |
Generate a report | Generates a report from your portfolio or accounting data. |
Set a custom field | Sets the value of a custom field on a lease or another record. |
Wait | Pauses before the next step runs. |
Holding a change for approval
An Automation can hold a change for approval as a Pending Action. The change waits until the Work Item it depends on is approved, and only then does the Automation complete and release it. A lease publish, for example, can be held this way before it takes effect.