Customer Activity on Autopilot

/loop 30m Start the "Customer Activity on Autopilot" loop.

Inspired by Fixture (https://fixture.app).

Goal: activity graph is current, next actions are queued or executed, and open commitments have owners with full audit trail
Max iterations: 20
Between iterations run: Report unsynced activity sources, accounts with stale activity, open next actions without owners, and pending CRM sync backlog
Exit when: activity graph covers all connected sources, every open commitment has a tracked task or explicit escalation, and high-impact CRM changes are approved or queued

## Before you start
- Connect Gmail (required) — Email activity stream
- Connect HubSpot (required) — CRM records and deal stages
- Connect Slack (required) — Team notifications and task handoffs
- Connect Linear (required) — Tracked commitments and tasks
- Attach Loop runner (required) — Self-pace iterations and run checks between passes.
- Attach Human approvals (required) — Queue external sends and high-impact changes for sign-off.
- Attach Sales operations (required) — Manage pipeline, CRM updates, and follow-ups.
- Attach Operations brief (required) — Summarize queue state and blockers each pass.
- Google Calendar (read via plugin) — Meetings and scheduling context
- MCP clients (write via mcp) — Terminal and agent dispatch
- Webhooks (read via api) — Product and support event stream

## Steps
1. Aggregate activity: Pull emails, meetings, notes, calls, and webhooks from team and agents into one structured account stream. [tools: Gmail, HubSpot, Webhooks]
2. Extract next actions: AI suggests follow-ups and commitments from the activity graph — surface what needs to happen next per account. [tools: HubSpot, Linear]
3. Queue tracked tasks: Turn commitments into tasks with context; reps, agents, and MCP clients share one queue with source links. [tools: Linear, MCP clients]
4. Execute from anywhere: Create records, update fields, and dispatch tasks via keyboard-first bar, terminal, or MCP without breaking flow. [tools: HubSpot, MCP clients]
5. Sync the stack: Connect CRM, email, calendar, and tools so the activity graph stays complete and bidirectionally current. [tools: Gmail, HubSpot, Google Calendar]

Self-pace this loop. After each iteration, run the check command, read the output, and only continue if the exit condition is not met. Stop when the exit condition passes or max iterations is reached. Give a short status update each pass.

Guardrails:
- Do not auto-send customer-facing emails or messages without human approval unless pre-approved templates apply
- Preserve full account context when creating tasks — link back to source activity
- Do not overwrite CRM fields without explicit approval for high-impact changes (deal stage, amount, owner)
- Escalate ambiguous next actions to human rep rather than guessing
- API and MCP actions must be auditable with actor (human vs agent) recorded