Integrations & automations

The command center is API-first so the rest of the toolstack (Grain, Slack, Notion, Attio, Linear) can feed it and read from it through Zapier, Make or n8n.

AI engine

Rules engine (demo mode)

Webhook auth

Open (demo)

Storage

SQLite in-memory + your changes (per browser)

Automation recipes

Grain → Command Center

Trigger

Grain: “Meeting recap ready” webhook

Action

POST the recap to /api/ingest with source=meeting. Action items land in Follow-ups with owners and due dates.

Slack → Command Center

Trigger

Slack: message saved / emoji reaction 📌

Action

Zapier or Make forwards the message text to /api/ingest with source=slack.

Command Center → Slack

Trigger

Schedule: weekdays 7:45 AM ET

Action

POST /api/brief to generate today’s brief, then post the Markdown to the founder’s DM.

Command Center → Notion

Trigger

Schedule: Fridays 4 PM

Action

GET /api/snapshot and upsert OKR progress + open follow-ups into the Notion company wiki (single source of truth).

Attio / Linear

Trigger

Follow-up created with an external partner or an engineering owner

Action

Route partner follow-ups to the Attio record and engineering items to a Linear issue (see the OKR → Linear planner project).

API endpoints

POST/api/ingest

Turn free text into follow-ups. Body: { text, source?: meeting|email|slack, dry_run?: boolean }

curl -X POST https://founder-command-center-jet.vercel.app/api/ingest \
  -H "Content-Type: application/json" \
  -d '{"text":"CTO to share strap test results by Friday","source":"slack","dry_run":true}'

GET/api/snapshot

Compact JSON of OKRs, open follow-ups, decisions, blockers and meetings. Add ?format=full for raw records.

curl https://founder-command-center-jet.vercel.app/api/snapshot

GET/api/brief

Latest daily brief as Markdown.

curl https://founder-command-center-jet.vercel.app/api/brief

POST/api/brief

Generate and store a fresh brief; returns { mode, markdown }.

curl -X POST https://founder-command-center-jet.vercel.app/api/brief