Skip to content
Knowledge base

Automation

Configure available recipes and follow approvals, outcomes and recovery.

5 min read · 3 sections
On this page

Recipes and authority

/app/<orgSlug>/automation shows the person's responsibility, contributing work areas, recipes, approval inbox, exceptions and run evidence. automation.view, automation.manage and automation.approve are distinct. Target products must be enabled and the actor must retain their source authority. Unsupported effects are unavailable until their delivery and review paths exist.

The general builder creates internal work using a manual trigger, periodic schedule or authenticated connector signal. It includes recipe name/description, interval or connector key, optional signal-text condition, delay, per-run approval, daily run limit, optional stop-after count/date, and task title/summary/priority. The chosen effect uses the applicable legacy or explicitly adopted Tasks backend.

  1. Create or edit a draft recipe.
  2. Test the draft and inspect the proposed internal effect.
  3. Publish the tested version.
  4. Trigger manually, wait for its schedule or send an authorized connector signal.
  5. Review any required approval and inspect run evidence.
  6. Pause the recipe if exceptions need investigation; resume or retire deliberately.

Published versions remain frozen. Changes require a new draft version, test and publication. New Tasks adoption does not rewrite old published versions or retries. Connector keys are shown when created/rotated; rotation invalidates the previous inbound key immediately. A connector signal does not bypass conditions or approval.

The scheduled worker selects recipes with an explicit due time. Published manual/connector recipes do not occupy or repeatedly restart its scheduled queue. Legacy undersold-rule initialization selects each unscheduled rule once per sweep.

Event task lists

An Event preparation recipe can contain 1–30 checkbox tasks. From Event Operations → Automation, create an event prep draft, then edit it in Manage recipes. Add a task title, optional instructions and an assignment for each item. Existing single-task drafts offer Turn this into a task list; the first item keeps the old title and instructions and needs its assignment reviewed. Saving does not create work: test the draft, publish it, then use its chosen trigger. Changes apply to new runs, not previously generated tasks.

The assignment selector disables rota roles when Rotas is not enabled with a current subscription, or when the Event's venue/time routing cannot be read. Guidance explains the missing prerequisite. Existing role names and task details remain in the draft; choose a person or open assignment, remove that item, or restore the prerequisite before saving. Open and person tasks remain saveable without Rotas. A current rota with no published role suggestions still permits a new role; no matching shift remains a separate waiting-for-cover state. If Rotas becomes unavailable after the choices load, saving refuses with readable guidance and keeps the draft. This correction does not enable Rotas or grant access.

Each task can target a specific person, a rota job role, or anyone on the event team. People must have an active business account and current Event access. The role is the function used on the rota (for example, Duty manager), not an employment position. Current published shift coverage, including confirmed and completed assignments, at the Event's venue and overlapping its start/end determines recipients; when no end is recorded, coverage is checked at the start. Draft/cancelled shifts and ineligible people do not count. Completed shifts still allow their eligible staff to finish closing tasks. Missing cover stays visible as No matching published shift; it does not become an open task. Rota changes refresh pending recipients through the bounded one-minute recovery worker; a large backlog can take longer. Completion and private attention access recheck the current source and recipient immediately.

Event Operations → Tasks shows generated jobs and their completion count. Assigned people see their work in My Work, linking back to that Event view. Open jobs are available to Event team members with Complete open Event tasks (ticketing.tasks.complete) or existing event-management access. A read-only Event viewer can view open work but cannot complete it. One person checking an item completes the shared job even if several people cover its role. Unchecking reopens it under the same current-recipient rules. Stale revisions require a refresh. Missing source access makes tasks unavailable; incomplete list windows are labelled and their counts must not be treated as the entire Event total.

Recipe authoring retains Automation management plus exact Event management permissions. Reading the Event's operational checklist uses current Event view. Completion also requires the open-task permission above or the item's current direct/rota assignment. It does not require Automation authoring or silently enable core Tasks adoption. Existing single-owner recipes retain their previous lifecycle. Web provides authoring and checkboxes. Native My Work can link to the Event route, but this change does not add a native checklist editor or establish installed-device acceptance.

Development-only /event-tasks-preview uses fictional people and jobs, with no task creation or notifications. In the desktop preview, the left panel defines each task and target; the right panel shows shared completion. The narrow dark preview shows an uncovered role remaining visible with its checkbox disabled.

Approval and recovery

An approval card shows requester, owner, scope, trigger facts, frozen action, delay and limits. Approve frozen run approves that exact proposal; rejection requires a reason and creates no effect. Managers and approvers may be different people under the relevant policy.

Runs show their outcome and evidence. Exceptions are grouped by root cause to avoid a wall of identical alerts. Safe replay uses retained run identity and source semantics; compensation is an explicit supported recovery action, not an arbitrary reversal. A paused/invalid owner or policy does not trigger a backlog of uncontrolled missed runs.

Ticketing's built-in confirmation, waiting-list and attendee communications remain Ticketing-owned and do not require Automation subscription. The existing Ticketing-rule table retains earlier undersold-Event discount rules for operation and audit. An eligible active legacy rule can only be paused; new creation, reactivation, editing and deletion are unavailable there. New work uses versioned recipes. Customer event recipes retain CRM eligibility and current source consent. Automation Orders routes expose authorized contributed commerce records, not a new seller or independent payment ledger.

The native Automation home presents current runs and permitted approval decisions. Recipe authoring and specialist settings continue through the authorized web workspace. Native approval requires an online connection and the same displayed frozen version.

Available features depend on your workspace, permissions and connected services. Preview and setup requirements are described in each guide.

Back to the knowledge base