Building a trigger and its steps by hand works, but it isn't the only way in. Open a canvas, type what you want in plain language, and your assistant drafts the whole thing so you're editing a draft instead of starting from an empty board.
Watch Mandric walk you through this topic
12:47Describe It in Your Own Words
Type the outcome you're after the way you'd say it out loud: "text the client three days after their file moves to conditions, then follow up by email a week later if they haven't replied." You don't need trigger names or step types; your assistant maps your sentence onto the pieces Pulse actually runs on, including the moment that starts it, each step, and its timing.
Watch It Take Shape on the Canvas
As your assistant works, the trigger and its steps appear on the canvas in front of you rather than behind a loading spinner. You see the moment it chose to start the automation, the steps it added, and how it timed each one, all before you've approved anything. Nothing runs and nothing sends while it's still drawing.
Answer the Questions It Asks Back
A sentence is often missing a detail Pulse needs, like which board a stage lives on, or whether a step should send automatically or wait as a draft. Rather than guess, your assistant asks, and you answer in the same conversation. Each answer narrows the build further, and you can correct a wrong assumption the same way, in plain language, instead of hunting for the field yourself.
Why It Writes a Template Instead of Inline Copy
Every message step on a canvas points at a template rather than carrying its own written wording, and that holds for a step your assistant adds too. Describe a message you want sent and it writes or attaches a template for that step; it cannot leave a step holding raw copy of its own. That keeps every message reusable and editable from the same place your hand-built steps already live, the template library.
Edit What It Drew, Then Save
Nothing your assistant builds is final until you say so. Open any step it added and change the timing, the recipient, or swap the template, exactly as you would on a step you built yourself. The automation saves switched off, the same as any other, so arming it is still your own separate press once you're satisfied with what it drew.
What to Do Next
- Group Automations Into Canvases to keep what your assistant builds filed under the same theme as the rest of your board.
- Test an automation before you switch it on, so you watch a full run land safely before a client ever sees it.
- Write an automation template if you want to hand your assistant polished copy to reach for instead of a fresh draft.