Skip to content
agentusehub

Manage 18 agents from a Notion workspace

Notion used as the control plane for a fleet of 18 OpenClaw agents.

Time saved
Not reported
Setup time
Not reported
Running cost
Not reported
Cost range
Not reported

Use case overview

Notion used as the control plane for a fleet of 18 OpenClaw agents.

Reported experience

  1. What they did

    The author built AgentOps, a Node/React server that uses Notion as its only database through the Notion API (MCP). Four Notion databases hold the agent registry, task queue, run log and alerts. A runtime polls Notion every 10 seconds and skips paused agents. Tasks created in Notion get dispatched. Prompts and configs sync both ways, and the fleet can be backed up or exported as JSON.

  2. How it went

    It tracked 18 agents, 78 logged runs and over 128K tokens. The author says migrating between instances takes minutes. A commenter raised concurrency concerns, and the author replied that the workloads are cron-based and run one at a time.

  3. Worth knowing

    Designed as a single poller over cron-style jobs, so concurrent writes from many agents were not tested. Secrets are redacted before configs sync to Notion.

Example prompts

Try with OpenClaw
Help me set up a small team of [number] agents, each with a clear job such as [job 1, job 2, job 3], and track their tasks and status in [Notion or another workspace]. Create a task board where I can assign work and see results from each agent. Before any agent sends messages or changes things outside the board, pause and show me what it plans to do.
Manage 18 agents from a Notion workspace | AgentUseHub