Sections11
Reading time8 min
EvidenceWorking integration

/api/integrations/slack/*

Slack already holds the documents that teams pass around during reviews. DynamiteDocs imports supported files from one enabled channel and responds to export commands where the connected Slack user writes them. Each customer authorizes their own workspace. Tokens stay encrypted, and channels must invite the app.

Slack channels, permissions, and delivery

  • Downloading a file from Slack, finding the upload screen, and returning with a spreadsheet creates avoidable handoffs.
  • A bot should not read every channel in a workspace. Teams need to invite it only where the workflow belongs.
  • A posted table should come from a reviewed extraction, not an unchecked first pass.
  • Workspace administrators need to see the exact permissions before approving the connection.

Connect Slack in five steps

Dynamite Docs logoDynamite Docs
The handoff
Document attachment: Documents in SlackOpen Slack from Apps. Authorize your workspace. Invite the app to a channel. Choose intake or delivery. Run a small test. Illustrative example, not extracted customer data.A REVIEWED DOCUMENT, CONNECTED TO YOUR WORKSOURCE DOCUMENTDocumentattachmentWorkspace OAutheach customer connect…Channel discoverypublic and private…Dynamite DocsSlackDestinationReview before delivery
  1. 01Open Slack from Apps
  2. 02Authorize your workspace
  3. 03Invite the app to a channel
  4. 04Choose intake or delivery
  5. 05Run a small test
Share a file. Review its data. Illustrative example.
01

Open Slack from Apps

Sign in to DynamiteDocs, open Apps, and choose Slack. The integration is available on Starter, Pro, and Scale plans. You can connect without selecting an extraction first.

02

Authorize your workspace

Choose Connect Slack, select the workspace you want, and review the permissions. Slack may send the request to a workspace administrator. After approval, you return to the same DynamiteDocs dialog with the workspace name shown as connected.

03

Invite the app to a channel

Open the destination channel in Slack and send /invite @DynamiteDocs. Do this for private channels too. The channel picker only lists channels where the app is already a member, so this invitation keeps access narrow and deliberate.

04

Choose intake or delivery

In the Import view, choose one intake channel for supported files shared by the connected Slack user. In the Export view, select a saved extraction and copy its export command.

05

Run a small test

Share a supported document or image in the intake channel and confirm that it reaches the Library. Then paste an export command into a joined channel and open the attachment Slack receives.

What the Slack connection can do

Dynamite Docs logoDynamite Docs
Inside the output
Document attachment: Documents in SlackWorkspace OAuth: each customer connects and approves their own workspace. Channel discovery: public and private channels joined by the app. Reviewed delivery: CSV, JSON, or Excel data posted from a channel command. Illustrative example, not extracted customer data.Extracted fieldsDOCUMENT SCHEMAworkspace_oautheach customer connects and…channel_discoverypublic and private channels…reviewed_deliveryCSV, JSON, or Excel data posted…Documents in SlackDESTINATION FIELDSWorkspace OAuthMap to your destination schemaChannel discoveryMap to your destination schemaReviewed deliveryMap to your destination schemaIllustrative mapping. Confirm the field names accepted by your destination.
Workspace OAuth
each customer connects and approves their own workspace
Channel discovery
public and private channels joined by the app
Reviewed delivery
CSV, JSON, or Excel data posted from a channel command
Share a file. Review its data. Illustrative example.

The connection uses Slack OAuth and stores a separate encrypted installation for each DynamiteDocs account:

Workspace OAutheach customer connects and approves their own workspace
Channel discoverypublic and private channels joined by the app
Reviewed deliveryCSV, JSON, or Excel data posted from a channel command
Channel intakesupported documents imported into the Library
Event verificationSlack signing secret checked against the raw request
Token storageworkspace tokens encrypted with AES-GCM

A realistic example

A practical accounts-payable channel can use both directions:

ActionWhere it happensResult
A controller shares vendor-invoice.pdf#invoice-review in SlackThe file is imported and queued for extraction
An analyst corrects a low-confidence totalDynamiteDocs review workspaceThe saved extraction becomes the approved version
The analyst writes an export command#invoice-review in SlackThe channel receives a file attachment with the reviewed rows

What the Slack connection does and does not do

Does

  • Lists channels that have invited the app and lets the user choose one intake channel.
  • Posts reviewed CSV, JSON, or Excel data and stored source files after an explicit Slack command.
  • Imports supported files from one enabled channel when the connected Slack user shares them.
  • Verifies signed Slack events before accepting imports or commands.

Does not

  • Does not read message history or scan every channel in the workspace.
  • Does not import files shared by every channel member. Intake is tied to the Slack user who connected the account.
  • Does not post an unreviewed extraction automatically.
  • Does not keep Slack tokens in browser storage or plaintext database fields.

Why the channel boundary matters

Slack works best as a handoff point, not a hidden document store. Requiring a channel invitation makes the boundary visible to the people already working there.

A user enables intake for one channel and writes each export request in its destination channel.

Signed events, encrypted workspace tokens, and per-account routing keep a convenient workflow from turning into broad workspace access.

Setup and delivery questions

Extraction guides

Related integrations

Document workflows it feeds

From the blog

Turn one Slack channel into a controlled document handoff.

Connect your workspace, invite DynamiteDocs to a channel, test one document import, and send a reviewed export command in Slack.

Can we save optional cookies?

Essential cookies keep you signed in. With your permission, optional analytics cookies and masked session replays help us understand usage and diagnose errors. Privacy policy. Change your choice anytime in Cookie settings.