AI workflow automation, written in plain language
Most workflow automation tools make you draw the process on a canvas first. Zero asks you to describe it, then writes both the workflow and the trigger that runs it.
Propose, agree, automate
It starts as a proposal, not a blank page
You never write it yourself. Ask Zero to do the job once and it proposes the steps, the tools, and the result. You correct it, and that agreed version becomes the workflow.
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 from the connected accounts
- 2.Write the commentary that explains what moved
- 3.Publish the report and post the link in #clients
A workflow is that agreement, written down
Saved, it becomes a reusable skill under your organization — anyone can run it, and every later fix lands for the whole team at once.
Run every Monday morning and produce one report per active client.
Steps- 1.Pull last week's numbers for the client from the connected accounts.
- 2.Write the commentary that explains what moved and why.
- 3.Publish the report and post the link in the client's Slack channel.
An automation is that workflow, with a trigger
Bind it to a schedule, a new email, a calendar event, or a finished run and it starts itself. One workflow can sit behind several triggers.
How AI workflow automation works here
No canvas, no node graph, no expression language. You describe the process, review what Zero wrote, and decide when it runs.
- 01
Ask Zero to do it once
Say what needs to happen and let it propose the approach. You correct what it got wrong before anything is saved.
- 02
Save it as a workflow
It becomes a reusable skill in your organization. Anyone can run it, and every fix lands for the whole team.
- 03
Give it a trigger
Attach a schedule, a new email, a calendar event, or a finished run. It starts itself and reports back.
- 04
Watch it and correct it
Every run leaves a log of what it read and did. When the output drifts, you edit the workflow in language, not configuration.
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 weekly pipeline review, the monthly board update — delivered before anyone asks.
Track competitors or a market on a fixed interval and keep one running document, not a new tab every morning.
The week's calendar, threads, and open items in one brief, so Monday starts with a page instead of a search.
Speaks up only when something actually moved.
Check a dashboard or a query on a schedule and speak up only when a number leaves the range you set.
Watch a mailbox, summarize what matters, and prepare the reply as a draft. Sending stays your decision.
When something does cross the line, the alert arrives with the history and the likely cause, not just the number.
The recurring piece, drafted end to end.
Draft, illustrate, and format the recurring piece, then hand the last edit to whoever owns the voice.
Move what was decided into the CRM, the tracker, or the spreadsheet — same fields, same way, every time.
Turn the week's work into the status doc, the changelog, or the client update, written from what happened.
It runs on the tools the process already lives in
Around 290 connectors, so one workflow can read from one system and write to another without anyone building an integration.
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
Slack, Gmail, Notion, GitHub, HubSpot, Salesforce, Stripe and the rest — some connect by approving OAuth, others with a key you paste in. Either way it is held outside the environment the agent runs in and attached at the network boundary, so 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. Read stays separate from write.
Some things need no connector at all
Scraping, search, maps, weather, and market data are built in and called without an 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 without anyone opening a chat.
Do I have to write the workflow myself?
No. Ask Zero to do the job once, let it propose how, and correct what it got wrong. The version you save is the one you agreed on.
Do I have to build a flowchart?
No. Describe the job in a sentence and Zero writes the workflow. There is no canvas, no node editor, and no expression language.
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. It reaches a connected service only where that person granted access, and only for the permissions they approved.
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: lay the process on a canvas, wire the branches, map every field. 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 on a trigger.
Can it handle business process automation, not just simple tasks?
Yes. AI process automation pays off on processes that span systems: one workflow reads from several tools, produces the artifact, and 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 — the difference between this and 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.