Slack

Slack connects as a company-scoped connector. One admin install authorises the Qorpera bot across the workspace; channel-level mapping determines which channels feed into which departments in the wiki.

What syncs

Channel messages and threads sync as content and activity. Messages are grouped into threads so a multi-turn conversation becomes a single reasoning context rather than a sequence of fragments. Thread participants resolve to person entities; the conversation feeds the entities’ activity streams.

Direct messages do not sync by default — Qorpera only sees what the admin explicitly maps to departments.

Channel mapping

The SlackChannelMapping table links each synced channel to a department. This matters for:

• Scope. Members see only the channels mapped to their departments.
• Routing. Situations detected from a channel route to that channel’s department by default.
• Privacy. Unmapped channels are excluded from sync entirely — you don’t have to trust the AI with channels you never wanted it in.

Situation detection

Incoming Slack messages trigger real-time content-based situation detection. Commitment language, escalation patterns, and action items in Slack threads surface as situations in the affected department’s My Work.

Write-back

Two actions are available when write-back is enabled:

• send_slack_message — post a new message to a mapped channel.
• react_to_message — add a reaction to an existing message.

All write-back goes through the Qorpera bot account, clearly attributable as AI-generated.