Skip to content
Per-pair page

Connect Box to Gmail in two minutes.

Real-time triggers from Box, ready-made actions in Gmail. 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
Gmail as the action

Workflows do something in Gmail, instantly.

See all 27 actions →
Both directions

Pick the way that fits your stack.

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

BoxGmail

When something happens in Box, do it in Gmail.

3 Box triggers wired to 27 Gmail actions. Most-used pairing: File DownloadedAdd Labels to Message.

GmailBox

Or fire it the other way around.

1 Gmail triggers wired to 6 Box actions downstream.

See GmailBox
Popular pairings

Common Box → Gmail workflows.

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

Showing 9 of 81 combinations
When file downloaded in Box, add labels to message in Gmail.

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, create draft in Gmail.

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, create label in Gmail.

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, delete draft in Gmail.

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, add labels to message in Gmail.

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, create draft in Gmail.

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, create label in Gmail.

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, delete draft in Gmail.

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, add labels to message in Gmail.

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 Gmail in five steps.

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

  1. 1
    Connect
    Authorize Box and Gmail

    Open Tiny Command, authorize Box and Gmail 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 Gmail action

    Drop the Gmail → Add Labels to Message action below it. Map fields from the Box payload into the Gmail inputs.

    google-gmail.add-labels
  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 + Gmail.

How long does it take to connect Box and Gmail on Tiny Command?
Under two minutes. Authorize Box and Gmail once each, drop the Box trigger and Gmail action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.
Is the Box ↔ Gmail integration real-time?
Yes. Both Box and Gmail 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 Gmail?
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 Gmail.
What Box events can trigger a Gmail 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 Gmail?
No. There's a free tier that covers most Box+Gmail use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.
What if I want Gmail → Box instead?
Build it the same way, in reverse. There's a dedicated /integrations/google-gmail/with/box page with the reverse-direction triggers and actions.
Related

Other apps that pair well with Box.


Wire Box to Gmail in 2 minutes.

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