Skip to main content
Automations
Automations
Automations

Automations

Build, schedule and follow the work that runs on its own — by hand, on a schedule, or when something happens in another app.

Overview

Describe the work in plain words, start from a template, or build it step by step, and review the drafted steps before anything is saved. An automation runs by hand, on a schedule or when something happens in another app, always as the person it runs for and never with more access than they have.

Every run keeps its steps, what it changed and who it ran for. A run's plain field changes can be put back with Undo This Run, and AI Operations' Pause All stops every automation at once.

Business admins see and manage every automation. A person given access builds, schedules and follows their own, within the actions, places, limits and dates their grant sets. Loop tells you whether an automation is helping: give it the number it should move and its verdict shows on the list.

Highlights

Describe the work in plain words or start from a template, and review the drafted steps before anything is saved.
Run an automation by hand, on a schedule or when something happens in another app, as the person it runs for — never with more access than they have.
Every run keeps its steps and what it changed, and a run's plain field changes can be put back with Undo This Run.

Capabilities

Build and publish
  • Draft an automation from a plain-words description or a process document, and review the proposed steps before applying them
  • Start from a template in the automation library, added as an editable draft that grants no access and starts nothing
  • Steps that ask a person for input, or for approval of an exact task before it is created
  • Test before going live: check the structure, run read actions with writes simulated, or review a live pilot
  • Drafts and published versions: saving a draft never changes what runs, and an earlier version can be copied back to the draft
  • Publish directly, or through a publication review your organization sets up
  • MangoApps' built-in automations, with Clone to Customize and Hide from Ask AI (business admins)
Starts and runs
  • Run an automation now, on a schedule, or when an event happens in another app
  • Scheduled starts that run as you, with your consent, an end date, and optional approval of chosen actions in advance
  • Answer an input request or approve a task on desktop or phone, from the link in Notifications
  • Run history with each step's result, filters by status, automation and date, and CSV export
  • Retry a failed run (steps that already succeeded are skipped) or cancel one that is no longer wanted
  • What this run changed, with Undo This Run to put changed fields back (business admins)
Access and control
  • Business admins see and manage every automation and every run
  • Process grants: capabilities, one automation or any eligible one, a scope, allowed actions, limits and dates
  • Every run acts as its run-as person, never with more access than they have
  • An app's admins manage that app's automations through a grant issued with the role (Give Automation Access)
  • Pause All Automations stops every automation's scheduled and event starts until a business admin resumes them
  • Pause All AI in AI Operations stops scheduled and event starts at once
  • A business admin can stop anyone's scheduled start without opening their automation
  • Loop's verdict on each measured automation, shown on the automation list

Use cases

Turn a request into a task, automatically
An automation asks the person who runs it for a title and details, then creates a follow-up task in Tasks assigned to them. Start from the Personal Follow-up template, publish it, and run it whenever the request comes up.
A weekly team follow-up the manager signs off
Every Monday an automation asks one named teammate for a follow-up, and their manager reviews the exact task before it is created. Nothing is created until the manager approves it, and a rejection stops the run.
Service and access requests that follow your own approval rules
An employee starts a service or new-hire access request from their own copy of a starter. Service Desk's approval and routing rules decide who approves and which queue fulfils it; the run follows the request until it is resolved or closed.
Find out whether an automation is helping
Give a start the number it should move when you add it, and Loop measures it. The verdict shows beside the automation on the list, and an automation nobody measures offers "Never measured — find out".

FAQ

Business admins always can. Anyone else needs to be in the Automations app's audience and either hold a process grant a business admin issued, or own the automation. A grant names what the person may do (edit, publish, manage starts, run), which automations and people it covers, the actions allowed, limits and dates.

No. Every run acts as its run-as person and checks their current access before each action. A process grant does not give app or data permissions; those still apply.

No. Saving changes the draft only. Publishing replaces the version future runs use and pauses what would run it until it is turned back on, and runs already started keep their saved steps.

A business admin can. The run's page lists what the run changed, and Undo This Run puts each changed field back to what it held before, unless it has been changed again since. Status changes, records the run created or deleted, and anything it sent are not undone.

Pause All Automations, in the menu on the automation list, stops every automation's scheduled and event starts and cancels queued runs until a business admin resumes them. Run now still works. Pause All AI in Admin › AI Operations stops every AI area at once, automations included. A business admin can also stop any one person's scheduled start from the Automations app.

Loop measures it. When Loop is on, give a start the number it should move, and the plan's verdict shows on the automation list. Loop judges; Automations runs.