Walkthrough
How to search Slack and Google Drive together
A practical workflow for turning shared Slack conversations and newly captured Google Drive files into one visibility-aware, cited answer.
Why this needs more than one source
Slack is where a decision is often negotiated. Google Drive is where the durable brief, plan, or final wording often lands. Searching either source alone can return a technically relevant result while hiding the change that made it current.
The reliable pattern is to search an intentionally shared evidence boundary rather than run two independent searches and merge the results by hand. Timeline keeps each captured source distinct, orders it by time, and lets the answer cite both kinds of evidence.
Build the answer step by step.
Each step leaves something concrete to inspect before the next layer adds interpretation.
- 01
Set the evidence boundary
Start with one real project. Select the Slack channels where the work is discussed, then activate the My Drive root or shared drives that contain its documents. Use the project name and stable identifiers in the query to narrow the broader Drive source.
Output
A named project scope inside explicit Slack and Drive sources.
- 02
Capture the source history
Slack messages, threads, edits, reactions, and shared-file signals from selected channels become source events. After Drive activation, supported files that change inside the activated root or shared drives can be mirrored into the document library, while their changes remain visible in event history.
Output
Separate, time-addressable evidence captured after activation.
- 03
Ask a question with edges
Name the project, the date range, and the kind of answer you need. “What changed in the launch plan since Monday, who agreed to it, and which document is current?” is stronger than “What is happening with launch?”
Output
A query that can be checked against a finite body of evidence.
- 04
Read chronology before confidence
Look for the order of events: an early Slack proposal, a later document revision, and any follow-up that confirms or rejects it. Recency matters, but a later message is not automatically more authoritative than an approved document.
Output
A defensible sequence instead of a relevance-ranked pile.
- 05
Inspect and share the answer
Open the citations for consequential claims. If a source is missing or the evidence conflicts, narrow the question or add the missing approved source before sharing the result.
Output
A cited answer with visible gaps, ready for human review.
Evidence example
See the evidence path
The example is illustrative. Its purpose is to make the provenance pattern visible, not to imply customer data or a guaranteed conclusion.
Question
What changed in the Acme rollout plan, and what is still undecided?
Maya Chen approves the onboarding copy in #acme-rollout.
The migration checklist records Friday’s review and Priya Shah as owner.
The rollout thread says pricing language is still open.
The review date and owner are set; pricing is still unresolved.
The migration review is due Friday with Priya Shah as owner. The latest Acme rollout discussion still leaves pricing language open. Source citation 01Source citation 02Source citation 03
- 01Copy approved
- 02Review assigned
- 03Open pricing question
Ask a question with clear edges
Try this question
“For [project], review the selected Slack and Google Drive evidence from [start date] to [end date]. Tell me what changed, which source is current, what remains unresolved, and who owns the next step. Cite every factual claim and call out conflicts instead of resolving them silently.”
A good query fixes the scope, time window, output shape, citation requirement, and treatment of missing or conflicting evidence.
Source roles
What each source contributes
Each source contributes a different part of the answer. Timeline keeps those roles distinct instead of flattening everything into one activity feed.
Slack
Conversation and decision trail
Messages, threads, edits, reactions, and file-sharing signals from selected channels.
What to know
A connection owner shares channels and a team admin activates them. After capture, Timeline event visibility, not each viewer’s Slack membership, controls who can retrieve the evidence.
Google Drive
Durable document context
Supported file bodies and file-change history captured after activation from My Drive root or selected shared drives.
What to know
Existing files that never change after activation are not backfilled. Unsupported or oversized files may contribute metadata without searchable body text; Drive comment activity is not part of the native evidence described here.
Treat authority and recency as separate questions.
A newer Slack message may explain why a document should change, but it does not by itself prove that the approved document changed. A revised file may be current, but it may not capture the dissent or unresolved question around it.
Ask Timeline to name conflicts and identify which source supports each claim. The human reviewing the answer still decides whether a conversation, a signed-off document, or another source is authoritative for the decision at hand.
What this cannot prove
- 01The search boundary is the material your team connected and shared, not every item in either provider.
- 02Drive capture begins with changes after activation; an older file that never changes is not available to this workflow.
- 03A cited answer can expose disagreement; it cannot turn disagreement into approval.
- 04Provider sync and extraction may lag behind the moment a message or file changes.
- 05Ambiguous project names, duplicated documents, and renamed channels require a more explicit query.
- 06Visibility rules still apply to every result. Team membership does not grant access to private evidence.
Common follow-up questions
Does this replace Slack or Google Drive search?
No. Provider search is still useful when you know the exact message or file you need. This workflow is for questions whose answer depends on evidence spread across both systems and whose claims need citations.
Can Timeline see every Slack channel and Drive folder after I connect?
No. A connection owner shares Slack channels and either My Drive root or shared drives, then a team admin activates those sources. Once evidence is captured, Timeline’s team, private, or specific-user visibility determines who can retrieve it; Timeline does not mirror each viewer’s provider membership.
What if Slack and the document disagree?
Ask the answer to show the conflict, the timestamps, and the source of each claim. Do not ask the model to choose an authority rule that your team has not defined.
Related walkthroughs
Try it on one real question
Try it on one project, not the whole company.
Activate one channel and the smallest Drive source available, ask a question about newly changed material that you already know how to verify, and inspect every citation.
Start with one project