Start free
Per-pair page

Connect Stripe to Box in two minutes.

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

Connect Stripe to Box — start free See reverse direction
Trigger app
Stripe as the trigger

Workflows fire when something happens in Stripe.

See all 10 triggers →
Action app
Box as the action

Workflows do something in Box, instantly.

Connect Stripe to Box — start free
Both directions

Pick the way that fits your stack.

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

Stripe → Box

When something happens in Stripe, do it in Box.

10 Stripe triggers wired to 6 Box actions. Most-used pairing: Charge Failed → Create Folder.

Box → Stripe

Or fire it the other way around.

3 Box triggers wired to 31 Stripe actions downstream.

See Box → Stripe →
Popular pairings

Common Stripe → Box workflows.

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

Showing 9 of 60 combinations
When charge failed in Stripe, create folder in Box.

Fires when a charge attempt fails in Stripe (decline, fraud, insufficient funds). Use to alert the customer, retry, or kick off dunning.

When charge failed in Stripe, download file in Box.

Fires when a charge attempt fails in Stripe (decline, fraud, insufficient funds). Use to alert the customer, retry, or kick off dunning.

When charge failed in Stripe, get file metadata in Box.

Fires when a charge attempt fails in Stripe (decline, fraud, insufficient funds). Use to alert the customer, retry, or kick off dunning.

When charge failed in Stripe, list folder contents in Box.

Fires when a charge attempt fails in Stripe (decline, fraud, insufficient funds). Use to alert the customer, retry, or kick off dunning.

When checkout completed in Stripe, create folder in Box.

Fires when a Stripe Checkout session is completed (regardless of payment async status). Common use: provision the customer, send a receipt, or grant entitlements.

When checkout completed in Stripe, download file in Box.

Fires when a Stripe Checkout session is completed (regardless of payment async status). Common use: provision the customer, send a receipt, or grant entitlements.

When checkout completed in Stripe, get file metadata in Box.

Fires when a Stripe Checkout session is completed (regardless of payment async status). Common use: provision the customer, send a receipt, or grant entitlements.

When checkout completed in Stripe, list folder contents in Box.

Fires when a Stripe Checkout session is completed (regardless of payment async status). Common use: provision the customer, send a receipt, or grant entitlements.

When new customer in Stripe, create folder in Box.

Fires when a new customer is created in Stripe. Use to mirror to your CRM, send a welcome email, or enrich the customer record before first charge.

How it works

Connect Stripe and Box in five steps.

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

  1. 1
    Connect
    Authorize Stripe and Box

    Open TinyCommand, authorize Stripe and Box once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick a Stripe trigger

    Drop the Stripe → Charge Failed trigger onto the canvas. TinyCommand auto-registers the webhook.

    POST /v1/webhooks/stripe.trigger-charge-failed
  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 Box action

    Drop the Box → Create Folder action below it. Map fields from the Stripe payload into the Box inputs.

    box.create-folder
  5. 5
    Publish
    Publish and forget

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

FAQ

Questions about Stripe + Box.

How long does it take to connect Stripe and Box on TinyCommand?
Under two minutes. Authorize Stripe and Box once each, drop the Stripe trigger and Box action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.
Is the Stripe ↔ Box integration real-time?
Yes. Both Stripe and Box 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 Stripe and Box?
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 Box.
What Stripe events can trigger a Box workflow?
Any of the 10 Stripe triggers, including "Charge Failed". Each fires in real time when the matching event happens in Stripe.
Do I need a paid plan to use Stripe with Box?
No. Both integrations come on every plan, including Free, which includes 1,000 credits a month with no credit card. Each workflow step uses 1 credit, and paid plans include more credits and team seats when you need them.
What if I want Box → Stripe instead?
Build it the same way, in reverse. There's a dedicated /integrations/box/with/stripe page with the reverse-direction triggers and actions.
Related

Other apps that pair well with Stripe.

+
Stripe + Gmail
Email
+
Stripe + Slack
Communication
+
Stripe + Google Sheets
Spreadsheets & Databases
+
Stripe + HubSpot
CRM & Sales
+
Stripe + Notion
Productivity
+
Stripe + Airtable
Spreadsheets & Databases
Connect Stripe to Box — start free