For the complete documentation index, see llms.txt. This page is also available as Markdown.

🪄Start From a Wizard

Start-here plus the first win on Automation Home. Deep catalogs stay one click away. Do not grow this into a sixth automation book.

What this is / when to use it

Automation Home is the first surface. The goal is a visible live success in about five minutes.

Automation is three jobs:

Job
Meaning

Workflow

Does the work

Messaging

Tells people

Approvals

Gets a human decision

Use the wizard when you have never shipped a notify or an approval. Use Foundation builders after the first win when you need custom steps, channels, or multi-route repair.

Before you start

A form or button exists. The right entitlement is on, or you are ready to Request access from the locked panel (the checklist stays visible while a request is pending).

Build it

Home checklist:

  1. Pick a job

  2. Connect the trigger

  3. Choose who receives it

  4. Add the screen people will use

  5. Run a live test

Primary CTAs above the advanced outcome builder:

  • Create your first automation: Notify someone

  • Create your first automation: Get an approval

Freeform “Describe your own outcome” stays under Advanced.

Notify someone

  1. Select the form/screen trigger (prefilled when possible).

  2. Choose recipient: record owner / people field, role pool, or a specific email.

  3. Choose channel: in-app Notification Center, email, or both.

  4. Add Notification Center with one click if it is missing.

  5. Run live test → open Notification Center / Activity.

  6. Optional: Turn this into an approval.

Get an approval

  1. Confirm When this happens + submitted status.

  2. Create or repair the approval workflow.

  3. Confirm Approval Inbox / Decision visibility for Approver.

  4. Create a test request.

  5. Complete only when the request appears in the inbox.

Every control

Control
What it does

Notify CTA

First-win notify route

Approval CTA

First-win approval route

Request access

Workflow / Messaging / Approvals

Advanced describe

Freeform, demoted

Simulate

After first win, on the route

What users see

A notification or a decision item. They never see “wizard.”

Limits and plans

Locked families need access. Wizards will not bypass Messaging levels or Approval toggles.

Example

First morning: Notify someone on Add request → owner + Notification Center. Afternoon: turn that into an approval and add the Decision screen for managers.

Fix problems

No item after test: automation not published, or screen visibility. See troubleshooting FAQ stubs (one paragraph each) and the Decision/queue page.

Full reference → Which automation, Trigger catalog, Messaging — topics that perform work, Approval workflows.

Last updated