Examples of business process automation, paired with the one approval line that ships each one.
Every SERP result for this keyword shows an autopilot. Trigger fires, branch evaluates, action dispatches, done. Nobody names who pulled the trigger. Clone is structurally the other thing: every example pauses on a named phrase before it ships.
Seven consulting automations, shown as a draft, a pause, a phrase, and a receipt. No auto-sends, no vendor builder, no branch surgery. The approval beat is the point.
Every SERP result frames the example as an autopilot.
Run the query. Open the top ten articles. Activepieces, Moxo, Flowforma, Jotform, Akveo, Blue Prism, Rebbix, Innovadel. Count how many name the human keystroke inside each example. The answer is zero. The example is always a pipeline of autonomous verbs, never a draft followed by a phrase.
For a Fortune 500 shared-services team, the autopilot framing is correct. The workflow has been repeated ten thousand times; drift is what's rare. For a solo consultant with seven clients and a mailbox that's also their support queue, the autopilot framing is where the money leaks. The send that went out on the wrong template, to the wrong address, with last quarter's rate, is the kind of mistake that a pause catches and an autopilot does not.
The anchor fact lives inside how-it-works.tsx.
The Clone marketing site's own src/components/how-it-works.tsx has a verbatim transcript for step 2. Four kickoff emails drafted, then this block:
“Clone drafts four kickoff emails. Then: "You: Send them all. Clone: Sent."”
src/components/how-it-works.tsx, lines 25-37
That two-beat is the whole product. Every example below is an extension of it. The draft is whatever artifact the app produces. The approval line is the string you type. The receipt is the evidence the app emits after the send. Clone does not replace the apps; it orchestrates drafts inside them and waits on one sentence.
Seven examples. Seven draft beats. Seven approval lines.
Each card below lists the moment that kicks the ritual off, the plain-English instruction, what Clone drafts autonomously, the reviewable artifact that sits in an app you can open directly, the sentence you type to ship, and the receipt Clone logs after the send.
Example 01
Draft this week's invoices for every active engagement.
Monday 08:00Clone drafts, autonomously
Pulls billable hours from Timely, opens QuickBooks or the matching billing app per client, fills 6 to 8 invoice drafts, posts the batch link in chat.
Reviewable artifact
A list of 6-8 invoice-draft URLs in chat. Each row: client name, hours, amount, draft link.
Human approval line (the string you type)
You: "Send them all."
Receipt after send
QuickBooks marks each draft as sent; Gmail logs 6-8 outbound emails to the client addresses the draft was composed against.
Example 02
Write the Friday status email for every active deal.
Friday 16:00Clone drafts, autonomously
Reads the deal's HubSpot notes, the week's Loom transcripts, and the shared Drive folder; drafts one status email per active engagement into Gmail drafts.
Reviewable artifact
5 Gmail drafts in your Friday folder, each addressed to the real client contact, each quoting a specific thing said on that week's call.
Human approval line (the string you type)
You: "Send 1, 2, 4. Hold 3 and 5."
Receipt after send
Three sent; two stay as drafts with a note in the chat timeline: 'held for tomorrow per your reply'.
Example 03
Draft the kickoff email whenever a new SOW is countersigned.
After PandaDoc SOW signatureClone drafts, autonomously
Watches PandaDoc for a signed status, clones the Drive template folder, composes the kickoff email with the six credential asks, queues a Calendly invite.
Reviewable artifact
One Gmail draft, one Drive folder link, one unsent Calendly invite. A summary card in chat names the client and the 6 asks.
Human approval line (the string you type)
You: "Fire kickoff."
Receipt after send
Kickoff email sent, Calendly invite dispatched, Drive folder shared with the client. The chat log shows the exact minute the three artifacts left.
Example 04
Write follow-ups that open with the prospect's own pain quote.
After a discovery call endsClone drafts, autonomously
Reads the Zoom transcript, extracts the verbatim pain sentence, drafts a follow-up email that leads with that sentence, attaches the one-pager from Drive.
Reviewable artifact
A Gmail draft showing the lifted quote in the first sentence, followed by two sentences of response and a calendar link. Source line number from the transcript is cited in chat.
Human approval line (the string you type)
You: "Send it."
Receipt after send
Email sent within 60 minutes of the call ending; HubSpot deal row is appended with a note linking to the transcript line that became the opener.
Example 05
When a client writes 'approved', fire the next milestone invoice.
On milestone sign-off replyClone drafts, autonomously
Watches the Gmail thread for the approval verb, opens the right billing app for that client, drafts the next-phase invoice, updates the SOW tracker row in Airtable.
Reviewable artifact
One invoice draft, one Airtable row diff (status 'M2' -> 'M3'), one staged 'phase three kickoff' note.
Human approval line (the string you type)
You: "Invoice them, open phase three."
Receipt after send
Invoice dispatched, phase-three kickoff email sent, tracker row committed. Chat log shows all three as separate ticked lines.
Example 06
Draft the escalation flow for any invoice unpaid 30+ days.
An invoice crosses Net+30Clone drafts, autonomously
Scans QuickBooks AR daily, detects the Net+30 threshold, drafts a phone-call script, a firm email, and a HubSpot note. Nothing auto-sends; everything queues.
Reviewable artifact
Two drafts (phone script and email) plus a HubSpot deal note, grouped in chat under the client name and the number of days late.
Human approval line (the string you type)
You: "Send the email, skip the call for today."
Receipt after send
Email goes out; phone script and HubSpot note persist for the next day. The 45-day cron picks up whichever is still unpaid.
Example 07
Assemble the closeout bundle at the end of every engagement.
Engagement closingClone drafts, autonomously
Compiles every deliverable into a final Drive folder, drafts the final invoice in the client's current billing app, drafts the closeout email, a testimonial request, and a Calendly wrap-call invite.
Reviewable artifact
Four drafts and one finished Drive folder. Chat shows the five items side by side with a single review link.
Human approval line (the string you type)
You: "Ship all four, save the folder link."
Receipt after send
Four artifacts leave on the same minute; the Drive folder link is pinned in the deal row so renewal conversations start with the full record.
The approval beat traced across every actor.
Monday 08:00 becomes 08:04:12, and the only human message in the whole run is the approval sentence.
monday invoicing, draft queue to approval to send
The draft queue is the choke point. Every example routes through it.
Inputs on the left, four approval verbs on the right. The queue never auto-ships. Every send is one of the four right-side verbs, typed in plain English.
Drafts in. Approval out. One sentence per batch.
The autopilot shape vs. the draft-then-approve shape.
Toggle between the two worlds. Same Monday, same 8 invoices, different default.
Monday 08:00, 8 invoices out the door
8 invoices auto-sent at 08:00:03. No human read. If the Timely hours were stale, the wrong amount went to the client. Clean-up requires a refund-and-revise email, a HubSpot note, and an apology thread.
- Zero human eyes between draft and send
- Bad sends land in client inbox before you wake up
- Clean-up is 4x the time a pause would have cost
- No 'held' state; partial approval not possible
SERP autopilot examples vs. Clone draft-then-approve examples
Six axes where the two example shapes diverge.
| Feature | SERP autopilot | Clone |
|---|---|---|
| Example framing | A fully automated pipeline with no human step | A drafted artifact, plus a named keystroke that ships it |
| Who pulls the trigger | Nobody, the workflow fires itself | You do, after reading what was drafted |
| What the reader sees | Arrows: trigger -> branch -> action -> send | Arrows: trigger -> branch -> draft -> pause on 'you:' line -> send |
| Risk of a bad send | Real — the send is unobserved by default | Gated — nothing ships without the review-and-approve line |
| Audit trail for a specific send | Log line recording the auto-send | Chat transcript showing the draft, the approval line, and the send, in order |
| Where you edit an example | Vendor builder UI with triggers and branches | Plain English in chat, backed by a markdown ritual file |
The approval beat in the actual chat timeline.
A real Monday, transcribed. Read the bold line: it is a full sentence, not a click. Five minutes after the ritual fired, seven invoices were out and one was held.
Five properties of the approval beat that the SERP never names.
The whole point of examples-of-business-process-automation lists is to show what gets done. The point of this page is to show where you, the operator, remain in the loop without blocking throughput.
The approval line is a string, not a button.
You type it in chat. 'Send them all.' or 'Ship 1 and 3.' Clone parses the numbers. There is no checkbox UI to miscount.
Every draft sits in one named place.
Gmail drafts, QuickBooks drafts, Calendly unsent invites. You can open the app directly and audit without Clone running.
Held drafts carry forward.
If you ship 3 of 5, the other 2 stay as drafts with a chat note. Tomorrow's run sees them and asks if they still apply.
Receipts land in the chat timeline.
Every send gets a ticked line in the same chat where the draft was posted. No second tool, no second log.
Partial approval is the default shape.
The system expects you to ship some and hold some. That is why every example is a batch, not a single fire.
How to build one of these examples on your own stack this week.
Six steps, one per day if you want. By Friday the first ritual runs itself on Monday and waits for your sentence.
Name one recurring moment.
Monday invoicing. Friday status. Post-call follow-up. Pick one that you already do by hand every week.
Type the plain-English instruction into Clone.
'Draft this week's invoices for every active engagement.' Clone saves it as a ritual the first time it runs.
Watch what Clone drafts the first time.
Do not ship. Read every draft. Delete the ones that are wrong. Tell Clone why so the rule moves into memory.
Decide your approval phrase.
'Send them all.' 'Ship it.' Whatever you would type naturally. Clone learns to expect it at the end of that ritual.
Set the schedule line.
One line in the markdown ritual file: schedule: monday 08:00. Save. The next run fires on its own.
Audit the chat timeline weekly.
Look for the ratio of shipped vs. held. If you held 0 of 8 for three runs in a row, relax the approval pause to 'ship after 10 minutes unless I hold'.
Where the drafts actually land.
None of these are API integrations. Clone's Computer Agent reads and drives the screens you already open. That is why the draft lives in the real app's drafts folder, not in a Clone-hosted staging area.
Gmail
Drafts folder is the review queue for every outbound
QuickBooks
Invoice drafts land here, the approval line ships them
FreshBooks
Per-client billing fallback, same draft-then-ship shape
Calendly
Invites are queued unsent until the approval phrase
HubSpot
Deal rows updated only after the send line fires
Airtable
Tracker diffs staged, committed on approval
Google Drive
Folders staged, shared with the client on approval
PandaDoc
Signature event is the trigger, not the send
Timely
Billable hours feed the draft, never commit to send
Zoom
Transcripts feed the follow-up draft, never the send
Notion
Retros drafted, not posted until you say so
Slack
Batch notifications sit as drafts pending approval
“The thing I did not expect was how useful the 'held' state is. Monday I ship six, hold two. By Tuesday the two become one, and by Wednesday the last one is either shipped or killed. I never had that expressed anywhere in Zapier.”
Bring one recurring moment. Walk out with its approval line.
Pick any recurring moment in your consulting calendar, Monday invoicing, Friday status, post-call follow-up. On a 30-minute call we write the ritual live, set the schedule, and decide the sentence you will type to ship each batch. Clone drafts the first real artifacts on your Mac before the call ends.
Book a 30-minute callEvery example pauses on one key. We show the pause points live.
Twenty minutes together. We run an example ritual and stop at each human-approval gate, so you see exactly where the yes-or-no key is needed.
Frequently asked questions
What does 'the one-key human approval' mean exactly?
It is the plain-English phrase you type in the Clone chat to ship what was drafted. 'Send them all.' 'Ship it.' 'Invoice them, open phase three.' Clone parses the sentence, picks which drafts to fire, and dispatches them. If you never type the approval phrase, nothing ships. The phrase is stored in the ritual's approval_examples list so Clone learns your vocabulary.
Why do SERP articles skip the approval step?
Because the autopilot framing sells better. A diagram of 'trigger fires, email auto-sends, record auto-updates' reads faster than 'trigger fires, draft drafts, human reads, human approves, then send'. The autopilot version also maps onto Zapier's and Make's builder UI, which is what most BPA content is written to sell. Clone's shape does not have a builder UI, so it reads differently: the human is part of the example, not missing from it.
Where does the draft actually live while it waits for approval?
In the real target app. Gmail drafts land in the Gmail Drafts folder. QuickBooks invoice drafts land in the QuickBooks invoice-draft queue. Calendly invites sit as 'unsent' meeting proposals. Clone does not build its own draft database. If you close Clone entirely, the drafts are still there and you can ship them manually. That is also why the 'receipt' is always something the app produced, not a Clone log.
Is this slower than a Zapier autopilot?
Per send, yes, by seconds to minutes (you have to read the draft). Per week, usually faster, because autopilot sends that went wrong are more expensive to clean up than autopilot sends that never happened. Every example in this page includes a 'held' state that a Zapier autopilot cannot express without building a whole second workflow.
What happens if I miss the approval window?
Nothing ships. The draft stays in the real app's drafts folder. The next scheduled run of the same ritual sees the previous draft and asks 'ship yesterday's Monday batch or replace it with this week's?' This is the main reason a missed day does not compound: the state lives in the app, not in Clone.
Can I approve in bulk, example by example, or partially?
All three. 'Ship it' approves the whole batch. 'Send 1 and 2, hold the others' approves two and holds the rest. 'Send 1, edit 2 to replace Q3 with Q2, ship' approves one, edits one in place, and ships both. Clone parses whatever sentence you type; there is no fixed bulk/single UI.
How do I see what was shipped vs. what was held?
The chat timeline. Every send shows as a ticked line with the timestamp and the target. Every hold shows as an info line with a 'draft persists' marker. If you scroll back two weeks, the Monday 08:00 entries read like a ledger: 7 of 8 shipped Monday, 8 of 8 shipped Tuesday, 5 of 8 shipped, 3 held Monday. No extra dashboard.
Does this work with a virtual assistant on my team?
Yes. Route the approval line through your VA. Clone posts the 8 drafts, the VA reviews and types the approval sentence on your behalf. The ritual is unchanged; only the identity that ships the batch changes. Every entry in the chat log records who approved, so the audit trail is intact.
Which file on the Clone source proves the draft-then-approve pattern?
src/components/how-it-works.tsx in the website repo. Step 2 shows four drafted kickoff emails followed by the literal line 'You: Send them all.' and then 'Clone: Sent.' This is the two-beat pattern the whole product is built around, and every example on this page extends it.
How is this different from the other Clone guides on BPA examples?
The page 'business-process-automation-examples' organizes 23 examples by the calendar they fire on. The page 'example-of-business-process-automation' shows five examples as three artifacts each (instruction, file, screen). This page takes seven examples and shows the approval beat inside each one: the draft, the pause, the phrase, and the receipt.
7 BPA examples, each paused on one approval line. $49/mo, 21-day trial.
Book a call