openclaw-automation-architecture
SKILL.md
OpenClaw Automation Architecture
Overview
Design automations around OpenClaw's native primitives first. Reach for external workflow tools only when the job truly depends on third-party app glue, webhooks, or auth patterns that OpenClaw cannot cover cleanly.
Read references/decision-matrix.md when choosing the execution plane. Read references/patterns.md when the user needs a ready-made workflow pattern.
Core Doctrine
- Prefer OpenClaw-native building blocks before Zapier, Make, or n8n.
- Prefer small reliable systems over giant brittle flows.
- Separate trigger, execution, state, delivery, and recovery.
- Pick the cheapest primitive that can do the job well.
- Do not ask the user to choose among primitives unless the trade-off materially affects behavior, cost, or reliability.
Quick Selection
Use this order: