Skip to main content
Help center / Apps & extensions / Automations App Overview

Automations App Overview

Automations

1. What it is

Automations is where you build, schedule and follow the work that runs on its own. An automation is a list of steps that act in your apps. It runs when someone clicks Run now, on a schedule, or when something happens in another app. It always runs as one person, and never with more access than that person has.

It is built for business admins, and for anyone a business admin gives access to automations.

  • Enablement: Automations is licensed. It comes with Platform Standard and Enterprise: if your plan includes it, it is on until an admin disables it. An organization that already had automations when the app was created had it switched on. On any other plan it is off until an admin enables it.
  • What it is not: Automations does not judge whether an automation helped. Loop does that, and while Loop is on its verdict shows on the Automations list (section 3). Automations is also not where you stop all AI at once: Pause All AI lives under AI Operations in the admin sidebar. The app’s own Pause All Automations stops automations only.

2. Standing it up

  1. In the admin sidebar, open All Apps, choose Automations, and click Enable App. Skip this step if Automations already appears in your sidebar.
  2. Open Automations. As a business admin you see five tabs: Automations, Templates, Automation Runs, My Scheduled Starts and Access.
  3. Decide who else may build or run automations. Business admins always can. Anyone else needs two things: to be in the app’s audience (Manage User Access on the app’s page under All Apps), and either a process grant from a business admin on Access or an automation they own.
    • An app’s own admins. In the admin sidebar, open All Apps, choose the app, and open App Admins. On an App admin’s row, the ⋮ menu offers Give Automation Access. It opens Access filled in for them: author, publish, schedule and run; company-wide, or only the places they manage when their App admin role is limited to places; that app’s actions plus the steps every automation shares (Wait, Collect details, Ask a participant, AI reasoning, Generate a value, Send a notification); running as them; ending in a year. Review it, then confirm, and their row reads Can manage automations. Removing their App admin role, or making them a Contributor, revokes that grant too, including a grant you replaced on Access.
  4. On Automations, click Create Automation, or open Templates to start from a template. Save the draft.
  5. Confirm it worked: the automation appears on the Automations list with the status Draft.

3. How it fits together

An automation, its starts and its runs

  • An automation is the definition: its steps, the inputs it asks for, and who it runs as. It has a draft and published versions. Runs use the published version; saving a draft changes nothing that runs.
  • A start says when it runs on its own: on a schedule, or when an event happens in another app. An automation with no start shows Manual on the list and runs only when someone clicks Run now.
  • A run is one execution. It keeps each step’s result, the inputs it started with, and who it ran as.

Access

A business admin sees and manages every automation. Anyone else reaches automations through a process grant, issued on Access by a business admin only. A grant names:

  • Capabilities: Edit process definitions, Publish processes, Manage process starts and Run processes.
  • Automation (optional): one automation, or any eligible one.
  • Process scope: one person, a reporting line, chosen locations, or the company.
  • Allowed actions: the app actions the person may use in an automation.
  • Limits: runs per hour, actions per run and people per run.
  • Access begins and Expires dates.

A grant does not give app or data permissions; those still apply to every action. Being an admin of this app, or of another app, gives no automation rights by itself.

Asks to a person

An automation can stop and ask a person for input, or ask them to approve an exact task before it is created. The person gets the ask in Notifications and answers on its own page, on desktop or phone. These asks file under the Approval Requests notification setting. Other automation notices — a start stopped, a change to your access — file under Automations.

Loop’s verdict

When Loop is on for your organization, the Automations list has a Result column. An automation whose start a Loop plan measures shows that plan’s verdict, such as Measuring or Kept. An automation with a running start and no plan shows Never measured — find out to people who can own a Loop plan; it opens a plan for that start. Everyone else sees a dash.

To give an automation a number when you add a start, answer What should this move? on the start form (optional, and shown only while Loop is on). For an automation under process access, Loop saves that plan as a draft, and nothing is measured until you mark it live under Not live yet on Loop’s Overview. On Loop’s ledger, a business admin sees the doors back here: a kept plan with no start offers Add a Start, a retired or rolled-back plan whose start still runs offers Pause its start (or Stop its start), and a rolled-back plan offers See its runs.

4. Running it

Build from a description, a document or a template

  1. On Automations, type what you want under “What process would you like to automate?” and click Draft with AI. Or click Start from a document, or Create Automation for a blank editor.
  2. In the editor, the Build with AI panel proposes steps from your description or a process document. Review the proposed steps before applying them.
  3. Click Save Draft.

