// use cases
Slack archive use cases
for teams.
Use Slackscraper when approved channel history needs to become searchable, auditable, exportable, or available to internal tools without over-broad Slack access.
// 01 · DATA TEAMS
Export Slack channels to JSONL.
Turn approved public and private channel history into structured JSONL files with author, timestamp, channel, thread timestamp, deletion status, and manifest checksums.
JSONLcurrent export format
$ slackscraper export create --destination-type object_store --async
output
{
"channel_name": "eng-platform",
"slack_ts": "1779373140.000200",
"author_name": "maya.chen",
"text": "rollback plan is linked in the incident doc"
}// 02 · COMPLIANCE
Slack eDiscovery and audit search.
Search approved channel history by query, channel, actor, and time window. Deletion ledgers, audit events, and checksummed exports give reviewers a stronger evidence trail.
auditedoperator actions
$ slackscraper search "rollback plan" \
--workspace acme \
--channel eng-platform \
--since 2026-05-01output
✓ result handle issued
✓ access profile version checked
✓ export manifest records SHA-256 checksums
// 03 · ARCHIVE
A backup you can actually read.
Backfill approved channels into a canonical store, then produce current-state JSONL exports that are easy to inspect, diff, and retain in customer-controlled storage.
manifestchecksummed output
$ slackscraper export create \
--workspace acme \
--format jsonloutput
exports/tenant_acme/export_01/messages.jsonl
exports/tenant_acme/export_01/manifest.json
manifest.chain_of_custody.excludes_deleted_messages = true
// 04 · RESEARCH
Slack retrieval for agents and research.
Expose approved Slack channel history through REST, CLI, and MCP tools so agents, internal tools, and research workflows can retrieve context without broad workspace access.
MCPagent retrieval
$ slackscraper mcp call search_slack_messages \
--query "deployment rollback"output
search_slack_messages
expand_slack_result
list_slack_channels
get_slack_sync_status
// workflow patterns
Three workflows,
three rollout paths.
“
Start with one approved channel, prove retrieval quality, then expand the access profile only when admins approve more scope.
P
Pilot workflow
Channel-by-channel rollout
“
Use deletion-aware exports when reviewers need portable evidence instead of direct access to the live retrieval surface.
R
Review workflow
JSONL plus manifest
“
Give agents an MCP search tool backed by scoped result handles rather than broad credentials or unbounded Slack access.
A
Agent workflow
MCP retrieval
Need a different Slack archive workflow?
Send the channel scope, export target, and retrieval use case you need to support.
$ plan pilot →