Hermes Agent just shipped Automation Blueprints — they turn raw cron jobs into clickable, fillable, conversational workflows. A schedule, a GitHub event, or an API call fires an agent, and it delivers wherever you want. I used it to build something live: an AI news digest that researches the web while I sleep and lands in my vault every Monday. Here's the whole thing — the update, the build, and a link to every part.
Before, an automation in Hermes meant writing cron syntax by hand. Now you pick a blueprint, fill in the blanks, and launch — or just tell Hermes what you want in plain English.
That one change is why this matters for everyone, not just developers. Here's the shape of it (full docs here):
Schedule — runs on a cadence (every morning, every Monday). GitHub event — fires when a PR opens or CI fails. API call — any service POSTs to your endpoint and an agent responds. One blueprint, three ways to set it off.
Telegram, Discord, Slack, SMS, email, GitHub comments, or a local file. The work happens in the background and shows up where you'll actually see it.
You tell the agent: "if there's nothing worth reporting, say [SILENT]." On quiet runs it stays quiet. You only get pinged when there's genuinely something to see. That's the difference between an automation you keep and one you mute.
No provider lock-in. Run it on a local model for free, or a frontier model when it matters. Your blueprint doesn't care which.
That's exactly what Blueprints fixed. You don't write cron syntax — you fill in a recipe or talk to Hermes.
"Every Monday at 9, research the biggest AI news and put it in my vault." That sentence IS the blueprint.
Here's the exact Automation Blueprint I built with the update — a weekly AI research digest. Five moving parts, one Monday-morning result. Tap any card to open the real thing.
Before
Every morning started the same way.
Twenty tabs. TechCrunch, arXiv, GitHub, five blogs, Twitter.
An hour gone before I'd written a single video idea.
And half the time I'd miss the one launch that mattered.
Then Hermes shipped Automation Blueprints, and I gave the morning research to an agent.
After
Now it's done before I wake up.
A clean digest is waiting in my vault every Monday — headlines, papers, trending repos.
I read it with my coffee, pull three video ideas, and I'm working by the time most people are still opening tabs.
I set up one blueprint. It's run every week since, for free.
You can have this too. Same Hermes. Same blueprint. This page links every part.
You've seen the digest. Real, written by an agent, while I slept.
The next few minutes show you every part of how the blueprint works.
So here's the deal.
Promise yourself one thing right now — you'll set up ONE Automation Blueprint before you sleep tonight. Just one. A digest, a scout, a monitor. Anything that watches something for you.
Because the moment you make this transition, you stop doing the work a machine should do — forever.
The people sitting still are still opening twenty tabs every morning. The people building blueprints today wake up to the answer already waiting.
Be one of those people.
Commit to the transition. Commit to taking action today. This changes how every morning starts.
Five layers turn an Automation Blueprint from "a cron job" into "research that's already done." This is how I think about every blueprint I build.
Firecrawl reads the web for you — the AI blogs, the news sites — and brings back the real headlines. You stop opening tabs.
arXiv and GitHub get pulled automatically — newest papers, trending repos — through free APIs. You stop checking five sources by hand.
The blueprint writes the digest itself — clean headings, one-line summaries, real links. You stop formatting anything.
The finished digest lands in your Obsidian vault — searchable forever, and your AI can read it back. You stop losing what you found.
The Hermes gateway fires the blueprint every Monday, on its own. You do nothing — it just shows up. You stop remembering.
The opposite — that's the whole point of a blueprint. It's a recipe, not a chatbot. Once it's wired, it runs untouched.
Mine's fired every Monday since I built it. I haven't opened it once.
The blueprint pulls from three sources: Firecrawl for web headlines (one API key), plus arXiv and GitHub which are free, no key. Firecrawl is the one that matters — it scrapes where plain search fails.
A small script calls all three, formats a clean digest, and writes it to your vault. No AI guessing, no flaky tools — it just runs. Mine lives at ~/.hermes/profiles/<profile>/scripts/ai-digest.py — open it here.
One Hermes cron blueprint runs the script every Monday 9am — --no-agent, so it's deterministic and free. The Automation Blueprints docs have a recipe for every trigger: schedule, GitHub event, or webhook.
The digest writes into your Obsidian vault, so it shows up in your Agent OS Memory tab — searchable, and your voice assistant can read it back. Spin up the next blueprint from the Hermes tab.
You don't wire it by hand — that's the whole Blueprints update. You tell Hermes what you want in plain English and it builds the job.
The full setup — the script, the Firecrawl connection, the exact prompts — comes done in the member pack.
If you want this done-for-you — the script, the Firecrawl wiring, the Hermes blueprint setup, plus a panel to launch more blueprints without touching a terminal — it all lives inside the Agent Operating System in the AI Profit Boardroom.
Swap the script's sources and the same blueprint becomes anything you wish watched itself:
Wake up to what every rival shipped overnight.
5 fresh title ideas in your vault every morning.
Only pings you when a keyword actually moves.
New brand mentions + backlinks, gathered daily.
If you do any kind of daily research — yes. Tonight.
It's a one-time setup, then it's free forever. The first Monday it lands in your vault, you'll wonder why you ever did it by hand.
The people who hand the boring, repeating work to agents now — while everyone else still opens twenty tabs — are the ones who'll have hours back every week when this is normal. Every blueprint you build compounds.
Firecrawl + arXiv + GitHub gather the research for you.
The blueprint writes a clean digest, headings and links done.
It lands in your vault — searchable, and your AI can recall it.
Hermes fires it every Monday on its own. Zero effort.
Wake up to the answer already written, for $0.
One blueprint. Set it up once. It works the night shift forever.
If you want your whole stack to work like this — blueprints that watch, research, and report while you sleep — go grab the Agent Operating System inside the AI Profit Boardroom.
It turns Hermes, Claude, and OpenClaw into one system with shared memory and one dashboard you control. Every blueprint you add makes the whole thing more powerful.