Automations.
Follow-ups and reminders that run themselves, and a clear record of everything they did. This guide walks through building an automation, testing it safely, publishing it and following every run.
What automations do
An automation reads like a sentence: when this happens, wait or check something, then do that. When a proposal is sent, wait for the client to view it, and if two business days pass without a look, email them. When a booking is confirmed, start the planning. Each automation is about one kind of record - a lead, an event, a contact, or the business as a whole - and each time it starts for one of them, that is a run.
A new automation is a draft, and a draft never runs. Nothing happens until you publish it, and publishing never reaches back: activity from before it was switched on does not start a run, so switching an automation on can never send a pile of late messages.
The Automations page
Automations in the sidebar (under More on a phone) opens the page that answers what is running, and what needs you. At the top, All automations running says whether anything is stopped - it reads All automations stopped after Stop all - beside Import and New automation. Under them the page has two tabs. Automations lists every automation, with Needs attention and Last 30 days. Activity lists every run of every automation, newest first; its count is the runs that need you.
- Needs attention. On the Automations tab, and only when something needs you. Each line says what is wrong, where, and carries the one button that fixes it - runs to review, a channel that cannot send, a setting an automation needs, people a run is waiting on.
- Last 30 days. What your automations did: runs started and finished, runs waiting now, messages waiting to send, runs that need review and goals reached. Activity, never revenue.
- Your automations. Filter by All, On, Off, Draft or Archived, by category, or search by name. Sort by what needs attention, name, last edited or what is running. The filters live in the address, so a link opens the same view.
- Open one. Click a row to open the automation. Its switch turns a published automation on or off, and its menu clones it, exports it, switches it off or on, archives it, or deletes a draft that was never published.
- Activity. Every run, newest first. Choose All, Needs attention, Waiting, Scheduled, Paused, Finished or Ended early, and narrow it to one automation with Automation. The filters live in the address too, so a link opens the same list.
On a laptop or a bigger screen Needs attention and Last 30 days stand in a column beside the list, so more of your automations fit on screen; each row says what it does in one line, and the list shows 50 at a time with page numbers under it. On a 27" or 34" screen the list adds Category and Runs for columns, stops at a width you can read across, and the two cards sit side by side beside it. Where there is no room for the column, Last 30 days is one short row of counts above the list. On a phone or an iPad held upright the automations are cards - two across on an iPad - 20 at a time, with Load more automations under them.
On, Off, Draft and attention
Every automation has one status, shown as an icon and a word: On (published and starting runs), Off (published, starting nothing new), Draft (never published) or Archived. Beside it, the version that is live - v3 live - or Draft changes once you have edited it since that version was published.
Attention is a separate signal, so an automation can be On and still need you: runs that need review, a channel that can’t send, a setting it needs (such as business hours or texting), or runs that wait for a person.
An Admin switches a published automation off or on from its row, or with Switch off and Switch on beside Publish in its header. Switching off always stops new runs from starting. When runs are in progress it asks first: let them finish, or hold them where they are until it is switched back on - a held run picks up exactly where it stopped, and nothing is lost. Switching on starts with new activity from that moment - nothing that happened while it was off is caught up.
Creating an automation
- New automation. Give it a name and choose what it is about: a lead, an event, a contact, or the business. It starts as a draft, and nothing runs until you publish it.
- Choose a trigger. What starts it - a lead coming in, a document being sent, a booking moving stage, a date approaching. A new automation opens on the Builder with Triggers first, ready to choose.
- Add the actions. Waits, checks, messages, tasks and notifications, in the Actions card or on the Canvas. Everything saves as you go.
- Test, then publish. Run a Simulated test against a real record, then publish it - switched on now, or switched off until you are ready.
- Clone. Makes a draft copy you can change without touching the original.
- Export. Downloads the automation as a .json file - to keep, or to bring into another business.
- Import. Brings an exported file in as a new draft. Stages, tags and people are matched to your own; anything that does not match becomes something to choose before it can be published.
The Builder and its five sections
An automation opens on three tabs: Builder, Canvas and Versions - on the Builder first. Moving between tabs keeps your place - a step you had open, the Test pane, the Issues list - and an edit still saving carries on saving. Its runs are on the Automations page’s Activity tab: See activity in the header takes you there.
The Builder reads top to bottom in five sections, each a label - its icon, its title and one line on what it is for - beside its card: Triggers (what starts a run), Re-entry (when the same record can start again), Schedule (when the run begins), Conditions (who can start a run, and what ends it early) and Actions (what happens, in order). Nothing in them is numbered. Where the window is narrow, each label sits above its card.
- Saves when you leave a field. There is no Save button. The header shows Saving, then Saved; if the connection drops, your changes wait and save when it is back. Every change is one step for Undo.
- One editor at a time. If someone else has the automation open for editing you see it view only, and can ask to take over. If two saves cross, you choose whose version to keep, or save yours as a copy.
- Nothing lost on a refresh. If the page closes before a change saved, opening the automation again offers to restore it.
On a 27" or 34" screen the header, the tabs and the Builder stand in one box: the editor, a wider Overview beside it, and Recent runs - the automation’s last eight runs, with See all for Activity. Test takes Recent runs’ place while it is open. On an iPad, or any window too narrow to keep the editor roomy beside it, Test opens in a drawer instead, and the header puts its buttons on a row of their own so the name is never cut short.
The Overview
The Overview reads the automation back in a few lines: what starts it and when, its actions in order, who can start a run, its Re-entry, and what ends a run. Under them, Before you publish ticks off what is done - Trigger configured, 3 actions added - and lists what still stands in the way, each with Go to for the section or step to put right; warnings that won’t block publishing are counted, with View, and once nothing blocks it says Ready to publish. With nothing to publish it says where the automation stands instead. Every line follows your edits as you make them.
On a wide screen the Overview is a column beside the editor that stays put while the editor scrolls; Hide overview puts it away, and Overview at the end of the tab row brings it back. On a laptop, an iPad, or any window too narrow for the column, Overview at the end of the tab row opens the same lines in a drawer, Workflow overview. It belongs to the Builder tab. While Test is open, Test takes the column’s place - unless a 27" or 34" screen has room for both.
The header: See activity, Publish, Switch off and ⋯
The header holds what belongs to the whole automation. Click the name to rename it; leaving the field saves. With it, the status says what is true now - On · v3 live, Off · v3, Draft · never published - and the save state. Under the name sit its category, a dropdown that can also make a new one, and its description, edited where it is read (Add a description when there is none). Both save the moment they change.
- See activity. First of the header’s buttons, on every tab: “4 running · See activity” while runs are in progress, “3 held · See activity” while the automation is switched off with its runs held, otherwise “See activity”. It opens the Automations page’s Activity tab narrowed to this automation.
- Issues. “2 to fix” while something blocks publishing. With nothing blocking, “Ready to publish” when there is something to publish; otherwise a warning count, or “No issues”. It opens the list, where Go to takes you to the section, step or field to put right. Issues never stop saving.
- The ⋯ menu. Late activity… ignores activity older than a number of hours, for activity that reaches automations late after an outage. Don’t run alongside… names a group: automations in the same group never run at the same time for one record - the second is skipped, not queued. Archive… puts the automation away.
- Switch off · Switch on. Switches the whole automation off or on at once, beside Publish. It is not an edit of the draft, so it works while someone else is editing. Switch off… asks first when runs are in progress; Switch on… asks first when runs are held.
- Publish. Publish the first time, then Publish changes only when the draft differs from the live version - otherwise there is nothing to publish and no button.
Archiving an automation with runs in progress asks whether to hold them as it archives, so nothing keeps sending; an archived automation shows Restore. Late activity and Don’t run alongside are part of the draft, so a change goes live when you publish.
Triggers
A trigger is what starts a run - any one of an automation’s triggers, unless they combine with and (below). Each trigger is a row that reads as its sentence - A form is submitted - and the sentence is the dropdown: click it to choose a different trigger in its place, keeping its conditions and where it leads. The list is grouped by topic and can be searched.
- Settings. A trigger’s own settings - which forms, which fields to watch, which kinds of document, which date - sit on its line, beside the sentence. Each says what it is set to, and an empty one says what empty means: All forms, Any field. A date’s When and a schedule’s Repeat open their controls in a panel that floats from the field.
- × removes it, with Undo. A removed trigger leaves “Removed … Undo” in its place until your next change. Remove the only trigger and its Start a run conditions wait for the next one you choose.
- There, or removed. A trigger is never switched off on its own, and never renamed: it is always its sentence. To stop the whole automation, switch it off in the header.
Between two triggers, the or | and toggle says how they combine, for the whole list: or, any one of them starts a run; and, a run starts once all of them have happened for the same record within the window set under the last trigger, Within, in hours or days. The run starts when the last of them happens, if the others happened in that window before it. Switch back to or and Within goes.
Add another trigger adds one more. A trigger named for a kind of document starts only for that kind: Proposal sent, Proposal accepted and Contract signed - a contract never starts a proposal’s automation, nor a proposal a contract’s. Document sent, Document signed and Document completed start for any document unless you pick kinds in their settings - Proposal, Contract, Invoice or Custom.
A trigger saved switched off in an older draft, an import or a restored version is never stuck: its row says Switched off: it doesn’t start runs. with Switch on beside it.
Re-entry
Re-entry, between Triggers and Schedule, says whether the same record can start a run again, as one sentence: Eligible to re-enter after 30 days, Never re-enters, Re-enters on every new trigger, Eligible to re-enter after the current run ends or Up to 2 runs at once per lead. A length or a count is set right in the sentence, and the line under it says what that means - “From the previous run’s start. A new matching trigger is required.”
⌄ at the end of the sentence opens the choices, under How often a lead can start this: Once per lead (or per event, per contact), Each time it’s triggered, Again after a waiting period, After the previous run finishes, or Several runs at once. A waiting period counts from the previous run’s start, not its end. A record that doesn’t match the conditions under Start a run never uses up its turn.
Schedule
The Schedule card says when a run starts after the trigger: Run immediately, as soon as the trigger happens, or Delay after trigger by a number of minutes, hours or days. With a delay, the line under them says what it means - “Runs start 15 minutes after the trigger. Entry conditions are checked when the trigger happens; stop rules apply during the 15 minutes.” While a run waits out its delay it reads Scheduled, with the time it starts.
When a message may go is set on the message itself: each email or text has its own Send window in its step settings (see Sending rules).
Conditions
The Conditions card has two rows, one above the other: Start a run and End a run. Each says in one line what is set - No entry conditions, 2 conditions · all must match, After the last action - with its buttons at the end of the same line. Its rules open beneath it, one line each - what it checks, how, and the value - with × beside it to remove it.
- Start a run. Checked once, when the trigger happens: a record that doesn’t match never starts a run, and isn’t counted for Re-entry. + Add condition adds one; from two, the or | and toggle between them says whether any one is enough or all must match - every toggle in a list changes together. + Add group adds an indented group that combines the other way. When the triggers have different conditions, each shows its own, with Use these for every trigger.
- End a run. + Add stop rule adds a rule that ends the run the moment it happens, even while the run waits - the client replies, a lead stage becomes Won or Lost - so stop rules always read “or”. Where a rule can reach wider, its Applies to says whose: this lead, or anything from this contact. With none, the row reads After the last action.
- The goal. Set a goal, on the End a run row, adds one line under Counts as done when - such as the lead stage is Booked. It is checked before each action, and reaching it ends the run and counts it as done. If a stop rule ends the run first (lead stage becomes Booked), the goal says it won’t count.
With no trigger yet, both rows read Choose a trigger first. Stop rules keep working while every automation is stopped: a run that is held can still end because the client replied.
Actions
The Actions card lists what happens, in order, one row per action, with a step’s paths indented under it. No step is numbered: each row is the step’s icon and its name, with a line under it on what it does, and the count under the section’s label says how many there are. A step that chooses or waits for something has paths under it, each labelled - It happened, Timed out, Yes, No, Otherwise - which fold and unfold.
Every path ends visibly. Continue with “Wait for a reply” means it carries on at that step, listed elsewhere, where two paths meet; click it to go there. End means there is nothing more to do. A path left open says This path ends with nothing else to do. with Add a step and That’s fine.
- Add. The + between two rows adds a step there, and above a step where paths meet, after the whole choice. + Add action adds one at the end.
- Each row’s ×. Click a row to open its settings underneath it. The × beside it deletes the step, and never asks: its cut-off paths go with it, and Undo stands in its place.
- Reorder. Reorder, under the section’s label - or a row’s grip - turns on handles: drag one, or click it or press Space and carry the step with the arrow keys; its paths move with it. A step whose paths end can only go last in a path. Done reordering turns it off.
- Switched-off steps. Steps are not switched off one at a time: to stop an automation, switch the whole of it off in the header. A step saved switched off in an older draft, an import or a restored version is stepped over when a run reaches it, keeps its settings, and shows Switch on on its row.
A step’s settings
Click an action’s row and its settings open underneath it, in a box of their own; the rows below move down to make room, and opening another step closes this one. The top line keeps the step’s icon and name - ✎ renames it there - with Done at its end. Done, Esc, or a click on that line closes the settings and puts you back on the row. On a long step the top line stays in sight as you scroll, so Done is always in reach. On the Canvas, a step’s sheet has a ⋯ menu - Duplicate, Move to… and Delete, with Switch on this step for a step saved switched off. A trigger’s offers Remove only.
A message to a client reads in the order you think in: Who it goes to (and what happens if there is no one), the Message with its Data Fill preview, and its Sending rules. More, closed until you open it, holds what most people never change - what to do when Text Data has no value, what happens if it isn’t sent, where each path goes next - and its closed line names every value and marks any problem inside.
Building on the Canvas
The Canvas tab draws the same automation as connected cards. On a wide screen the library on the left lists every step you can add - drag one in, or press it to add it after the selected step; on a laptop, + Add step opens the same list. Hover a connection and press + to put a step there. Branch connections carry their labels, and a path that joins another says which step it joins. A label never covers a step: where its line runs behind a card, the label moves along the line to a clear spot. View as a list (Steps), or the Builder tab, goes back to the sections.
Select a step or a trigger to open its settings in the panel on the right - the same settings as open under its row in the Builder. A trigger’s panel shows its Only start if conditions, the ones Start a run shows in the Conditions card; a change made there is for that trigger alone. A trigger saved switched off says Switched off, and its panel offers Switch on.
The toolbar zooms, fits the whole automation on screen, tidies it with Arrange, undoes and redoes, and finds a step by name. The minimap in the corner shows where you are on a large one. On an iPad its buttons are full-size for a finger, and on a 27" or 34" screen the Canvas opens a short automation closer up.
The Canvas needs a screen at least 1024px wide, so a phone or an iPad held upright has no Canvas tab. Opened there, a Canvas link shows the Builder instead and says so in one line at the top: “The Canvas needs a wider screen, so this is the Builder.”
Builder or Canvas
The Builder - the five sections - and the Canvas are two tabs on one automation. Moving between them converts nothing and loses nothing: the step you had open stays open, its settings are the same in both, and the Test pane, the Issues list and Undo carry over. An automation always opens on the Builder; a link to its Canvas opens the Canvas.
Text Data in messages
Emails and texts are written with Text Data, the same fields documents use: + Text Data inserts a chip such as the client’s first name or the event date, filled in from the record when the message goes. The Data Fill preview shows the message with a real record behind it, so you can read exactly what a client would. The Text Data guide covers every field.
Waits and timing
- Wait a length of time. Minutes, hours or days - calendar days, or business days counted only on the days you are open.
- Wait for a moment. A time before or after a date on the record - an event’s start, a lead’s event date, a task’s or an invoice’s due date - such as 7 days before the first event day at 9:00 AM. A new wait starts from the record’s own date. You choose what happens if that time has already passed, and if the record has no date yet.
- Wait for something to happen. Such as the client viewing a proposal, with a time limit; the step then has two paths, It happened and Timed out.
Business days and business-hours sending need your business hours, which you set once in Settings → Automations - until they are set, an automation that counts business time cannot be published. Times are worked out in the record’s own time zone, and every time an automation shows you says which zone it is in.
Sending rules
Every message step has a purpose - sales follow-up, operational, billing or marketing - and rules that follow from it. A sales follow-up pauses when the client replies, so nobody gets chased after answering; billing reminders do not. A send window keeps a message to business hours or hours you choose, set on each message. Texts also wait out your business’s quiet hours in the client’s time zone - emails too, once you turn email quiet hours on - and useful until drops a message that would arrive too late to matter.
Some checks are always on and cannot be switched off: unsubscribes and do-not-contact are respected, and one step sends a client one message, never two. A step is due when its turn comes; it sends when every rule allows it, and the run shows both times when they differ. A run whose message is put off until it may send reads Waiting to send.
Testing safely
Test in the header runs the automation as it is now, Simulated, in a pane beside the Builder or the Canvas - the button looks pressed while the pane is open. On a 27" or 34" screen the pane stands where Recent runs was; on an iPad, or a window too narrow for it beside the editor, it opens in a drawer. Test it with a real record (it is read, never changed) or A sample lead, made up for the test; set the moment with Pretend it’s, then press Run test. Where the run waits for the client, choose what they do - view the proposal, reply, or nothing - or skip ahead on the clock. The results show each step in order and when each message would send.
Nothing is sent and nothing is created in a Simulated test: no emails, no texts, no tasks, no notes. If you change the automation after a test, the test says “You’ve edited since this test.” with Run again.
Publishing and versions
Publish checks the automation first. Problems that block publishing are listed under Must fix before publishing, each with a Go to or Go to step button that lands on the field to fix; things Worth a look are listed apart and do not stop you. The dialog shows what changes since the version that is live, and on a first publish you choose Switch it on now or Publish it switched off. Publishing an automation that is off keeps it off until you switch it on.
Each publish makes a numbered version. Runs already in progress finish on the version they started on; new runs use the new one. The Versions tab lists every version with its note, compares any two - or a version and the draft - and restores an older one as the draft for you to publish again. Steps that change bookings or other high-risk records can only be published by the Owner. On a 27" or 34" screen Compare also draws the two versions side by side under what changed, so you can see each change in place.
Activity and what happened in a run
Every run is on the Automations page’s Activity tab, newest first. Choose All, Needs attention, Waiting, Scheduled, Paused (a run someone paused, or one held while its automation is switched off), Finished or Ended early (a stop rule ended it, or someone cancelled it), and narrow it to one automation with Automation. See activity in an automation’s header opens it already narrowed. Narrowed to one automation it also offers Simulated: the runs from testing, never mixed in with real ones. Scheduled shows the runs still in their Delay after trigger, soonest start first. On a phone the runs are cards grouped by day, with the filters in a sheet.
Open a run - from Activity, from Recent runs, or from a lead’s, event’s or contact’s Automations card - to see why it started, what happens Next (when it is due and when it can send), and its full timeline; Back returns to where you opened it. Before anything sends it is checked again, so a run that was due to email a client who has since replied, or unsubscribed, says it skipped the step and why. Narrowed to an automation that is switched off with its runs held, Activity says so above the list - “It’s switched off with 3 runs held. They pick up where they stopped when you switch it on.” - with Switch on…; the automation’s header reads 3 held · See activity, and each of those runs reads Held.
On a 27" or 34" screen a click on a row in Activity previews that run beside the list - who it is for, what happens next, why it started and what happened - without leaving the list; the arrow keys move through the runs, and Open, Enter or a double-click opens the run itself. The preview changes nothing; pause or cancel a run from its ⋯ or its own page. On a 34" screen the preview shows what happens next beside the timeline. A run opened on such a screen reads in three columns: its steps, the timeline, and who and what is next. A run’s Canvas opens at a size you can read, from the start of the run; Fit shows all of it.
- Put off and skipped. A step waiting to send is waiting for a send window, quiet hours or a channel; it sends by itself when it may. A skipped one says which rule skipped it. The timeline’s Put off & skipped filter shows just these.
- Needs review. A step that could not finish stops and waits for a person. Retry it once the cause is fixed, or cancel the run.
- Pause, resume, cancel. Pause a single run and resume it later, or cancel it. Simulated runs are labelled Simulated everywhere they appear.
On a lead, event or contact
The Overview of every lead, event and contact has an Automations card listing what is running for that record and what finished recently, with when each runs next. Pause one run from the card - it works the same on a phone - or open it to see everything it did. On a desktop the link under the list, named for the latest run’s automation - See all Proposal follow-up runs - opens Activity narrowed to that automation, for every client.
For each run, the card shows what it is waiting for and when it runs next, and it lists what finished in the last 30 days. Opening a run shows why it started as well as everything it did. Runs labelled Simulated are tests: they never send anything or change the lead, event or contact.
When the client replies, automated sales follow-ups to them stop, and the card opens with Follow-ups paused: who wrote, how and when, and what still goes - invoices and event reminders keep sending. A matching pill sits in the lead’s, event’s or contact’s header on every tab; press it to jump to the card, or See reply to read what they wrote. A reply filed on the client’s only open lead or event also pauses the sales follow-ups of automations that run for the client as a whole. When a reply cannot be matched to one automation, the follow-ups wait for a person, and an Admin, the client’s contact owner or the teammate their conversation is assigned to can press Hand back to automations. A run whose next message will not go says why in place of its time - the client replied, someone on the team wrote to them, or it is waiting for a person.
Stopping everything
If something is going wrong, Stop all automations… holds every automation in the business at once: no run moves and nothing sends until it is lifted. It is in the All automations running menu at the top of the Automations page, and on the Stop all automations card in Settings → Automations. Stop rules still apply, so a held run still ends when, say, the client replies.
Once stopped, the menu reads All automations stopped and the page says who stopped them and when. The Owner or an Admin can stop; only the Owner can resume, with Resume all automations…. A Member sees whether they are running, with no menu. Resuming lets held runs carry on under the same sending rules, so a message past its useful-until is skipped rather than sent late.
Settings for every automation
Settings → Automations holds the rules every automation in the business shares: your business hours (for business days and business-hours sending), quiet hours for texts and, if you want them, for emails, how long automated sales follow-ups and marketing step back when someone on your team writes to a client themselves, and the sending limits that cap how much the business sends in a minute. A message kept to business hours before they are set says so under its Send window, with Set business hours to take you there.
Who can do what
- Members. See every automation and run, and can pause a single run.
- Admins. Build, test and publish automations, switch them off and on, archive them, and change Settings → Automations.
- The Owner. Everything an Admin can, plus publishing high-risk steps and resuming after Stop all.
On your phone and iPad
An iPad edits automations, held either way: from 768px wide the Builder is the full editor, with large controls for a finger, Test in a drawer and the Overview behind its button. The Canvas needs 1024px, so an iPad held upright edits in the Builder. Only a phone reads automations without changing them.
On a phone the Automations page shows each automation as a card, with Filter & sort in a sheet, and Activity shows each run as a card, grouped by day. An automation opens for reading: its header says its status, Switch off… or Switch on for an Admin, See activity with how many runs are going, and Edit on a larger screen. Its ⋯ moves between Builder and Versions. Below are the same five sections with their icons - Triggers, Re-entry, Schedule, Conditions and Actions - every value in words. A trigger’s settings read one per line under its sentence - Fields to watch Stage, Source - Re-entry says when the same record can start again, and Schedule says when a run starts. Tap an action to read its settings under it.
- Built for the thumb. Large controls, nothing hidden under the bottom navigation, and no sideways scrolling.
- Needs attention travels with you. The same attention lines lead the page, each with the button that fixes it. You can see runs, pause a run, and stop all automations.
Keyboard shortcuts
The Builder and the Canvas work fully from the keyboard. F6 moves between the header, the Builder or the Canvas, the Overview’s column and Recent runs where they show, and a pane on the right, and a ring shows which one you are in. On a Mac, use ⌘ for Ctrl and Option for Alt. In Reorder steps, Space picks a step up, the arrows carry it, and Space or Enter puts it down - Esc puts it back.
In the Actions card
- ↑ ↓. Previous or next row
- → ←. Open or close a path, or go into a step’s paths and back out
- Home / End. First or last row
- Enter. Open or close the step’s settings under its row (Esc closes them)
- Alt ↑ / Alt ↓. Move the step one place, into and out of paths
- A or +. Add a step after this one
- Delete. Delete the step - Undo stands in its place
- Ctrl D. Duplicate the step
- Ctrl Z · Ctrl Shift Z. Undo · Redo, anywhere in the Builder (a text box keeps its own undo)
- F6. Move between the header, the Builder, the Overview, Recent runs and the Test pane
On the Canvas
- ↓ ↑. Follow the connections down or back up
- ← →. Move between paths side by side
- Home / End. Go to the start or the end of the path
- Enter. Open the step in the panel (Esc comes back)
- A or +. Add a step after this one
- Delete. Delete the step
- Ctrl Z · Ctrl Shift Z. Undo · Redo
- Ctrl D. Duplicate the step
- Ctrl F or /. Find a step
- Shift 1. Fit the whole automation on screen
- = / −. Zoom in · Zoom out
- Alt + arrows. Nudge the step
- F6. Move between the header, the canvas and the panel
- ?: Show every shortcut
- Announced as you go. Screen readers hear each move, add, undo and redo - “Moved to step 2”, “Undid: delete step”.
- Paths open and close. In the Actions card, the right and left arrows open and close a path, so long automations stay readable.
- Nothing sends from the Builder. Editing, testing and switching tabs never send anything; only a published automation that is on does.
- Delete leaves an Undo. Deleting a step never asks: its paths go with it - and where they meet again, that step and everything after it stay - and Undo in its place brings everything back.
- Archive keeps the history. An archived automation starts nothing, and keeps every run and version.
- Tests stay tests. Simulated runs never touch a client or a record.