Skip to content
Per-pair page

Connect Box to Slack in two minutes.

Real-time triggers from Box, ready-made actions in Slack. Filter, transform, and route without writing a line of code.

Trigger app
Box as the trigger

Workflows fire when something happens in Box.

Action app
Slack as the action

Workflows do something in Slack, instantly.

See all 45 actions →
Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

BoxSlack

When something happens in Box, do it in Slack.

3 Box triggers wired to 45 Slack actions. Most-used pairing: File DownloadedRaw API Request.

SlackBox

Or fire it the other way around.

13 Slack triggers wired to 6 Box actions downstream.

See SlackBox
Popular pairings

Common Box → Slack workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 9 of 135 combinations
When file downloaded in Box, raw api request in Slack.

Fires when a file is downloaded from Box. Useful for audit workflows that need to track "who downloaded which sensitive document when" or for engagement tracking on shared customer-facing content.

When file downloaded in Box, add reaction in Slack.

Fires when a file is downloaded from Box. Useful for audit workflows that need to track "who downloaded which sensitive document when" or for engagement tracking on shared customer-facing content.

When file downloaded in Box, archive channel in Slack.

Fires when a file is downloaded from Box. Useful for audit workflows that need to track "who downloaded which sensitive document when" or for engagement tracking on shared customer-facing content.

When file downloaded in Box, cancel scheduled message in Slack.

Fires when a file is downloaded from Box. Useful for audit workflows that need to track "who downloaded which sensitive document when" or for engagement tracking on shared customer-facing content.

When file uploaded in Box, raw api request in Slack.

Fires when a new file is uploaded to a watched folder. Payload includes filename, size, uploader, parent folder. The base hook for "auto-process new uploads" workflows — OCR receipts, scan for sensitive content, sync to a downstream system.

When file uploaded in Box, add reaction in Slack.

Fires when a new file is uploaded to a watched folder. Payload includes filename, size, uploader, parent folder. The base hook for "auto-process new uploads" workflows — OCR receipts, scan for sensitive content, sync to a downstream system.

When file uploaded in Box, archive channel in Slack.

Fires when a new file is uploaded to a watched folder. Payload includes filename, size, uploader, parent folder. The base hook for "auto-process new uploads" workflows — OCR receipts, scan for sensitive content, sync to a downstream system.

When file uploaded in Box, cancel scheduled message in Slack.

Fires when a new file is uploaded to a watched folder. Payload includes filename, size, uploader, parent folder. The base hook for "auto-process new uploads" workflows — OCR receipts, scan for sensitive content, sync to a downstream system.

When folder created in Box, raw api request in Slack.

Fires when a new folder is created inside a watched parent. Useful for "new client folder → auto-populate with intake checklist templates" provisioning workflows.

How it works

Connect Box and Slack in five steps.

No code, no glue, no half-day setup. Each step is one click.

  1. 1
    Connect
    Authorize Box and Slack

    Open Tiny Command, authorize Box and Slack once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick a Box trigger

    Drop the Box → File Downloaded trigger onto the canvas. Tiny Command auto-registers the webhook.

    POST /v1/webhooks/box.trigger-file-downloaded
  3. 3
    Transform
    Add a filter or AI step

    Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.

  4. 4
    Action
    Add the Slack action

    Drop the Slack → Raw API Request action below it. Map fields from the Box payload into the Slack inputs.

    slack.api-request
  5. 5
    Publish
    Publish and forget

    Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Box + Slack.

How long does it take to connect Box and Slack on Tiny Command?
Under two minutes. Authorize Box and Slack once each, drop the Box trigger and Slack action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.
Is the Box ↔ Slack integration real-time?
Yes. Both Box and Slack expose webhooks, so events from one fire workflows in the other within seconds rather than on a polling interval.
Can I filter or transform data between Box and Slack?
Yes. Add a Filter node to only pass through matching events, a Switch node to branch by value, or an AI / Code node to transform payloads before they hit Slack.
What Box events can trigger a Slack workflow?
Any of the 3 Box triggers, including "File Downloaded". Each fires in real time when the matching event happens in Box.
Do I need a paid plan to use Box with Slack?
No. There's a free tier that covers most Box+Slack use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.
What if I want Slack → Box instead?
Build it the same way, in reverse. There's a dedicated /integrations/slack/with/box page with the reverse-direction triggers and actions.
Related

Other apps that pair well with Box.


Wire Box to Slack in 2 minutes.

Free tier available. No credit card. No onboarding call.