Five fixed public sources
Do not begin with your primary inbox, payment account, or confidential material.
AI AUTOMATION · FROM ONE SUCCESS TO A STABLE RUN
Want AI to run automatically? Start with one repeated task you can inspect and recover.
Automation is not handing one sentence to an agent and walking away. A useful workflow defines its trigger, sources, output, approval points, and where to resume after failure.
See what you should get first
SEE THE FINISH LINE FIRST
Test with one daily result whose quality you can judge
A change brief with original links
Mark each item as new, duplicate, conflicting, or still unknown.
Before send, publish, pay, or delete
Return a proposal for review instead of changing external state.
NOT MAGIC · A PATH YOU CAN INSPECT
A stable workflow makes these six states visible
If one step is unclear, pause there instead of hiding the problem under more generations.
- 1
Trigger
Schedule, new file, or manual start
- 2
Read
Only the material needed
- 3
Decide
Separate rules from AI judgment
- 4
Return
File, list, or reviewable draft
- 5
Approve
Humans decide consequential actions
- 6
Recover
Record failure and resume safely
WHAT A GOOD FRIEND WOULD FLAG EARLY
Think through these three failures before turning it on
Too much access
Reading a page does not justify access to every signed-in page. Drafting email does not justify sending it.
Looks done, actually stuck
Network, sign-in, page changes, and quotas interrupt runs. Without state, logs, and alerts, you only know that nothing happened.
Automating the wrong routine
Complete the same task manually or semi-automatically three times, then keep the stable parts. Do not force a constantly changing judgment into a fixed flow.
START HERE TODAY
Choose the entry point by task—not by maximum power
SIMPLE SCHEDULE OR TRANSFER
Your current AI + a fixed source list
Prefer rules, templates, and schedules already in your tools. You may not need an agent.
- BRING
- Five public sources, one fixed output format, and three manual runs
- DONE MEANS
- Three runs return a change brief with original links
- STOP WHEN
- If the brief keeps changing after three runs, the task is not stable enough to automate
READ, THEN DECIDE
Aye · browser task agent with visible steps
Use a workflow tool with run history, approval, and failure alerts. Start read-only.
- BRING
- Mac or Windows, low-sensitivity public pages, and supervision of the first run
- DONE MEANS
- The plan, current step, returned result, and approval point stay visible
- STOP WHEN
- Do not expand access when sensitive accounts or unclear data paths are involved
OPERATE REAL PAGES OR SYSTEMS
Heym · open-source workflows with human approval
Begin with a test account and no-write environment. Expand only after checking access, targets, and recovery.
- BRING
- Local deployment, test accounts, permission design, logs, and recovery
- DONE MEANS
- Failures are visible and reruns do not duplicate sends or real-data changes
- STOP WHEN
- Do not connect production accounts without a test environment, backup, and approval gate
WHY WE FRAMED IT THIS WAY
Inspect the public primary material before investing.
These maker pages show how automation is being productized. BitShovel does not claim that these flows have run safely in real accounts.
ONE-TAP FEEDBACK
Do you know what to do next now?
One tap. No writing required.