synthesis-slack-sync

To sync Slack channels to local transcripts, you run an automated workflow that fetches channel messages, DMs, and group-DMs, then persists them into per-day, per-channel transcript files. This handles day-start, mid-day, and day-end syncs.

Yes, you can generate daily action plans from Slack messages. The sync workflow aggregates channel conversations and direct messages, updating per-person action plans to ensure drafts are grounded in current context.

Slack MCP requires authentication checks before syncing thread transcripts. The automation verifies your MCP credentials successfully before fetching channel messages or persisting local transcripts and action plans.

You configure per-project behavior for Slack transcript sync by creating a .claude/slack-sync.yaml configuration file. This file tailors workflow rules for channel messages, DMs, and thread re-reading to fit your project needs.

To re-read active Slack threads and capture new replies, the sync workflow automatically surfaces thread replies during the day-start, mid-day, or day-end runs, ensuring your local transcripts retain the most current context.

The best way to retain Slack conversation context is using automated per-day, per-channel transcripts. This approach reliably archives daily channel messages and aggregator DMs, preventing manual tracking errors and knowledge loss.