A business process automation tool with no graph editor.
Every other BPA tool on page one of Google ships a workflow graph editor as its main user surface. Zapier has the Zap editor. Make has the scenario canvas. Power Automate has the flow designer. UiPath has Studio. Appian, Nintex, Kissflow, Camunda, Bizagi, ProcessMaker all ship a BPMN canvas.
Clone shipped without one, on purpose. The user-visible input surface is a chat window backed by a folder of markdown files at ~/.clone/memory/. No node graph. No drag-and-drop designer. No BPMN surface. Not a simplified one. Not a hidden one.
Every BPA tool category leader is a graph editor first.
Run the search. Open each homepage. The headline screenshot is a workflow canvas. The onboarding flow sends you to that canvas. The marketing pages argue about which canvas is more intuitive, which drag handle is smoother, which branch syntax is less confusing. The canvas is the product.
That shape is correct for a 500-person operations team with a dedicated BPM admin. It is wrong for a 1-to-5 person consulting firm, where nobody wants to become the canvas owner. The canvas sits empty for weeks, then half-wired for months, then forgotten. The work keeps getting done by hand while the canvas license keeps billing.
What Clone ships instead, quoted from its own source.
The Clone marketing site is open source. The hero is not a canvas screenshot. It is a chat log defined as a six-pair array in the component file. Here it is verbatim. If you want to falsify the claim on this page, open src/components/hero.tsxand search for the word "canvas". You will not find one.
anchor fact
The entire marketing demo of Clone, on the homepage above the fold, is a six-pair array of chat messages. No workflow canvas component is imported anywhere in that file.
One card per BPA tool, showing the canvas inside it.
Each of the tools below ships a graph editor as its primary value prop. The card names the canvas by its vendor term. At the bottom, Clone gets one card too, with the claim this page is about.
Zapier
The canvas is the Zap editor. Every automation is a linear chain of typed nodes (Trigger, Action, Filter, Paths, Delay). Branching is another canvas. Each app integration is a modal. No canvas, no Zap.
Make (Integromat)
A 2D scenario canvas with circular modules and connecting lines. You zoom, pan, connect, configure inside each module. The canvas is the product. The UI is the graph.
Power Automate
A vertical flow designer shipped as part of Microsoft 365. Each step is a typed connector action. Branches, switches, loops are canvas elements. Copilot drafts into this canvas, it does not replace it.
n8n
A directed node graph, like a miniature IDE. Each node is a function, a webhook, or a service call. You wire nodes together visually. The primary value prop is the canvas itself.
UiPath Studio
A full desktop IDE for RPA, with activity panels, a flowchart surface, a sequence surface, and a Workflow Designer. Not one canvas, three. Recording adds more.
Appian, Nintex, Kissflow, Pega, Camunda, Bizagi, ProcessMaker
Enterprise BPM, all built on a BPMN canvas. Swim lanes, gateways, events, sub-processes. The canvas is the durable artifact the vendor sells. Delete the diagrams and the product has nothing left.
Clone
No canvas. Not a hidden one. Not a simplified one. The user-visible surface is a chat window and, beneath it, a folder of markdown files at ~/.clone/memory/. You can grep it, diff it in git, and open it in any text editor.
Building one invoicing automation, the two ways.
Same job, same source data (Timely hours), same destination (QuickBooks invoices plus Gmail cover emails). One version is a canvas-building session that typically ends in a failed integration. The other is one typed sentence and a staged batch.
canvas tool
clone
The durable artifact is this file, not a graph.
A Clone automation is a markdown file under ~/.clone/memory/rituals/. You can open it in any text editor, grep for a client name, diff it in git, copy it to another Mac, email it to a colleague. It is the same shape as a README, not a JSON graph. If you uninstall Clone, the file still exists and still describes what you were trying to do.
Four numbers you can verify by opening the product.
The first number is the point. There is no workflow canvas React component in the repository. The second number is the hero demo's full surface area. The third is a typical time from install to first saved ritual. The fourth is the flat Solo price, with no per-connector or per-task tier on top.
Six things the canvas costs a small firm.
None of these are rhetorical. Each one is the kind of cost a BPA buyer only discovers in month two, after the canvas license has already been paid. The shape of the tool predicts the shape of the cost.
A role you do not have
The canvas assumes someone on the team owns it (a BPM admin, a Zap builder, an RPA developer, an automation architect). Small firms do not have that role. The canvas sits empty or half-wired.
A week before the first real output
Wiring a real end-to-end process in a canvas takes days. Multiple trigger-action mappings, field conversions, error paths, test runs. Meanwhile the work the canvas is meant to do still happens manually.
Rewiring every time a tool changes
A client switches from QuickBooks to FreshBooks. In a canvas, that is a new connector, a re-auth, a remap of every field, a regression test of every branch. In a markdown ritual file, it is one edited line.
Apps the canvas cannot reach
Canvases are constrained to whatever has an official connector. QuickBooks Desktop, Filemaker, most law-practice billing tabs, your 2014 client portal have no connector. Clone drives them through the Computer Agent because it reads the screen.
Your voice, discarded
A canvas does not know how you sign emails, when you cc your assistant, or what your do-not-contact list looks like. A markdown ritual file can record those rules in one paragraph. Clone reads the file.
Vendor lock-in by topology
Export a canvas. You get a JSON graph only that vendor can re-import. Export a folder of markdown rituals. You get a folder of markdown rituals. It runs on your Mac whether Clone is installed or not.
Same process, two tool shapes.
Toggle between the canvas-first and the chat-first version of building Monday's retainer invoicing automation. The deltas are structural, not motivational.
building monday invoicing
You open Zapier (or Make, or Power Automate). You click Create Zap. You pick Timely as the trigger app. You OAuth. You pick the trigger event. You add a filter. You add a formatter. You pick QuickBooks Online as the destination. You OAuth. You map six fields. You add a branch for SOW attachments. You add a Gmail action. You template the cover email. You test each path. You realize your real invoicing tool is QuickBooks Desktop and there is no connector. You give up and do invoicing by hand.
- Two to four hours to wire the first Zap
- The canvas is the artifact, not the invoice
- QuickBooks Desktop is out of scope
- Every tool change is a rewire
The entire configuration surface, in six steps.
There is no admin console to learn, no canvas to master, no BPMN vocabulary to absorb. The whole configuration surface of Clone fits on this timeline, and the durable artifacts (markdown ritual files and an action log) are both human-readable.
You type a plain English sentence.
The input surface is a chat window. You describe what you want done in a sentence or two. Clone asks one disambiguating question if needed, not ten.
Clone picks the apps by looking at your screen.
There is no connector picker in the UI. The Planner layer reads which apps you have open on your Mac and decides the sequence of actions. If QuickBooks Desktop is running, Clone uses QuickBooks Desktop.
The Computer Agent drives the apps.
Reads the screen, clicks, types, scrolls. That replaces the canvas's connector catalog. Apps without an API count the same as apps with one.
Drafts appear in chat for review.
The output is not a published workflow. It is the actual invoices, emails, CRM notes. You approve the batch. You ship. That is Day 1 of real output.
The instruction becomes a markdown file.
Say: save that as a ritual, monday 08:00. Clone writes one markdown file at ~/.clone/memory/rituals/<name>.md with a schedule line and the body. Edit it in Vim. Diff it in git. Copy it to another Mac.
Every action is logged and reversible.
The other durable artifact is the action log. Every click, every typed field, every sent email is recorded. Roll back an entire morning of work with one click. This also replaces the canvas's version history.
Six dimensions, six canvases, one chat.
The columns below are the five BPA tools a small firm is most likely to shortlist, plus Clone. The rows are the dimensions that matter once you realize the canvas is itself a cost center.
| Dimension | Zapier | Make | Power Automate | n8n | UiPath | Clone |
|---|---|---|---|---|---|---|
| Primary input surface | Zap editor canvas | 2D scenario canvas | Flow designer canvas | Node graph canvas | Studio with 3 canvases | One chat window |
| Durable automation artifact | Zap JSON in Zapier | Scenario JSON in Make | Flow JSON in M365 | Workflow JSON | Studio project files | Markdown files in ~/.clone/memory/ |
| Apps without an API | Out of scope | Out of scope | Out of scope | Custom code nodes | Recorded selectors, fragile | Computer Agent reads the screen |
| Changing a tool in the stack | New connector, rewire every Zap | New module, rewire every scenario | New connector, rewire every flow | Swap the node, rewire surrounding graph | Re-record selectors | Edit one line in the markdown file |
| Role required to operate it | Zap builder or ops generalist | Ops generalist or dev | Admin or M365 power user | Developer | RPA developer | Operator, no other role |
| Time to first real artifact | Hours per Zap | Hours per scenario | Hours per flow | Hours to days | 1 to 3 weeks | Under 10 minutes |
Seven canvas-detection questions to bring to any BPA demo.
If the answer to most of these is yes, the tool is a graph editor with a runtime attached. That may be fine for a large ops team. For a small firm, each yes is a cost you will pay monthly for as long as you own the license.
the canvas detection checklist
- Does the tool's homepage lead with a screenshot of a workflow canvas?
- Is the first thing you are asked to do after signup to pick a trigger from a dropdown?
- Does each new automation require wiring a new graph, even for near-identical processes?
- Is every supported integration a named connector, with nothing in between?
- When a target app has no connector, is the tool simply out of options?
- Is the automation's durable artifact a JSON graph only that vendor can import?
- Does the tool assume a named role on your team whose job is maintaining the canvas?
The steps the canvas forces you to take.
Each step on this flow exists because the tool is a graph editor. Remove the canvas and most of the steps disappear, because the canvas is what makes them necessary.
- 1
Open the tool
Zapier dashboard vs. Clone chat
- 2
Describe the job
Click Create Zap, pick apps vs. type one sentence
- 3
Configure each step
Per-node modal vs. Clone asks one disambiguating question
- 4
Handle the edge case
Add a branch, test it vs. mention the edge case in the sentence
- 5
First real artifact
Hours to days vs. under ten minutes
- 6
Save the automation
Publish the Zap vs. save the sentence as a markdown ritual
“We spent three weekends wiring Zaps for invoicing. On Clone, one sentence and one markdown file replaced the whole thing. I have not opened a canvas since.”
Solo strategy consultant, 6 active clients
“The moment I realized Clone had no workflow builder was the moment I stopped looking for one. Nothing I wanted to automate actually needed a graph, it needed someone to do the work.”
What you actually buy, if not a canvas.
Four pieces, nothing else. All four are named in Clone's architecture diagram and all four are user-observable on the Mac running the tool. None of them are a workflow builder.
1. A chat window
The input surface. You type sentences. Clone asks one disambiguating question when needed, not ten. The first sentence after install is your first automation.
2. A Planner
Reads the instruction, looks at which apps are on screen, decides the sequence of actions. Replaces the dropdowns of a canvas tool and the OAuth walls of a connector catalog.
3. A Computer Agent
Reads the screen, clicks, types, scrolls. Runs the apps you already use. Replaces the entire connector catalog of every other BPA tool.
4. A memory folder
Markdown files at ~/.clone/memory/. Rituals, clients, voice examples, rate tables. Replaces the vendor database a canvas tool would save your workflow JSON into.
Run one process through the canvas-less shape on a 30 minute call.
Bring one recurring business process. We install Clone on your Mac, you type the instruction in plain English, and by the end of the call one ritual file is written to ~/.clone/memory/ and scheduled. No canvas, no OAuth wall, no connector configuration.
Run one process on a callNo graph editor. No YAML. One English sentence becomes a ritual.
Twenty minutes together. You describe one task in plain English; we let Clone induce the ritual file and run it, no flow-chart required.
Frequently asked questions
Why does this page claim Clone has no workflow graph editor?
Because it does not ship one. Clone's marketing website (cl0ne.ai) has no canvas surface anywhere in its navigation or hero. The hero demo is a six-pair array of chat messages defined in src/components/hero.tsx as const chatLines = [...]. The product itself is a chat window plus a folder of markdown files at ~/.clone/memory/. The architecture diagram in src/components/architecture.tsx names six layers (You, Clone Planner, Clone Computer Agent, Clone Memory, Your Apps, Your Business). None of them are a workflow builder. If you install Clone, the first thing you see is a chat, not a canvas.
Isn't a workflow canvas a useful feature for a business process automation tool?
For large operations teams with a dedicated BPM admin role, yes. The canvas is a shared artifact the team reasons about, audits, and hands off between shifts. For a solo consultant, a 3-person advisory firm, a 5-person bookkeeping practice, or a 2-attorney law office, the canvas is overhead. No one owns it, no one maintains it, it becomes a haunted graveyard of half-wired Zaps. The claim on this page is narrow: for small-firm buyers, the canvas is a cost not a benefit, and a BPA tool without one is faster to deploy and cheaper to change.
If there is no canvas, how do I see what Clone is going to do before it does it?
Two ways. One, Clone stages every batch of actions as drafts in the chat before anything is sent or committed. You see the six invoice drafts, the six cover emails, and you approve the batch with one yes. Two, every recurring automation is a markdown file at ~/.clone/memory/rituals/<name>.md. You can open the file in any text editor and read the instruction in plain English. The review surface is chat plus plaintext, not a graph.
What is inside a Clone ritual file?
A plain English instruction, a schedule line, and optional voice notes or stop conditions. Concretely: the top of the file has a schedule: line (e.g. schedule: mon 08:00 local). Below that is a paragraph describing what to do. Below that, optional sections for voice notes the Planner learned from past emails (open with a personal line, cc assistant above $10k, etc.), tool-binding rules (if QuickBooks Desktop is open, use it; otherwise use QuickBooks Online), and stop conditions (pause and ask if any line item is above $15k). Every line is grep-able.
What happens when a client switches from QuickBooks Online to QuickBooks Desktop?
In a canvas tool, that is a new connector request, a re-auth flow, a remap of every invoice field, and a regression test of every Zap that touches invoicing. In Clone, you open the ritual file and edit one line from 'use quickbooks online web tab' to 'use quickbooks desktop'. Next Monday at 08:00, Clone drives the new tool. The Computer Agent handles the UI difference because it reads the screen instead of calling an API.
How do I verify the claim that Clone has no canvas without installing it?
Open cl0ne.ai and look at the hero, the product screenshots, and the architecture section. You will see chat transcripts, code examples, and a six-layer diagram. No canvas. Also, clone the marketing repo (this very page lives inside it) and grep for 'canvas', 'workflow builder', 'node editor', 'flow designer', 'bpmn'. None of those terms name a user-configurable component. The only place they appear is in comparison text describing what other tools have and Clone does not.
What about ShipStation, HoneyBook, Dubsado, or a generic SaaS with built-in automations?
Those are vertical CRMs or ops suites with a few fixed automations on rails. They do not give you a general BPA tool, they give you their canned workflows in their canvas. Clone is a different shape: an agent that drives whatever tools you already use (including HoneyBook or Dubsado) with no integration work, and stores your recurring instructions as markdown files. It is closer in spirit to a virtual assistant you can program than to a vendor ops platform.
How does pricing compare?
Clone Solo is $49 per month (flat, unlimited rituals). Zapier and Make start near $49 but quickly climb into the hundreds as task volume grows. Power Automate is licensed per user or per flow inside M365. n8n is open source if self-hosted; the cloud tier starts near $20 per user. UiPath seats plus Orchestrator run $1k+ per robot per month. Enterprise BPM (Appian, Pega, Nintex) is license plus implementation partner, typically $50k to $250k in year one. Clone's pricing is flat because there is no per-connector or per-task billing, because there are no connectors or task counts to bill against.
What about AI copilots that generate Zaps or flows for me?
Copilots that draft workflows into an existing canvas are still outputting a graph you have to maintain inside the vendor tool. The graph is still the artifact. When a tool changes, you still rewire. Clone's approach is different: the artifact is not a graph at all, it is a markdown file that describes the work in plain English, and the execution layer is a screen-driving agent that does not depend on connectors. There is no graph to maintain, because there is no graph.
If there is no workflow builder, how do I handle branching logic (if X then Y else Z)?
You put it in the sentence, in plain English. Example ritual body: 'draft the invoice, but pause and ask me if any line item is above $15k, and if the client is flagged on-hold in hubspot, skip them entirely'. Clone parses the instruction and runs the branches at execution time. The Planner layer also asks one disambiguating question if the instruction is ambiguous, rather than silently picking a path. If you prefer, you can add explicit stop-condition lines to the ritual file. It is still plaintext.
Is this really a 'tool', or is it an agent that happens to be sold as a tool?
It is both, and the distinction is the whole point of the page. Most BPA tools are graph editors with an execution runtime attached. Clone is an agent with a chat and a markdown folder attached. The category name 'tool' was invented for the graph-editor shape. Clone fits the 'business process automation tool' search intent (a single product that automates business processes across your stack) while rejecting the graph-editor assumption baked into the category.
Can I try the canvas-less shape on one process in a live call?
Yes. Bring one recurring business process you want automated (Monday invoicing, Friday admin, weekly pipeline update, quarterly closeout). On a 30-minute call we install Clone on your Mac, you type the instruction in plain English, the Computer Agent drives your real apps, and by the end of the call one ritual is saved to ~/.clone/memory/ and scheduled. No canvas, no OAuth wall, no connector catalog, one artifact shipped.
Three Clone guides that frame the same shape from different angles.
Adjacent reading on the same canvas-less architecture
Business Process Automation Solution, Evaluated by the Day 1 Integration Test
The canvas-less shape, viewed through a single buyer-side test: what ships on Day 1?
Business Process Automation Service That Runs the Overnight Shift, and Lets You Roll the Whole Morning Back
The review queue and rollback layer that sits on top of the same canvas-less architecture.
Business Process Automation Examples, Organized by the Calendar They Fire On
23 BPA examples expressed as markdown ritual files on a schedule, no canvas required.
A BPA tool with no canvas, no connector catalog, no BPMN. $49/mo, 21-day trial.
Book the canvas-less demo