Internal Ops (Slack)
Internal Ops (Slack Bot)
Section titled “Internal Ops (Slack Bot)”ClinicFlow manages internal clinic operations, infrastructure alerts, and deployment tracking via a standalone Slack Bot.
To maintain decoupling from the core patient-facing API, the Slack Bot lives in its own repository root folder (/slack-bot/) and uses the @slack/web-api SDK.
Slack Workflows
Section titled “Slack Workflows”While the Node app handles custom events, routine operational sequences are defined declaratively as JSON schemas in the /slack_workflows/ directory (using the 2026.1 Slack schema version).
1. Urgent Support Escalation (urgent_escalation.json)
Section titled “1. Urgent Support Escalation (urgent_escalation.json)”This workflow is triggered when a team member adds a red circle (🔴) reaction to a message. It automatically captures the original message text, the user ID, and the message link, and broadcasts it to a dedicated triage channel.
2. Daily Reflection (daily_reflection.json)
Section titled “2. Daily Reflection (daily_reflection.json)”An automated end-of-day check-in that pings the team. It uses slack#/functions/send_message to ask:
- What was your biggest win today?
- Any blockers for tomorrow?
3. Client Celebrations (new_client_celebration.json)
Section titled “3. Client Celebrations (new_client_celebration.json)”A webhook-triggered event fired by the backend whenever a new clinic completes their onboarding phase and signs their first active patient.