Meeting Sync (Circleback)
Meeting transcripts from Circleback auto-imported as markdown with attendee detection, auto-tagging, and entity propagation. The richest signal source - 5-10 entities per meeting.
Why Meetings Are High-Value
A 30-minute meeting mentions 5-10 people, 3-5 companies, and generates 2-3 action items. Each should propagate to relevant wiki pages. Without this integration, meetings are black holes. With it, every meeting compounds the wiki. Source: scripts/sync-meetings.ts; recipes/meeting-sync.md
Usage
npx tsx scripts/sync-meetings.ts # sync last 7 days
npx tsx scripts/sync-meetings.ts --days 30 # last 30 days
npx tsx scripts/sync-meetings.ts --start 2026-01-01 --end 2026-04-12
Requires CIRCLEBACK_TOKEN environment variable. Get it from
https://app.circleback.ai → Settings → API.
Output
Meeting pages at raw/meetings/{YYYY-MM-DD}-{slug}.md with:
- Frontmatter: title, date, duration, source_id, attendees, tags
- Summary (from Circleback AI)
- Attendees list (filtered - no conference rooms or mailing lists)
- Action items with assignees
- Full transcript with speaker labels
Auto-Tagging
Meeting titles → tags: "1:1" → 1on1, "standup"/"sync" → sync, "board" → board,
"interview" → interview, "retro" → retro, "demo" → demo.
Circleback API
Uses JSONRPC 2.0 over SSE with double-JSON encoding. The collector handles the parsing automatically. This is the most common failure point if implementing manually.
Cost
$0-17/mo. Circleback free tier: 10 meetings/mo. Pro ($17/mo): unlimited.
Timeline
- 2026-06-17 | Added inline provenance and linked the page to its recipe and automation. Source: scripts/sync-meetings.ts; recipes/meeting-sync.md; automations/meeting-sync.md
- 2026-04-12 | Created. Recipe at
recipes/meeting-sync.md, automation atautomations/meeting-sync.md. Source: scripts/sync-meetings.ts