Slack
Push a recap after the call, or a set of approved findings after review, and the message arrives formatted: severity markers, verbatim quotes, and links that open the exact moment. Setup is two minutes and one channel invite.
- Updated
- 8 October 2026
- Read
- 4 min
- Needs
- Workspace admin; paid plan to push
Five steps.
Public channels work out of the box; private channels need one /invite.
Open the integrations settings
Settings, then Integrations under Push destinations. Connecting needs a workspace admin or owner and, on the Slack side, permission to install an app in the Slack workspace (some workspaces route this through admin approval).
Settings, then Integrations. Connect Slack from its card and choose the channel before sending anything. Connect Slack
On the Slack card, choose Connect and approve the requested access: posting messages and reading the channel list, shown in the dialog before you approve. Connecting posts nothing.
Pick the channel
The picker lists your channels live. Public channels work immediately. Private channels appear only after you invite the Citesvue app to them in Slack (/invite in the channel), which is deliberate: a private channel opts in explicitly.
Confirm the card reads connected
The card shows the Slack workspace name and the chosen channel. Nothing is posted until you push something.
Send something
From any recording: push a finding, a set of findings, the recap, or a cited Q&A answer. The app confirms "Queued", and the message lands formatted, with severity markers, per-finding evidence quotes, and links that open the exact moment in Citesvue.
Four kinds of content, formatted for the channel.
- A single finding
- Type, severity, title, description, and the evidence quote, with a link to the moment.
- A set of findings
- One message, severity-ordered. Very large sets say "and N more findings" with a link to the rest rather than flooding the channel.
- Recap
- Overview, decisions, action items with owners, and topics, readable in the channel without opening anything.
- A cited Q&A answer
- The question, the answer, and each citation with its quote and timestamped link.
Transcripts and full reports are not Slack content: a channel is the wrong place for 12,000 words. Send those to Notion or export them, and let Slack carry the things a channel acts on.
The errors say what to do, verbatim.
Slack failures are almost always channel membership. The messages name the fix.
"Citesvue is not a member of that channel"
Invite the app to the channel in Slack, or pick a public channel. This is the most common failure and the fix is one /invite.
"That Slack channel no longer exists or the app cannot see it"
The channel was deleted, archived, or made private without inviting the app. Pick the channel again from the card.
"That Slack channel is archived"
Archived channels cannot receive messages. Pick an active channel.
"Reconnect needed" on the card
The Slack authorisation was revoked or the app was removed from the workspace. Reconnect from the card.
Slack integration, answered.
A paid Citesvue plan to push (connecting works on every plan), the workspace admin role in Citesvue, and permission to install apps in your Slack workspace, or a Slack admin willing to approve it.
Connecting over Slack sign-in posts nothing. The one exception: if you connect by pasting a Slack incoming-webhook URL instead, Citesvue sends a single confirmation message, because that is the only way a webhook can be checked.
Yes, once the Citesvue app is invited to that channel in Slack. Private channels never appear in the picker before the invite: membership is the permission.
No. Slack deliveries are notifications: each push posts a new message, so the channel history reflects what was shared when. For a canonical, updatable record, deliver to Notion or a tracker alongside.
A workspace holds one Slack connection with one chosen channel at a time. Point it at the channel where findings get acted on; admins can change the channel from the card whenever needed.