Knowledge & operationsBLoc Slack Workbench11 min read

Extracting Slack Contacts, Organizing Channel Attachments, and Reviewing Thread Evidence

Extract Slack email addresses to CSV, organize document attachments by channel and year, and review thread evidence locally with checkpoint resume.

Executive summary · 11 min read
  • Extract unique addresses from messages, threads, and attachments into one deduplicated CSV.
  • Collect PDF, Word, Excel, and PowerPoint attachments organized by channel and year, with per-year checkpoint progress.
  • Stop run pauses extraction at a checkpoint; Exit app closes the local server — closing the browser tab does neither.
  • Thread Review works on supplied evidence and never posts back to Slack; online analysis requires explicit opt-in.
Session Completeness & Supplied Evidence: Always inspect skipped or failed attachment logs before treating a Slack extraction run as complete, as workspace permissions and session tokens govern what can be read. Thread Review operates on supplied or pasted conversation evidence locally (unless online provider analysis is explicitly authorized) and never posts back to Slack.

Slack accumulates the operational record most teams never intended to keep: contact addresses buried in introductions, decision documents attached to threads, and the conversation context around both. When someone leaves, a contract ends, or an audit begins, that record needs to leave the platform in a usable form. BLoc Slack Workbench is a Windows local browser application with two extraction workflows and a review workflow, all running with your own authorized Slack access and workspace permissions.

Why Slack evidence gets lost

  • Contacts are scattered. A partner's real address appears once, in a forwarded message, in a thread from two years ago. Search finds it only if you already know it exists.
  • Attachments are organized by accident. The contract PDF lives wherever the channel lives; nothing groups the documents a project produced across channels and years.
  • Threads hold decisions. The scope change everyone agreed to, and the question that was never answered, sit mid-thread where nobody reports from.
  • Browser tabs are not archives. Closing a tab loses nothing in Slack but everything in your review state.

The common thread is that Slack's value decays with membership: every departed admin, archived channel, and plan change makes tomorrow's export harder than today's. Extraction converts that decaying record into files you control while it is still cheap to do so.

Three workflows in one local interface

You choose Email addresses or Document attachments in the same local browser interface, and Thread Review works on supplied evidence. The table summarizes what each consumes and produces.

In a typical engagement the workflows run in order: extract the address list first because it is fast and defines the contact universe, collect attachments per year because those runs are long, and review thread evidence last once you know which conversations matter. Nothing prevents running them independently — they share the interface, not their state.

The permission boundary is worth restating before any run: extraction reaches exactly what your own authorized Slack access and workspace permissions can see, and no more. An empty result set is information — either the addresses are not in the accessible history, or the channels that hold them sit outside your permissions. Check which before concluding the data is not there.

WorkflowInputOutputControls
Email address extractionAccessible messages, threads, and attachmentsCSV of unique addressesLive activity, Stop run, checkpoint resume
Document attachment collectionPDF, Word, Excel, and PowerPoint files per type, date, and channel rulesAttachment folders organized by channel and yearPer-year saved progress and resume
Thread reviewSupplied or pasted conversation evidenceDecisions, actions, and unresolved questionsLocal review or explicit online opt-in

Extracting email addresses to CSV

Email address extraction walks accessible messages, threads, and attachments and collects unique addresses into a CSV. Uniqueness is the point: the same address surfaces dozens of times across channels, and the CSV collapses it to one row you can dedupe, clean, and import into campaign or CRM tooling. Extraction gathers the raw candidates; a cleaning workflow validates and suppresses them before anything is mailed. See the guide on cleaning contact lists and running Classic Outlook campaigns for the downstream half of that pipeline.

What uniqueness means in practice

An address is collected once regardless of how many times it appears: the introduction thread, the forwarded invoice, an attachment body — every occurrence collapses into the same single row. That is deliberate. The CSV is a contact universe, not an activity log; frequency analysis belongs to your tooling, not to this file. Expect the raw list to include addresses you will suppress later — role addresses, excluded domains — and plan the cleaning pass as part of the workflow rather than treating the CSV as final.

Organizing document attachments by channel and year

