Copilot
The Copilot is an assistant built into the workflow editor. You describe what you want in plain language, and it builds it on the canvas for you — adding blocks, connecting them, and filling in their settings while you watch.
It's the fastest way to get from an idea to a working draft. You stay in control the whole time: the canvas is protected while it works, nothing is switched on without your approval, and the last set of changes it made can be reverted with one button.
Where to Find It
Open a workflow in the editor and switch the right-hand side panel to the Copilot tab. (The other tab, Toolbar, is the block palette — see Toolbar & Controls.)
Before you've asked for anything, the panel shows:
Build with the Copilot "Describe what you want — e.g. "Add a Slack node and connect it to the trigger." The copilot edits the canvas for you."
:::info Save the workflow first The Copilot works on a saved workflow. Until the workflow has been saved at least once, the message box is switched off and the panel reads "Save the workflow to start using the Copilot." Click Save in the panel header (or press ⌘/Ctrl + S) and the Copilot becomes available. :::
Using It
- Switch the side panel to the Copilot tab.
- Type your request in the box at the bottom — it prompts you with "Ask the copilot to build or change the workflow…".
- Press Enter to send. (Use Shift + Enter if you want a line break instead.)
- Watch the canvas as the Copilot works. Blocks appear, connect and get configured live.
A good first request is a single, concrete change:
"Add a Slack node and connect it to the trigger."
What the message box tells you
| State | What you see |
|---|---|
| The workflow isn't saved yet | "Save the workflow to start using the Copilot." — the box is switched off |
| Ready for your request | The box invites you to "Ask the copilot to build or change the workflow…" |
| A request is being worked on | The box reads "Copilot is working…" and is switched off; the send button becomes Stop |
Watching It Work
While the Copilot is building, the panel narrates what it's doing right now, one line at a time.
| You'll see | What's happening |
|---|---|
| "Inspecting the workflow…" | It's reading what's currently on your canvas |
| "Finding the right block…" | It's looking for the block that fits your request |
| "Checking block options…" | It's reading a block's available settings |
| "Updating the workflow…" | It's applying the change to your workflow |
| "Checking your connections…" | It's looking at the accounts and keys you've set up in Connections |
| "Reading the last run…" | It's opening your most recent run to see what happened |
| "Proposing a schedule…" | It's preparing a schedule for you to approve |
Between those lines you'll see a "Thinking…" pulse with a small step-and-seconds counter, so you can always tell it's still going on a longer request.
The canvas is protected while it builds
While a build is in progress a banner appears over the canvas:
"Copilot is building — canvas is read-only to protect your changes"
During that time you can't drag, connect, select or delete blocks, and Run is switched off with the reason "Copilot is building — please wait". If you try the run shortcut anyway, you're told "Copilot is building this workflow — wait for it to finish before running."
On the Workflows list the same workflow shows a Building badge in place of its usual status, so you can see a build is under way even from outside the editor.
Stopping
Click Stop (the send button turns into it while a request is being worked on) to cancel what the Copilot is doing. The panel returns to normal and you can type a new request.
:::tip You don't have to sit and wait A build keeps going even if you leave the editor. When you come back to the workflow, the Copilot reconnects to the build that's still running and replays its progress and reply, so you don't lose the result of a request you walked away from. :::
What It Can Do
| Ask it to… | What it does |
|---|---|
| Add a block | Puts the block on the canvas for you |
| Connect blocks | Draws the link so the flow runs in the order you described |
| Configure a block | Fills in that block's settings |
| Remove a block | Takes it off the canvas |
| Look at what you've built | Reads the current workflow before it changes anything |
| Find the right block | Searches the available blocks and picks the one that fits |
| Check your connections | Looks at the accounts and API keys already set up |
| Explain the last run | Reads your most recent run to see what happened |
| Put it on a schedule | Proposes a schedule for you to approve — see below |
Starting a run is still your call: build it with the Copilot, review it, then click Run yourself. See Running Workflows.
Approving a Schedule
If you ask for something like "run this every weekday at 8am", the Copilot doesn't switch anything on by itself. It shows an approval card instead:
Approve this schedule?
The card repeats your own words and then shows exactly what would be created:
| Row | What it shows |
|---|---|
| Cron | The recurrence pattern it worked out from your request |
| Timezone | The timezone the schedule would run in |
| Next run | The date and time it would fire next |
Then choose:
| Button | What happens |
|---|---|
| Reject | The card is dismissed. Nothing is created |
| Approve & activate | The schedule is created and starts running |
Nothing is scheduled until you press Approve & activate. If the schedule can't be created you'll see "Could not create the schedule. Please try again." — try once more, or set it up yourself on the Schedules tab.
Undoing the Last AI Change
After the Copilot edits your workflow, a card appears in the panel:
Last AI change · 3 edits
Click Undo and you're asked to confirm — "Revert the last AI change? This restores the workflow to before that build." Choose Cancel to keep the changes, or Revert to roll them back. The workflow returns to exactly how it was before that build, and the canvas refreshes to show it.
- The card is hidden while a request is being worked on, so an undo can never collide with a build in progress.
- The offer stays with the workflow, not with the panel — reopen the workflow later and the Undo card is still there for the last build.
- This is different from the canvas Undo (⌘/Ctrl + Z), which steps back your own individual edits. This card reverts the Copilot's whole last build in one go.
:::caution If you've edited the workflow since the build The revert is refused rather than overwriting your own work. You'll see "The workflow changed since this build — undo is not safe. Reload to see the latest." Reload the workflow to see the current version, then remove the parts you don't want by hand. :::
Your Conversation Is Kept
Each workflow has its own Copilot conversation, and it's kept between visits. Reopen the workflow and your earlier requests and replies are still there, so you can carry on from where you stopped instead of re-explaining what you're building.
Switching to a different workflow shows that workflow's own conversation.
When Something Goes Wrong
| What you see | What it means | What to do |
|---|---|---|
| "Save the workflow to start using the Copilot." | The workflow has never been saved | Click Save, then type your request |
| "Copilot is building — canvas is read-only to protect your changes" | A build is in progress | Wait for it to finish, or click Stop |
| Run is switched off, "Copilot is building — please wait" | The same — you can't run mid-build | Wait for the build to finish, then run |
| A red message in the panel | The request couldn't be completed | Dismiss it with the ×, then rephrase and send again |
| "The workflow changed since this build — undo is not safe. Reload to see the latest." | The workflow was edited after the Copilot's build | Reload the workflow and undo the unwanted parts yourself |
| "Could not undo. Please try again." | The revert didn't go through | Try Undo again |
| "Could not create the schedule. Please try again." | The approved schedule wasn't created | Try again, or create it on the Schedules tab |
Getting Better Results
- Be specific. "Add a condition that checks whether the email subject contains 'invoice'" gets you further than "add a check".
- Name the service. If the step involves Slack, Gmail or Notion, say so — the Copilot can pick the right block straight away.
- Build in steps. Ask for one change, look at what appeared on the canvas, then ask for the next. Small requests are easier to review — and easier to undo.
- Say what should come first. Describing the order ("…and connect it after the agent") saves you rewiring the canvas afterwards.
- Set your connections up first. A block that reaches an outside service needs an account or key from Connections. The Copilot can add the block, but only you can sign in.
- Review before you run. Open the blocks it configured and check the fields — especially anything that sends a message or writes data.