To start from a template, open the Templates tab. In the Automation library, click Preview to see a template’s steps and inputs, and Use to add it as an editable draft. A template grants no access, publishes nothing and starts no schedule.

Test it

On the automation’s page, click Test. Choose Check the structure (checks the steps without running their actions), Test read actions (runs permitted read actions and simulates writes), or Review a live pilot (can change real data). Click Prepare test. Tests use the saved draft. A pilot’s result page offers Start live pilot; each action that changes data then asks for approval. A structure check creates no task, so verify a real run and its task in Tasks.

Publish it

The automation’s page shows the Unpublished draft card.

  • Click Publish Version when you may publish (a business admin, or a person whose grant includes “Publish processes”).
  • If your organization set up a publication review, the card offers Request Publication Review instead. The reviewers’ approval publishes the version. It does not approve any action during a run.

Publishing replaces the version future runs use. It also pauses what would run it, and the card says what before you confirm: the automation’s starts, and for an automation under process access the automation itself. Choose Resume from the menu beside Edit to turn the automation back on; each start’s owner then renews its consent and resumes it. Runs already started keep their saved steps. Published versions lists earlier versions; Copy to Draft puts one back in the draft.

Run it

In the Run this automation card, fill in any inputs and click Run now. The run starts as you. If it needs your input or approval, the request reaches you in Notifications.

Schedule it

There are two ways to add a start.

  • A business admin’s start. In the list’s Starts column, click the start count or Manual · add a start. On the starts page, click Add a Start, choose a schedule or an event, and fill in the inputs. Each start’s menu offers Edit, Run now and Pause. A start under process access that runs as someone else offers Stop this start instead of Run now and Pause.
  • Your own scheduled start. Open My Scheduled Starts and click Set up a scheduled start, then Set up schedule beside an automation. Pick the schedule and time zone, click Review paused start, then Save paused. On the start’s page, choose whether to approve actions in advance and when consent ends (90 days unless you change it; at most 365). Click Review consent, then Authorize this start.

An automation can be scheduled this way when it is published and active, runs as you, has no Wait step, and pauses only for your answers to a top-level input step or your approval of a top-level task it creates. A person who is not a business admin also needs “Run processes” and “Manage process starts” access to it. On the start’s page, Pause future starts stops future starts; Revoke consent also stops later steps in unfinished runs.

Follow runs

Open Automation Runs. A business admin sees every run; everyone else sees My Automation Runs. Filter by status, automation and date, and click Export CSV to download the list. A run’s page shows each step and its result.

  • A business admin can Retry a failed run (steps that already succeeded are skipped) or Cancel run.
  • The person a run belongs to follows it on its run request: click Open run request. That page shows who has the run now, links the task or service request it created when you can open that record, and offers Cancel Run.
  • A created task or ticket is still waiting until its own app records the outcome. Cancelling a run stops later steps; it does not undo work already created.

Undo This Run

When a run changed records that keep a history, a business admin sees What this run changed on its page: each change, linked to its Audit Log entry. While a changed field can still be put back, the card offers Undo This Run. Each field goes back to what it held before the run, unless it has been changed again since. Status changes, records the run created or deleted, and anything it sent are not undone.

Answer an ask

  1. Open the ask from Notifications.
  2. For an input request, fill in the fields, click Review answers, then Confirm answers.
  3. For an approval, click Review action on the run request. It shows the exact task, its assignee and due date. Click Approve task to continue the run, or Reject and stop with an optional reason (up to 2,000 characters).

Confirming answers queues the rest of the run; it does not mean the remaining steps are done. Rejecting stops the run without creating the task; earlier completed steps remain. One reminder may be sent while an ask stays open.

Starters to build with

Two examples, for a person with access to Automations and Tasks plus “Edit process definitions”, “Manage process starts” and “Run processes” for their own scope:

  • Personal follow-up: Add Request information, keep the person running the automation as respondent, and add a required Text input named task_title, labeled “Task title”. Follow it with Tasks → Create task: set title to $inputs.task_title, use “Follow up on my request” as the description, and leave the assignee unset to assign yourself. Save the draft, publish it, choose Resume, then click Run now. Open the input request, enter the title, then confirm your answers.
  • Personal review reminder: Use Tasks → Create task with the title “Review my priorities”, the description “Choose my next follow-up”, and yourself as assignee. Publish it, resume it, and set up your own scheduled start as described under “Schedule it”.

The template library includes Personal Follow-up, Reviewed Weekly Follow-up and Verified Workday Completion. Each adds an editable, inactive draft. Review and publish the draft, then resume it; a recurring one also needs its own scheduled start.

Three team-process starters are also available:

Starter Configure before publication What completion means
Manager-approved Service Request In Service Desk, configure General requests for manager approval and a fulfillment queue. Map any required custom fields into the input step. The employee runs the automation for themselves. The same native request is resolved or closed.
Weekly Team Follow-up As the manager, choose one named teammate in Who responds? and the same person as Task assignee. Use reporting-team scope, at least two people per run, and current Tasks assignment rights. Review the Monday schedule and its time zone, then authorize it separately. The manager approved the exact task and its assignee completed it in Tasks.
New-hire Access Request In Service Desk, configure Access requests for manager approval and your IT queue. Add the request type’s required fields. The new employee starts their own request by hand. The native request is resolved or closed; the automation does not provision an account or write to an HR system.

The service-request starters are employee-owned copies. A business admin first gives that employee a grant on Access with “Edit process definitions” and “Run processes”, plus access to Service Desk. The employee adds and configures their copy; someone allowed to publish reviews it before it runs. A manager’s published copy cannot be run as a different employee. None of this makes the employee a business admin.

The Service Desk starters use its current approval and routing rules. If approval is off for the chosen request type, the automation does not add it. Required fields the automation cannot collect, such as attachments or a mandatory knowledge-article check, need the native Service Desk form. A missing eligible manager or participant blocks the affected handoff; no substitute is chosen.

The teammate receives only their own input request, through Notifications or its desktop or phone link. Their answers do not change who the run belongs to. For the team task, the original manager reviews the task title, details and assignee before it is created. A rejection reason stays on the reviewer’s decision page; it is not copied into notifications.

If access or a reporting line changes, correct the setup, cancel the old run, and use Review process and start again where it is offered. A new run starts from the beginning, so check existing tasks and tickets first to avoid duplicates.

Verified Workday Completion is a manual automation for your own completed Training enrollment. An administrator first configures Workday Learning in Training and supplies the connection and the exact existing enrollment references. The course reference must be Learning_Course_ID:<course ID> or WID:<course WID>; course offerings are not supported. The step requests or observes Training’s existing completion delivery and waits for verified completion before creating your follow-up task. Training may already have queued or sent the completion. Cancelling the run stops later steps; it does not undo or cancel Training’s delivery. This step is not available in schedules, nested steps or approval-before-send flows.

5. Settings and access

Automations has no settings page of its own. Who sees what:

Person What they see
Business admin All five tabs, every automation, MangoApps’ built-in automations, each automation’s starts page, every run with What this run changed and Undo This Run, Access, and Stop any scheduled start
A person in the app’s audience with a grant, or who owns an automation Automations, My Automation Runs and My Scheduled Starts, and Templates when they may build automations; the automations their grant covers; only the actions its capabilities allow
Anyone else No Automations app

Every run acts as its run-as person, so nobody can automate more than they can do themselves.

Pause All Automations, in the ⋮ menu on the Automations list, is for business admins and for the app’s admins who can open the list (an app-admin grant alone does not open it; see the table above). It stops every automation’s scheduled and event starts and cancels queued runs until a business admin resumes them, with Resume Automations on the list’s banner or in AI Operations. Run now still works. It is the same automations pause that AI Operations shows, so Pause All AI there covers it too.

Built-in automations are the ones MangoApps provides. A business admin sees them in their own section under the Automations list: Clone to Customize makes an editable copy, and Hide from Ask AI keeps one out of Ask AI, MCP and the automations a form’s “Run an automation” step can pick, for everyone in your organization. Its starts keep running.

Three controls live outside the app:

  • Pause All AI in AI Operations stops every AI area at once, automations included, until an admin resumes them. Run now still works, and the Automations list shows a banner while the pause holds.
  • Who sees the app is set under Manage User Access on the app’s page under All Apps.
  • Notification settings: asks are under Approval Requests; other automation notices are under Automations.

On a phone, My Scheduled Starts, a start’s page, setting up a start, the administrator stop list and every ask (input, approval, run status, cancel) have phone pages. Building, testing, the automation list and the runs list are desktop pages. Ask AI, MCP, Notifications and email links open the owning pages; a link does not submit answers or authorize a run.

6. More help

  • Automations FAQ — setup and operating questions, exact limits, and what to check when a run waits.
  • Loop App Overview — how Loop measures whether an automation, or any change, actually worked.
  • AI Operations — Pause All AI, approvals of AI agents’ actions, and agent health.
  • Ask AI — on the Automations pages, Ask AI can list automations and draft one for you. It hands you an ask’s own page rather than answering it for you.