The Automations tab
The list of your organization's automations, what each row tells you, and how it is filtered.
An automation is one trigger plus an ordered chain of actions. They are built on the web from templates. The phone lists them, shows what each one is pointed at, runs one on demand, reads its run history, and answers the approvals they pause on.
Automations get their own tab in the bottom bar, next to Home, Entities and History. Guests do not see it.
The list
Every automation in the organization, with a row each. A row shows:
- The name.
- What triggers it, in plain language.
- A dot showing whether it is enabled.
- When it was last updated.
Anything with an approval waiting on you is sorted to the top of the list and marked, so the thing that needs you is the first thing you see.
Filters
Three chips: All, Triggered and Scheduled. Scheduled means the automations that run on a clock; triggered means everything that runs off something happening, such as a meeting starting or ending. There is no manual-only trigger, so every automation falls into one of the two.
Asking for a new one
A dashed Request new automation button sits below the list, and the + in the top bar opens the same thing. Because automations are authored on the web, the phone files a request rather than building one. See Requesting an automation.
Guests
Guests get a locked empty state instead of the list. The tab itself is hidden from the bar for them.
The rest of the roles all see the tab, including users, because an approver can be any member of the organization. That is deliberately more permissive than the web sidebar, which hides its automations entry from users.