Workflows in OpenClaw

After installing OpenClaw, I was wondering how I would approach AI and Alex Hormozi put it in the right words (verbatim):

Do not see AI agents as roles in companies, but in workflows. What does this employee do? Break it down in workflows and try to automate it.

So, I came up with the idea of a workflows folder in OpenClaw's workspace. It contains a bunch of markdown files which are … workflows. I can tell my AI: "Remi, run workflows/FILING.md" and it executes that workflow. With that I can build, fix, improve and finally release it as a cron job. Memory loss is not a problem. Everything lives in that MD file.

Or more generally speaking, the workflows folder is best understood as a collection of lightweight operational applications for agent-driven work. Each item in it represents a recurring business process that is being turned from an ad hoc human task into something structured, repeatable, and increasingly automatable. These are not just notes or prompts. They are working process definitions: documents and supporting files that describe what a task is, how it should be handled, which tools it can use, what decisions are safe to automate, which exceptions matter, and where human review is still required.

In practice, a workflow usually begins as a supervised helper for a real business task. It might start with rough instructions and only partial reliability, but then it improves through repeated use. Each run reveals edge cases, failure modes, ambiguities, and operational constraints. Those lessons are written back into the workflow until the process becomes more precise, more resilient, and less dependent on constant human steering. Over time, the workflow starts to behave less like a fragile script and more like a small app with defined behavior, guardrails, and expected outputs.

That is why "workflow" is the right word here, but also why "app" is not wrong. These workflows are essentially agentic apps expressed through instructions, rules, memory, tooling, and iteration. They are designed to do real operational work, not just demonstrate an idea. A good workflow captures the business logic of a task, the practical handling rules, and the safety boundaries needed for automation. It becomes a durable unit of capability that can be tested, improved, and eventually trusted.

The long-term goal is not merely to document processes, but to operationalize them. Once a workflow has been exercised enough times and its behavior is well understood, it can often be promoted into a cron-driven background process. At that stage, the workflow has effectively matured from a manually supervised agent helper into a reliable automation that runs with little oversight. In other words, the workflows folder is where recurring business chaos is slowly distilled into dependable agent behavior. It is both a workshop and a deployment pipeline for operational intelligence.

I might be doing something very conventional without knowing it, but it feels so powerful.