Gmail → Slack operations router

Feb 2026 · INTERNAL · integration · The Contentment Foundation

Moved operational email into Slack with deduplication and thread detection, not forwarding. Confirmed running and being refined through May 2026.

Problem

Important operational email lived outside the team's working environment. Forwarding everything to Slack created noise: truncated bodies, reply-thread clutter, and auto-replies mixed in with real work.

Intervention

Built as an operations system rather than an inbox dump: message filtering, thread and reply detection, noise suppression, body extraction, and routing logic, so work is owned where the team already works.

Result

• Operational email owned in Slack instead of a side inbox
• RFC Message-ID deduplication with a seven-day lookback
• Controlled batch processing that preserves unread state
• Fuller email-body visibility, less thread noise, auto-replies filtered

Stack: Gmail, Google Workspace, Slack API, Routing Logic