AI workflow automation, written in plain language
Most workflow automation tools make you draw the process on a canvas. Zero asks you to describe it, then writes the workflow and the trigger that runs it.
Propose, agree, automate
It starts as a proposal, not a blank page
A recurring job is rarely three steps, and half of it lives in one person's head. Ask Zero to do it once and it writes the whole process back — you argue with a draft, not a blank page.
Every Monday, put the client report together and post it in #clients.
Here is how I would run it — tell me what to change.
- 1.Pull last week's numbers for each active client
- 2.Compare them with the four weeks before
- 3.Write the commentary, and flag anything off-plan
- 4.Publish, and post the link in the client's channel
Happy with it? I will save it as a workflow for the team.
A workflow is that agreement, written down
Saved, it is a reusable skill under your organization. Anyone can run it, and every later fix lands for the whole team.
Every Monday morning, one report per active client.
Steps- 1.Pull last week's numbers from the connected accounts.
- 2.Compare them with the previous four weeks.
- 3.Write the commentary that explains what moved and why.
- 4.Publish, and post the link in the client's Slack channel.
- —One report per client, and a link in their channel.
An automation is that workflow, with a trigger
Bind it to a schedule, an email, a calendar event, or a finished run. One workflow can sit behind several triggers.
Business process automation teams hand over first
Recurring processes that never justified an engineer or a seat of workflow management software, and that business process automation tools are too rigid to take.
The report that is finished before anyone asks for it.
The Monday metrics, the pipeline review, the board update.
A competitor or a market, tracked on a fixed interval into one document.
The week's calendar, threads, and open items in one brief.
Speaks up only when something actually moved.
A dashboard or a query on a schedule, reported only when a number leaves the range.
Watch a mailbox, summarize what matters, draft the reply. Sending stays yours.
The alert arrives with the history and the likely cause, not just a number.
The recurring piece, drafted end to end.
Draft, illustrate, and format the recurring piece. The last edit stays with you.
What was decided goes into the CRM, the tracker, or the sheet — same fields, every time.
The week's work becomes the status doc, the changelog, or the client update.
It runs on the tools the process already lives in
Around 290 connectors, so one workflow reads from one system and writes to another with no integration to build.
Axiom
Ahrefs
Airtable
Gmail
Google Sheets
Notion
DocuSign
LinearAxiomAhrefsAirtableGmailGoogle SheetsNotionDocuSignLinear
Google Calendar
Intercom
Deel
HubSpot
Dropbox
Sentry
Figma
VercelGoogle CalendarIntercomDeelHubSpotDropboxSentryFigmaVercelThe credential never reaches the agent
Connect by OAuth or by a key you paste in. Either way the credential is held outside the environment the agent runs in and attached at the network boundary — the workflow never carries it.
Granted per connector and per permission
Approve the exact scopes a workflow needs, for the people who need them, with an expiry.
Some things need no connector at all
Scraping, search, maps, weather, and market data are built in, no account of your own.
Workflow automation FAQ
What is the difference between a workflow and an automation?
A workflow is the instructions on their own: reusable, shareable, no schedule. An automation is that workflow bound to a trigger and an agent, so it runs on its own.
Do I have to build the workflow myself?
No. Ask Zero to do the job once and correct what it proposes — no canvas, no node editor, no expression language. The version you save is the one you agreed on.
What can trigger an automation?
A schedule, a new message in a connected mailbox, a new calendar event, or another run finishing. You can also start one by hand.
Whose access does an automation use when it runs?
The person who owns it, and only for the permissions they approved on each connector.
What happens when a run fails?
The run stops and keeps its log, so you can see which step broke and what it was working with. Nothing is retried silently.
How is this different from other workflow automation tools?
Most workflow software is a builder: canvas, branches, field mapping. Zero is described rather than built, so it also copes with steps a rigid platform cannot, like reading a thread and judging what matters.
Is this a workflow automation platform or an AI assistant?
Both. An assistant answers when you ask; a workflow automation platform runs the same process on a schedule. Zero saves what the assistant got right and hands it to an AI agent for workflow automation.
Can it handle business process automation, not just simple tasks?
Yes. AI process automation pays off on processes that span systems: one workflow reads several tools, produces the artifact, posts the result. What AI business process automation will not do is replace a system of record.
Do we need engineers to run it?
No. Anyone who can brief a colleague can write a workflow — unlike process automation that ships with an implementation project.
Zero also covers generative services, team collaboration, and Slack. See the built-in web services, the models you can switch between, and pricing.
Turn this week's recurring job into an automation
Describe the work once. Zero writes the workflow, and you decide when it runs.