One source of truth for the ClawBot worker, the 20-bot fleet, the 16 n8n cron callers, the 5 Airtable bases and the F0→F5 path from a single VPS to a resilient AWS stack. Navigate by topic — every page links back here.
Each section is a self-contained page with diagrams, tables and source references.
5-layer view: sources → ClawBot worker core → surfaces. Parallel systems (ClawBot vs Operational Tasks) and shared infra primitives.
02 · Current Flow16 n8n cron workflows, HubSpot lists + Airtable views, ClawBot FastAPI on a single VPS, queue write to task_queue_sales.
03 · TargetECS Fargate workers, RDS Postgres, EventBridge schedules, Secrets Manager, observability. No more SPOF VPS.
04 · IntegrationsAirtable SSOT, HubSpot CRM, Gmail/WhatsApp, n8n cron, QuickBooks, Make.com, Slack. Auth model + data direction per integration.
05 · LifecycleQUES00095 walkthrough: trigger → enrich → generate → queue → human approval → send. Status fields, robin_tasks, audit trail.
06 · RisksVPS SPOF, 99 duplicates, status SSOT desync, guardrail gaps, secret sprawl. Severity, blast radius, mitigation.
07 · RoadmapFrom hotfix (F0) to fully cloud-native (F5). Owner, dependencies, exit criteria for each phase.
08 · OperationsHealth Sentinel, 20-bot fleet directory, owners, runbooks, on-call rotation, escalation paths.
ClawBot generates outbound work from cron schedules. Operational Tasks captures human work from event triggers. Both write to the same Airtable queue and both are reviewed by Robin.
16 n8n workflows call POST /pipeline/list or /pipeline/orders on the FastAPI worker. Source: HubSpot lists or Airtable views. Output: drafted messages written to task_queue_sales for human approval.
Inbound emails, form submissions, Slack signals route to Robin/R3, who creates tasks in robin_tasks. Status tracked separately from ClawBot but reviewed through the same approval UI.
The Workflows & Automations SSOT table (tbl38RfIpWTRJKyiQ) in base appUDQ65M1lSnSM5p defines all 16 playbooks, their schedules, owners, enabled status and bot bindings. If a workflow isn’t there, it doesn’t exist.