New Automations

Automations: built, for site administrators only

Internal: Automations is built: when something happens in one area, Magpie does steps in others by itself. Only site administrators can open it.

Internal: docs/specs/AUTOMATIONS.md is built behind AutomationPolicy::MEMBERS_ENABLED = false, so only site administrators can open Automations.

A runner, the automations scheduled job, runs every minute. It turns events into runs, does each step at most once, tries a step again after a failure that can pass, stops automations starting each other in a loop, pauses an automation that keeps failing and holds its runs, and clears a run's details after 30 days.

An automation can be started by events in thirteen areas: Forms, Meetings, Contacts, Store, Invoicing, E-Signatures, Issues, Kanban Boards, To-dos, Newsletter, Courses, Webinars and Proposals, and by a set time. Its steps can be Add or update a contact, Add tags to a contact, Add a row to a spreadsheet, Add a To-do, Add a card, Add a Note, Add an issue, Post a message in a channel, Add an event, Make a document, Add a subscriber, Send an email and Send the details to a web address, with Only if, If or otherwise and Wait between them.

The editor shows an automation as a picture of its steps, fills answers with the details of what happened, and has a Test that changes nothing and Run it once for real. Automations also has Starters, JSON import and export, Add an automation… in the More menu of a Form, a Kanban board and a course, a page for every run with Run again from the failed step, emails when an automation fails or is paused, Search, Recent work, and limits by plan on how many are on and how many runs a month.

Two independent reviews, of the engine and of the pages, were made, and what they found was fixed.