Copilot and Canvas
Until now we’ve built everything by hand — picking triggers, choosing actions, wiring steps together. That skill still matters, but the way you start a build has changed. Zapier now lets you describe what you want in plain English and have it assemble the thing for you. It’s the difference between knowing how to lay bricks and being handed the walls. You still need to know what a good wall looks like.
Copilot: say it, and it builds it
Zapier Copilot takes a plain-English description — “when a new item lands in my Inoreader folder, summarise it and add it to my Signal table” — and builds the Zap, choosing the trigger, the steps and the connections. Zapier reports success rates around 92% for simple Zaps, which is to say: for the everyday stuff, it mostly just works.
What this changes is the starting line. Instead of staring at an empty canvas wondering which trigger you need, you describe the outcome and let Copilot produce a first draft of the automation. You then check it, correct it, and switch it on. It also builds the other pieces — a Table, an Interface, an agent — from the same kind of instruction.
The catch is the obvious one: Copilot builds what you said, not what you meant. It will happily wire up something subtly wrong with total confidence. So the old understanding isn’t obsolete — it’s what lets you look at the draft and spot that the filter is in the wrong place or the date format will break the next step. Describing is faster. Reviewing is still on you.
Canvas: drawing the system before you build it
Canvas is the companion piece, and it works the other way round. It’s a visual space for mapping a workflow or a whole system — boxes and arrows for how information should move — which you can then turn into actual Zaps. Sketch the flow first, agree it’s right, then generate the build from the diagram.
For anything with more than a couple of branches, this is genuinely useful. It forces you to think the process through before committing to it, and it gives you a picture you can show a colleague or a client without making them read a list of steps. Map, agree, build — in that order — and you make your mistakes on a diagram instead of in a live automation.
What this shift really means
Step back and the pattern is clear: the centre of gravity is moving from operating the tool to specifying the outcome. The valuable skill is no longer remembering where a setting lives; it’s being able to describe precisely what you want, and to recognise when what you got back isn’t it.
That’s a comfortable shift for people who work in health communications, because precise specification is already the job. A good brief, a clear set of requirements, an exact description of the output you need — that is the same muscle. The people who get the most from Copilot and Canvas won’t be the most technical. They’ll be the clearest.
Next: 15. Zapier: when the automation makes decisions — agents that set their own steps, and the guardrails that decide whether you can trust them.
Zapier for health communications is a practical series. New post every week.
— Ned