Document attachment collection gathers supported PDF, Word, Excel, and PowerPoint files from accessible channels, applying the extractor's document-type, date, and channel rules. You choose an output folder and an attachment year; files land organized by channel and year, which turns "all the documents from the 2025 delivery" from a search project into a folder. Separate saved progress tracks different years, so collecting 2024 and 2025 are independent runs you can pause and resume without entangling their checkpoints.

Planning runs by year

Run one year at a time and give each run its own output folder. Year-scoped runs are predictable: a 2025 run with a defined channel set finishes, its checkpoint closes, and the folder is final — while a 2024 run can resume weeks later once a workspace permission question is resolved. If your scope spans several years, treat each year as its own pass and merge folders afterwards; untangling merged checkpoints is not a recovery you want to improvise.

Checkpoints, Stop run, and Exit app

Long extractions are interruptible by design. Live activity shows progress as the run advances; Stop run halts extraction while keeping saved checkpoints; restarting with current credentials resumes from the last checkpoint rather than from zero. Exit app closes the local server itself. The distinction matters operationally: closing the browser tab alone does not stop a run. The local server keeps working, which is exactly what you want when you accidentally close the wrong tab, and not what you want when you believed everything had stopped.

A scenario worth rehearsing with your team: an extraction is running at the end of the day and someone closes the laptop. The tab is gone, the run continues, and the honest question is which state you intended. If the run should stop, reopen the interface and use Stop run; if the machine is being handed over, Exit app closes the server outright. Decide once, write it into your runbook, and stop relitigating it at the end of every run.

Production note: closing the browser tab does not stop a run. Use Stop run to pause extraction at a checkpoint, or Exit app to close the local server — and confirm which one you intended before walking away.

Reviewing thread evidence locally

Thread Review starts from supplied or pasted conversation evidence rather than reading live Slack. It reviews the material for decisions made, actions agreed, and questions left unresolved, and it does so locally by default. If your team wants assisted analysis, sending content to a configured online provider requires explicit opt-in — a deliberate consent step, not a default. The findings are yours to review and act on; Thread Review does not post replies to Slack, so no workflow in the app can speak in your channels.

Preparing evidence for review

Paste complete threads, not excerpts: a decision often hangs on context three messages earlier. Redact what does not belong in the record before supplying it, and settle the local-versus-online question before pasting anything — once content is prepared for an online provider, the consent decision has effectively been made. Review the surfaced decisions, actions, and unresolved questions yourself; the tool structures the evidence, and a human decides what it means.

Operational checklist

  1. Confirm the Slack access and workspace permissions you will use cover the channels in scope.
  2. Run email address extraction across the accessible history and export the unique-address CSV.
  3. Hand the CSV to your cleaning workflow for deduplication, validation, and suppression before any outreach.
  4. Collect document attachments per year, one saved run per year, into a dedicated output folder.
  5. Use Stop run rather than closing the tab when you need to pause; resume with current credentials from the checkpoint.
  6. Paste or supply thread evidence for review and read the decisions, actions, and unresolved questions it surfaces.
  7. Decide explicitly whether any content goes to an online provider; without opt-in, review stays local.
  8. Exit the app when finished so the local server is not left running.

Technical FAQ

Which permissions does extraction use?

Your own. Extraction runs with your authorized Slack access and workspace permissions and follows the extractor's document-type, date, and channel rules. It cannot reach channels your account cannot read.

Why did my run keep going after I closed the tab?

Closing the browser tab does not stop the local server. Use Stop run to pause extraction at a checkpoint, or Exit app to close the server itself, then confirm the state you intended.

Can Thread Review reply for me in Slack?

No. Thread Review analyzes supplied or pasted evidence and surfaces decisions, actions, and unresolved questions for you to review. Nothing in the app posts back to Slack.

How is attachment collection across years isolated?

You choose the attachment year per run, and separate saved progress tracks each year independently, so resuming a 2024 run never disturbs a 2025 run's checkpoints or output folders.

The BLoc Slack Workbench tool page and the interactive walkthrough demonstrate each workflow; use the request form to confirm optional AI setup and edition availability. Related reading: cleaning contact lists and running Classic Outlook campaigns and exporting and auditing Confluence spaces locally.

BLoc Slack Workbench · Slack workflows

Ready to apply this workflow in production?

Extract email addresses and documents from Slack, then review conversation evidence with optional AI assistance. Pricing: $7 / month or $70 / year.

← All 14 localization engineering guides