What it does
A lot of deal activity happens in Slack: the account channel where your team coordinates, the thread where a customer's requirement gets restated, the message flagging that a champion has left. None of that normally reaches your CRM.
The Slack integration brings your public Slack channel activity into Databook, so that conversation record becomes part of an account's intelligence, alongside your CRM data, call transcripts, third-party data and Databook's own insights.
What it can do:
Read your public Slack channels on a schedule. Databook reads messages, channels and user records from your workspace, on a recurring sync rather than in real time.
Match Slack activity to the right account. Channels are mapped to accounts using your CRM data, and Slack users are matched to Databook users so the same person is recognized across sources.
Surface Slack activity on the account timeline. Once a channel is mapped, its messages appear alongside events from your other connected systems, tagged with Slack as their source.
Ground Databook's AI and recommendations in what's actually happening. Because Slack often carries deal movement and internal reasoning that hasn't been logged anywhere else yet, it helps keep Databook's answers and recommendations current between calls and CRM updates.
The Slack integration is designed to support Databook's context graph and GTM Decision System.
Why it's useful
It covers the gaps between formal touchpoints. A deal moves in the days between calls, and that movement is usually discussed in Slack before it's logged anywhere else.
It carries internal reasoning, not just customer-facing statements. What your team believes about a deal's risk is often only written down in a channel.
It's timely. Messages are available on the sync schedule rather than waiting on call processing and transcription.
What Databook reads
Data | What it contains | Notes |
Channels | Channel name, identifier, topic, purpose and membership metadata | Public channels only. Channel naming is a significant input to account mapping |
Messages | Message text, author, timestamp, channel and thread position | One record per message, including threaded replies |
Users | Slack user name, display name, email and active status | Used to match Slack authors to Databook users and to your CRM contacts |
Access is read only. Databook does not post, edit or delete anything in Slack.
What's excluded
Rule | What it excludes |
Public channels only | Private channels, direct messages and group DMs. Databook cannot read them and doesn't request the permissions that would allow it to |
No account linkage | Public channels that can't be mapped to a CRM account. Without an account, there's nowhere for the conversation to attach |
Expect only a small share of your overall Slack traffic to reach an account timeline. General company channels, social channels and engineering channels all drop out at the account-mapping step. That's by design.
Where Slack data shows up
Slack data appears in your GTM Decision System instance, for example in:
Account timelines. Slack-derived events appear on the account timeline, tagged with Slack as their source, so you can tell them apart from events from your other connected systems.
Databook conversations, agents and coaches. Because context graph records are queryable, Databook can ground answers and recommendations in recent channel activity rather than static data alone.
Each customer's Slack data lands in a separate, isolated catalog. Slack data is never pooled across customers.
What you'll need in place
A Slack workspace and an administrator who can approve app installation. Many enterprise workspaces restrict who can install apps, and some require an admin to approve an install request before the app can be added at all.
Access to the Databook GTM Control Center Admin Console, to run the install from the Integrations page.
CRM connected to Databook. Account mapping runs through your CRM records. Without CRM data, channels can't be mapped to accounts and nothing reaches a timeline.
Public account channels. If your account channels are private, the integration won't have anything to read from them in its current form.
See Connecting Slack to Databook for the full setup steps.
Limitations worth knowing
One way and read only. Nothing is written back into Slack.
Public channels only. If your account conversations happen in private channels, please discuss this with your Databook account manager.
Account mapping depends on channel conventions. A disciplined naming convention for account channels produces materially better mapping. Worth reviewing before you turn this on.
Message quality is yours. Extraction quality depends on what people actually write. Channels used mainly for link sharing and reactions produce little.
Common questions
Question | Answer |
Can Databook read our private channels? | No. The integration reads public channels only, and doesn't hold the permissions needed to read private channels or DMs. |
Can Databook read our direct messages? | No, for the same reason. |
Will Databook post in our Slack? | No. Access is read only. |
Who inside our company can see what Databook reads from Slack? | Anyone with access to the relevant account in your Databook tenant. Public channel content is already visible to your whole workspace, so this doesn't widen access, but it's worth knowing. |
Why is this channel missing from the timeline? | Almost always one of two reasons: the channel is private, or it couldn't be mapped to a CRM account. |
Does Databook store our full message history? | Messages from eligible public channels are ingested into your own isolated data catalog and used to build your account intelligence. |