Advanced Pulse is where every broker builds now, and a board holding dozens of automations reads as noise once nothing separates one theme from the next. A canvas is a named group: file every renewal touchpoint into one, every lender-specific follow-up into another, and the board reads as a handful of themes instead of one long list.
Watch Mandric walk you through this topic
12:47What a Canvas Is
A canvas is a folder for automations, nothing more. It carries a name and a place on your board, and the automations filed inside it run exactly as they would if the canvas didn't exist. Grouping changes nothing about what fires or when; it changes only what you see when you open Pulse. Instead of scrolling one long list, you open the canvas whose name matches the theme you're after.
Create One and Move Automations Into It
Press New Canvas from the library view and name it after the theme it holds, then open it to start building fresh inside it. An existing automation moves in from its card menu, and you can drag automations between canvases the same way you'd file a document into a different folder. Nothing about a trigger, a step, or a template changes when it moves; only the group that claims it changes.
Open One Automation or the Whole Canvas
Click an automation's card in your library and the board opens holding just that automation, in the middle of the board, so you can read and edit it without the rest of the canvas around it. Press Add Automation there and the new one appears beside it and is saved into the same canvas. Open on the canvas itself shows every automation in the canvas side by side, in the order a file meets them.
The round jump button in the toolbar lists every automation in the canvas, each marked On, Off or Test Mode. Pick one to go straight to it. At the bottom, This One shows only the automation you are working on and Whole Canvas shows them all, whichever way you opened the board. Hiding an automation only hides it from view: anything you have not saved yet stays unsaved and is still saved when you press Save all.
Ungrouped Is Not a Problem to Fix
Every automation built before you started using canvases, and every simple one-off you build today, sits in Ungrouped rather than inside a named canvas. That's the honest default, not a backlog waiting to be cleared. An automation left in Ungrouped runs exactly the same as one filed away neatly. Grouping earns its keep once a theme holds enough automations that finding one by name beats scrolling for it; a single reminder automation rarely needs a canvas of its own.
The Switch on a Canvas Header
A canvas header shows a switch, but a canvas holds no on or off setting of its own. What you see is worked out from the automations filed inside it: on when every one of them is enabled, off when none are, and a mixed position when the canvas holds a blend of both. Flip the header switch and it writes to every automation inside the canvas in one pass, rather than asking you to open each one and toggle it by hand.
Renaming or Deleting a Canvas
Rename a canvas any time from its settings without touching anything filed inside it. Delete one and its automations go with it, archived rather than left behind loose in Ungrouped, so nothing keeps running under a name you just removed. Reopen the canvas from your archive if you change your mind, and everything it held comes back with it.
What to Do Next
- Describe an Automation to Your Assistant to have a new build land inside the canvas you're already looking at.
- Branch on What the Client Does to give one automation in a canvas a different arm for a reply than for silence.
- Test an automation before you switch its canvas on, so a full group goes live only once you've watched a build fire safely.