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, every change it makes is listed, 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.)
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."
:::tip Save your own edits first The Copilot works on the saved workflow. If you have unsaved edits when it changes the workflow, a Copilot updated this workflow dialog makes you choose between Apply Copilot version — your unsaved edits are discarded — and Keep my edits. Pressing Save before you send a request avoids the choice. :::
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 |
|---|---|
| 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 a stop button |
| Someone else is building this workflow | The box is switched off and names them: "… is building — you can send once they finish" |
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 |
| "Looking at your tables…" | It's checking which tables you have |
| "Searching the web…" | It's looking something up online |
| "Checking the date…" | It's reading today's date and time, for example before proposing a schedule |
| "Thinking it through…" | It's working out the next step |
| "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 |
| "Working…" | Anything else |
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 list of changes
The Copilot doesn't only tell you what it did — the panel lists it. Under its reply you find a line such as Applied to the canvas · 3 changes, followed by one row per change: a block added, a block edited, a block deleted, a connection made or removed.
- The list builds up live while the Copilot works, so you watch the edits land.
- Once the build is finished, click a row to be taken to that block: the canvas moves to it, selects it and highlights it. Rows for a deleted block or a connection can't be clicked.
- If the block has been removed since, you're told "That block is no longer on the canvas."
- The blocks a build added are highlighted on the canvas for a few seconds when it finishes.
If a reply and the list ever disagree, trust the list: it is the record of what was actually changed.
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 the stop button (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.
Stopping does not undo what was already done. If the Copilot had changed the canvas before you stopped it, the conversation shows "Stopped — but these changes had already been applied." with the list of those changes.
:::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. :::
When Someone Else Is Building
Only one build can run on a workflow at a time. If another person started one, you see it in three places:
| Where | What you see |
|---|---|
| Banner over the canvas | "… is building with the Copilot · started 12 min ago — canvas is read-only", with a Stop button |
| Copilot panel | Someone else is building, and a note that their conversation is private — nothing of it is shown to you |
| Message box | Switched off: "… is building — you can send once they finish" |
The canvas is read-only for you until their build ends. You can wait — or stop it:
- Click Stop on the banner.
- A Stop this build? dialog names the person and warns: "Stopping it discards the work in progress — anything already applied to the canvas stays."
- Click Stop the build. You see "Build stopped. The canvas is editable again."
:::caution Stopping someone else's build A build can represent a long piece of work. Stop a colleague's build only when you have to — and tell them. :::
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 |
| Use your tables | Looks at the tables you have, so it can wire a table step to the right one |
| Look something up | Searches the web when it needs outside information |
| Work with dates | Checks the current date and time |
| 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.
:::note On a workflow that is switched on The Copilot's edits are saved as a draft, like your own. The triggers keep running the published version until you click Publish changes next to the workflow title — see Publishing changes. :::
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 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 |
Under those rows a line starting "Copilot's wording:" repeats how the Copilot understood your request. Compare the two: the three rows are what will really be created, the wording is only its description. Next run is the quickest check that they agree.
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.
A schedule only fires while its workflow is Active. If the workflow is still switched off, the new schedule shows Inactive on the Schedules tab until you switch the workflow on.
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.
- The offer lasts 24 hours. After that the build can no longer be reverted, and trying tells you "This revert point has expired (they are kept for 24 hours), so nothing was changed."
- This is different from the canvas Undo (Ctrl/Cmd + 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.
- The conversation is kept in the browser you're using, for your account. On another computer or browser you start with an empty panel.
- The most recent 100 messages of each workflow are kept.
- Switching to a different workflow shows that workflow's own conversation.
Starting over
Once there is a conversation, a New conversation button appears at the top of the panel. Click it to clear the conversation for this workflow and start fresh — useful when the Copilot keeps circling the same misunderstanding. It clears the conversation only; the workflow itself is not changed. The button is hidden while a request is being worked on.
When Something Goes Wrong
A failed request leaves a red message in the conversation. It stays there, so you can still read it after you reload the page. Rephrase or simply send your request again.
| What you see | What it means | What to do |
|---|---|---|
| "Copilot is building — canvas is read-only to protect your changes" | A build is in progress | Wait for it to finish, or stop it |
| 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 |
| "The AI service could not be reached. Please try again." | The assistant couldn't be reached for this request | Send the request again. If it keeps happening, tell your administrator |
| "The copilot stopped responding (no activity for 90 seconds). It may still be working in the background — reopen this workflow to check." | Your browser lost touch with the build; the build itself may still be running | Go back to the Workflows list and open the workflow again |
| "Too many requests — please wait a moment and try again." | You sent requests too quickly | Wait a moment, then send again |
| "Your session has expired. Please sign in again." | You were signed out | Sign in again and reopen the workflow |
| "You do not have access to this workflow." | Your permissions changed, or the workflow isn't yours | Ask your administrator |
| "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 |
| "This revert point has expired (they are kept for 24 hours), so nothing was changed." | The build is more than 24 hours old | Remove the unwanted parts by hand |
| "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.
- Write a description for the workflow. The Copilot reads it first, so a sentence about what the workflow is for helps every later request.
- Review before you run. Read the list of changes, open the blocks it configured and check the fields — especially anything that sends a message or writes data.