A walkthrough of how Slackscraper connects to Slack, backfills approved channels, applies message events, and produces JSONL exports with evidence.
OAuth handshake with your workspace. We request read-only channel history, channel metadata, and user lookup scopes for approved channels. A workspace admin approves and we never ask for write access — we cannot send messages, modify channels, or impersonate users.
Slackscraper crawls every channel you authorize, in parallel, respecting rate limits. Backfill is resumable: if the connection drops, it picks up where it left off. Idempotent: re-running it never duplicates a message.
After backfill, Slackscraper accepts signed Slack Events API callbacks for channel messages. Creates, edits, and deletions update the canonical store and preserve deletion tombstones.
Create current-state JSONL exports from the governed store. Export jobs can write local artifacts or S3-compatible object-store objects with manifest checksums and access-profile scoping.
We cannot send messages, modify channels, or impersonate users. Period.
TLS 1.3 from Slack to us. TLS 1.3 from us to your destination. Always.
Messages live in the configured store for retrieval, deletion handling, and export generation.
An admin can remove the app at any time. We stop receiving events immediately.
Tenant and workspace keys are enforced through repositories, authorization checks, and operational review.
The hosted ingestion path is intentionally focused on approved public and private channels.
JSONL exports include manifest files, record counts, checksums, and chain-of-custody metadata.
Credential, access profile, deletion, export, job replay, and operations actions are audited.
Start with a scoped pilot. Confirm approved channels, run one sync, and review exported JSONL evidence.
Plan a pilot →