Run a small agent fleet from Notion

They used Notion as the control panel for 18 OpenClaw agents, with tasks, logs, alerts and configs all flowing through one workspace.

Done with OpenClawยท Advancedยท Mar 2026

What they did
They built AgentOps, a Node and React server that treated Notion as the only database through the Notion API. Four separate Notion databases handled the agent list, task queue, run history and alerts, while a poller checked Notion every 10 seconds and skipped any paused agents. When a task appeared in Notion, the runtime picked it up and sent it to the right agent; prompts and settings also synced in both directions, and the fleet could be backed up or exported as JSON.
How it went
The setup kept track of 18 agents, 78 recorded runs and more than 128K tokens. The author said moving the system between instances took only minutes. One commenter worried about concurrent writes, and they answered that the jobs were cron-based and executed one at a time.
Tips
This approach fits a single poller handling scheduled jobs, not heavy concurrent writes from many agents. If you sync configs to a workspace, strip out secrets first.

Try it yourself with OpenClaw

Help me set up [number] OpenClaw agents to run as a small team from [Notion or another workspace]. Give each agent a clear role, build a task board, and keep a log of runs, alerts, and current status. Before any agent sends a message, updates records, or makes a change outside the board, stop and show me the exact action plan for approval.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on dev.to โ†—

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.