Auron
Use AuronMobile appAutomations

Automations

Where automations live now, what each row tells you, and the card for the ones that run on a clock.

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.

Getting there

Menu → Organization → Automations. The row carries a count of the approvals waiting on you, so the number you care about is visible without opening anything.

They sit in the menu rather than the bottom bar because the bar is for places you open several times a day. The only automation thing most people ever act on is an approval, and that arrives on the Actions tab on Home and in the bell. Going looking for the automation itself is the rarer trip, and the menu is where rarer trips belong.

Scheduled

Above the list sits a card for the automations that run on a clock: how many there are, and which one is due next. It reads the same way as the Upcoming card at the top of History, and tapping it opens the one that is due.

Those automations are in the list underneath as well. The card answers what runs next; the list is the automations themselves.

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 and marked, so the thing that needs you is the first thing you see.

The list is not filtered. It is short enough to read, and the two things worth separating out, what needs you and what runs next, are already pulled above it.

Asking for a new one

A dashed Request new automation button sits above the list. Because automations are authored on the web, the phone files a request rather than building one. See Requesting an automation.

Guests

Guests get no Automations row in the menu at all.

Every other role sees it, 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.

Where to go next

On this page