Skip to content

Client Blog Workflow

What Openclaw Is

Openclaw is a self-hosted AI agent gateway running on Unraid at tower.local:18789 (Tailscale: https://tower.tail4e22b.ts.net). It orchestrates AI agents that can read, write, and publish content autonomously.

Project location: ~/projects/b-labs/openclaw-agents/ Doppler config: dev-os project, dev_openclaw_unraid config

Target Workflow: Client Blog Automation

The end-state workflow (to build):

Boxi CRM triggers Openclaw agent
    │
    ├── Agent receives: client slug, target keyword, publish date
    │
    ├── Agent calls mos-seo-content → generates MDX blog post
    │
    ├── Agent reviews + refines content (brand voice, internal links)
    │
    ├── Agent calls GitHub API → commits MDX to client repo
    │         └── Vercel auto-deploys (~60 seconds)
    │
    └── Agent calls Postiz API → schedules 3 social posts
              ├── Publish day
              ├── Day 3
              └── Day 7

This is the Level 4 fully automated pipeline — one Boxi CRM workflow trigger, zero manual steps.

Why This Matters

Pattern confirmed by external practitioners in 2026: “Astro/Next.js + AI agent controller = fully automated content operations”
Agencies using this pattern manage 40+ client sites at scale with a single operator
Not yet standard in the market — building it is a genuine differentiator

Integration Points (to build)

Integration	What it does	Status
Boxi CRM → Openclaw trigger	Sends client slug + keyword + publishAt to agent	Not built
Openclaw → mos-seo-content	Agent calls Marketing OS content command	Not built
Openclaw → GitHub API	Agent commits MDX to client repo	Not built
Openclaw → Postiz API	Agent schedules social distribution	Not built

Current Openclaw Capabilities

Document current capabilities here as they are built. This page is the living spec for the client blog automation workflow.

Blog Automation — pipeline levels and API patterns
Tech Stack Standards — client site infrastructure