Automations

An automation is one trigger plus an ordered chain of steps: when a meeting ends, summarise it, write it to the CRM, email the result. Automations are built on the web from templates. The phone lists them, shows what each one is set up to do, tests one on demand, shows its run history, and answers the approvals it pauses on.

Automations and agents

The two are easy to mix up. An automation runs the same fixed steps every time its trigger fires, and an admin sets those steps on the web. An agent decides for itself, after a debrief, whether there is follow-up work worth doing, and you switch agents on and off in the Configure tab. Agents are covered in Agents and their cards.

Who has them

Getting there

Open the menu and tap Automations under Organization. The row shows a count of the approvals waiting on you.

Approvals also reach you without opening the list: on the Actions tab of Home, and as notifications. See Approvals.

The list

At the top is a dashed Request Automation button. Automations are built on the web, so the phone files a request for a new one instead of building it. See Requesting an automation.

Below it, if any automation runs on a schedule, a Scheduled card names the one that runs next and when. When there is more than one, a count sits beside the title. Tap the card to open the one that is due. Scheduled automations also appear in the list underneath.

Then every automation in the organization, one row each. A row shows:

• the name
• what triggers it, in plain language
• "1 run needs your approval" (or the number of runs), when any are waiting on you
• otherwise "Disabled" if it is switched off, and when it was last updated

Automations with an approval waiting on you are sorted to the top. Pull down to refresh.

With nothing set up yet, the screen says "No automations yet".

Where to go next