App Logo
slack.com

Export a Slack conversation to a JSON file

Automatically export a Slack conversation to a JSON file on slack.com. Downloads the full accessible history of one Slack conversation as a JSON file, including thread replies. Works for a channel, a direct message, a group message or your own saved messages, addressed by name, by ID or by the other person's handle.

Input

conversation required

What to export. A channel as '#general' or 'general'; any conversation by its ID (C, G or D prefix); a direct message as '@handle' or the other person's user ID; or 'self' for your own saved messages. Display names are rejected because several people can share one, so use a handle or an ID.

expectedUser required

Your Slack handle, display name, or user ID. Checked against the signed-in account before anything is exported.

workspaceDomain required

Workspace hostname, for example acme.slack.com.

maxPages optional

Safety cap across history and reply pages. Exceeding it fails rather than downloading a partial archive.

Default: 10000
inspectOnly optional

Resolve and report the workspace, account and conversation without reading history or downloading anything.

Default: false

Output

account required
workspace required
conversationId required
inspectionOnly required
conversationType required
download optional
pageCount optional
threadCount optional
counterparty optional
messageCount optional
lastTimestamp optional
firstTimestamp optional
conversationName optional
completeForAccessibleHistory optional

FAQ

Downloads the full accessible history of one Slack conversation as a JSON file, including thread replies. Works for a channel, a direct message, a group message or your own saved messages, addressed by name, by ID or by the other person's handle.
Ask an AI agent connected to Reduck to run reduck/slack.com/export_conversation, or run it from a terminal with the Reduck CLI: npx @reduck-ai/cli@latest run --script reduck/slack.com/export_conversation
You do not need one. "Export a Slack conversation to a JSON file" drives the real slack.com pages in a browser, so it works whether or not slack.com offers an API for this.
Required: workspaceDomain, expectedUser, conversation. Optional: maxPages, inspectOnly.
It returns account, download, pageCount, workspace, threadCount, counterparty, messageCount, lastTimestamp, conversationId, firstTimestamp, inspectionOnly, conversationName, conversationType, completeForAccessibleHistory.
Yes. It acts as you on slack.com: on your own Chrome it reuses your session, and on a Reduck-hosted browser it loads the slack.com cookies saved by the Reduck extension.
It only reads. It looks things up on slack.com and changes nothing there.
Ask an AI agent connected to Reduck to run reduck/slack.com/export_conversation, or run it from a terminal with the Reduck CLI: npx @reduck-ai/cli@latest run --script reduck/slack.com/export_conversation
It is part of Reduck's official curated catalogue.

Related scripts

slack.com

Search Slack messages

Full-text search across the workspace's messages, supporting Slack's modifiers (from:@user, in:#channel, before:/after:date, "exact phrase"). One page per call. Requires login.

slack.com

List Slack invoices

List Slack billing statements from the workspace's admin billing history. Returns workspace, total and invoices (date, statement, billId, amount, status, description, pdfUrl) — metadata only. Feed a row's pdfUrl (or billId) to slack.com/download_invoice to fetch that statement's PDF. Requires a workspace billing admin; defaults to the primary workspace, or pass workspaceDomain (e.g. acme.slack.com).

slack.com

Send Slack message

Post a message to a channel or DM, identified by name ('social', '#social'), channel/DM id (C…/D…), or a user (@handle or U…) for a direct message. Pass threadTs to reply inside a thread (with broadcast to also send it to the channel). Returns the new message ts, channel id and permalink. Requires login.

Start building not clicking

Get started for free