Social media agency — client-approval flow
Draft, route for client sign-off, then publish scheduled posts.
This is an illustrative scenario, not a real customer. The numbers and narrative below are a worked example of how this process would run on G8 — accurate to the product, but not a measured case study.
00 / Before and after
Before — manual
Drafts live in a spreadsheet. A coordinator pastes each one into a DM for the client, chases the approval, then logs in to publish manually. Sign-offs get lost in chat, and the wrong draft occasionally goes out.
After — on G8
The flow assembles the day's queued drafts, posts a single approval summary to the client channel, and waits. Nothing publishes until someone approves it — and every decision is recorded against the run.
01 / The G8 lifecycle, applied
From description to running flow
- 01 / Blueprint
Describe the publishing process
The coordinator writes the process in plain language: collect queued drafts, send a daily approval summary, pause for client sign-off, then publish the approved set. G8 compiles it into a Blueprint with steps and risk levels.
- 02 / Contract
Bound what the agent may do
The Automation Contract allows posting summaries and publishing approved drafts, blocks editing or deleting existing posts, and marks publishing as approval-required so it can never fire unattended.
- 03 / Simulate
Dry-run with no side effects
A simulation walks every step and shows the exact approval message and the posts that would publish — without sending or posting anything. The team reviews the preview before going live.
- 04 / Run
Execute on schedule, pause on risk
Live, the schedule trigger fires each morning. The run sends the summary, then pauses at the approval gate. On approval it resumes and publishes; on rejection it stops cleanly.
- 05 / Monitor
Watch and trace
Monitor shows run volume, success rate, and which runs are waiting on a human. Each publish is traceable to the approver and the step that produced it.
02 / Connectors and approvals
Connectors used
- TelegramPost the daily approval summary to the client channel.
- HTTPPublish approved drafts to the scheduling platform's API.
- EmailSend a digest of what published once the run completes.
Approvals and blocks
- Publishing is approval-required — the run pauses until a human approves the set.
- Editing or deleting existing posts is blocked outright by the contract.
03 / The illustrative outcome
Illustrative: every post that goes out has a recorded human sign-off, and the coordinator stops re-keying drafts by hand.
Model your own process.
Describe it, contract it, simulate it, and watch it run — with humans on the risk.
Start a flow