Hermes Cron Setup for Safe Scheduled AI Workflows

Cron is for time-based work. In Hermes, use it when a private assistant should wake up on a schedule, inspect approved context, prepare a summary or draft, and stop at the right approval gate.

Use Hermes cron for scheduled reminders, owner briefings, follow-up queues, review prompts, and routine checks. Keep jobs narrow, low-noise, and reviewable. A scheduled job should usually read, summarize, draft, and ask. It should not silently send customer messages, delete records, issue refunds, publish content, or change production systems.

Cron is a timer. It is not a manager.

Good Hermes cron jobs

Good scheduled workflows have a fixed time, a clear source, and a reviewable output.

Examples:

• weekday morning owner briefing;
• daily lead follow-up draft queue;
• Friday open-loop review;
• weekly CRM hygiene summary;
• monthly tool access review reminder;
• end-of-day “what needs approval?” digest;
• weekly content planning prompt;
• daily memory cleanup suggestion, not automatic deletion.

Each job should answer one question and stop.

Bad cron jobs

Do not use cron for work that needs live judgment, urgent escalation, or irreversible action.

Avoid scheduled jobs that:

• auto-send customer emails;
• quote prices or promise timelines;
• delete, archive, or overwrite source material;
• issue refunds or billing changes;
• merge code or change production settings;
• post public content;
• create frequent alerts nobody owns;
• run broad research with no clear output.

If a bad run would create confusion before anyone sees it, add approval or redesign the job.

A safe cron pattern

Use this pattern for the first Hermes scheduled workflow.

1. Schedule: when should it run?
2. Purpose: what single outcome should it produce?
3. Sources: what files, tools, calendars, inboxes, or systems may it inspect?
4. Skill or runbook: what procedure should it follow?
5. Output: what should the owner receive?
6. Approval gate: what must not happen automatically?
7. Receipt: where is the run logged?
8. Review: who checks the first five runs?

Example task:

> Every weekday at 8:30am, Hermes prepares a five-bullet owner briefing from today’s calendar, open follow-ups, and approved notes. It may draft suggested replies, but it must ask before sending messages, editing CRM records, or changing calendar events.

That is narrow enough to test.

For owner briefings, consider splitting the job in two. Let an earlier scheduled run do the heavier preparation across notes, inbox, calendar, and open loops, then let the delivery run send a short decision brief later. The owner sees a focused briefing instead of waiting on a long live scan at the moment they need to decide.

Scheduled does not mean unsupervised

A cron job should still follow the same security model as an interactive assistant:

• scoped credentials;
• approved sources;
• narrow tools;
• explicit blocked actions;
• approval before commitments;
• visible receipts;
• easy off switch.

The schedule only changes when Hermes starts. It does not change what Hermes is allowed to do.

Use skills for recurring procedures

If a scheduled job repeats the same procedure, put the procedure in a Hermes skill or runbook instead of rewriting a long prompt in the cron entry.

Example split:

• Cron says: “Run this every Friday at 3pm.”
• Skill says: “How to produce the open-loop review.”
• Runbook says: “Which sources, owners, approvals, and blocked actions apply.”
• Memory stores stable preferences, not this week’s task list.

This makes the job easier to update when the workflow changes.

Cron and memory hygiene

Scheduled jobs should be careful with memory. A daily briefing should not save every temporary fact it sees. A follow-up queue should not preserve sensitive customer details unless there is a durable reason.

Use memory for:

• stable preferences;
• repeated corrections;
• durable business facts;
• source names and formatting preferences.

Keep current state in the source system, a project file, or the run output. Let Hermes reread current sources instead of accumulating stale memory.

Cron vs manual trigger vs heartbeat

Use the simplest trigger that fits the work.

• Manual trigger: best when the owner wants control over when the task starts.
• Cron: best when the time matters and the output is predictable.
• Heartbeat or condition-based checks: better when Hermes should inspect state periodically and decide whether anything deserves attention.

Examples:

• Manual: “Prepare a proposal follow-up for this client.”
• Cron: “Every Friday, summarize open loops.”
• Heartbeat/check: “During business hours, flag only urgent customer escalations.”

Many systems use all three, but the first scheduled workflow should usually be plain cron.

Approval design for cron

Scheduled approval messages should be fast to review.

Include:

• run name and timestamp;
• sources inspected;
• summary of findings;
• proposed action;
• exact draft or change;
• risk level;
• approve/revise/hold options;
• receipt location.

Bad approval:

> Should I handle these leads?

Better approval:

> I found three new qualified leads. I drafted replies for Alex and Priya and held Sam because pricing was unclear. Approve sending these exact two drafts? If approved, I will send them and add CRM notes. I will not quote pricing or change deal stage.

The second message lets the owner decide.

Common mistakes

Mistake 1: scheduling vague work

“Check everything important every morning” creates noise. “Prepare five bullets from calendar, follow-ups, and open invoices” is reviewable.

Mistake 2: making cron too frequent

More runs do not mean more value. For owner workflows, a daily or weekly batch is often better than constant interruption.

Mistake 3: letting scheduled jobs execute externally

A scheduled draft is useful. A scheduled unsupervised customer email is risky. Keep external actions behind approval unless the task is low-risk and proven.

Mistake 4: never reviewing failures

A cron job nobody reviews becomes background clutter. If a job is useless for two weeks, fix it or delete it.

First Hermes cron plan

1. Choose one low-risk scheduled output.
2. Write the source list and output format.
3. Decide whether a skill should define the procedure.
4. Keep all external actions behind approval.
5. Log the result where the owner already looks.
6. Review the first five runs.
7. Remove noise before adding more jobs.

A good scheduled assistant should feel boring: useful when it appears, quiet when it has nothing to say, and clear about what needs approval.

Recap

Hermes cron is best for scheduled summaries, reminders, follow-up queues, and routine checks. Keep jobs narrow, use skills or runbooks for repeated procedure, keep memory clean, require approval for external actions, and review early runs before expanding.

Next step

For overall runtime setup, read Hermes Agent Runtime for Business Workflows. For skills used by scheduled jobs, read How to Use Hermes Skills for Repeatable Business Workflows.