Back to workflows
One-Bot workflow

Operations status report

A dated status report that shows successful checks, missed runs, failures, and requested next actions.

Designed for: People responsible for recurring automated work, websites, or internal systems

Full workflow and setup details
Before you begin

Gather the information the Bot needs

  • Approved system and schedule list
  • Read-only status sources
  • Escalation rules and report audience
Operating guide

Know when to run it and who leads

Lead Bot
Ops
Typical first run
15–30 minutes for a first manual run
When to run it
On the reporting schedule you choose, after manual testing

Use this workflow when you need a dated status report that shows successful checks, missed runs, failures, and requested next actions.

Access for the first run
  • The approved inputs listed on this page
  • Only the files, sources, and services required for this run
  • No sending, publishing, spending, or live-system changes without approval
Run the first version one step at a time

Give one Bot the complete job

Use one Bot for the first run. Add a specialist only when the job becomes complicated enough to need a separate role, different access, or independent review.

1

Ops

Check the approved signals and schedules, organize problems by urgency, and write the update for the intended reader

Produces: A clear status report with successful checks, failures, and actions that need approval
Use the approved inputs I provide. Check the approved signals and schedules, organize problems by urgency, and write the update for the intended reader. Return this result: A clear status report with successful checks, failures, and actions that need approval. Ask me about missing information before you continue.

Overall request

Check the approved system list and prepare today's status report. Show successful checks, missed runs, failures, and the exact action that needs approval.

Use this as the complete first-run request.

Decisions for a person

  • Approve repairs and configuration changes
  • Approve external notifications
  • Choose the schedule after manual tests
First test

Try the workflow with low-risk material

Check two harmless read-only status sources and confirm that the Bots make no changes.

Check the result

Check the result against your original material. You make the decisions listed below. Check two harmless read-only status sources and confirm that the Bots make no changes.

If the workflow stalls

If the result is incomplete, mark the missing information and ask the same Bot to correct it. Add another Bot only when a genuinely separate role or independent check would help.

Set it up in Hermes Desktop

Begin with one Bot and one manual run

  1. Open the linked starter page, download its .tar.gz profile, and import it from the Profiles screen in Hermes Desktop.
  2. Review the profile’s SOUL.md, Bot Passport, and requested access.
  3. Run the complete request in that Bot’s chat with low-risk material and review the result.
  4. Add a schedule, outside connection, or optional specialist only after the manual version works.
Read the official Bot Mode guide