Automations
Configuring the automations that trigger off a signal or a request.
An automation template is a trigger plus an ordered chain of actions, authored once and then either running on its own or available for someone to request on demand.
What you configure
Configuration covers the trigger, a signal, a schedule, or nothing at all if the automation should only ever run on manual request, the action chain the automation executes once triggered, and any approval gates: which steps, if any, pause for a human sign-off before executing.
Where it's authored, where it runs
Automations are authored in the console. This isn't something configured from the mobile app. Once published, a run can be triggered, monitored and approved from any surface, including the phone; see Automations on mobile.
Requests for new automations
When someone needs an automation that doesn't exist yet, they can request one instead of building it themselves. The request reaches admins as a description of what's needed, not a half-built template.
Where this is managed
Automations are built in the console under Automations.