Update Stripe subscriptions from Box collaboration changes
A changed Box collaboration can signal a shift in customer access or agreement terms. Ask Notis to update the corresponding Stripe subscription when the intended change is explicit.
Trigger
Collaboration Details Changed
Triggers when a collaboration's details change (e.g., role, status, expiration). This trigger monitors a specific collaboration and detects when any meaningful field changes, such as role, status, expiration date, access type, or acknowledgment status.
Action
Update Subscription
Updates an existing, non-canceled stripe subscription by its id, ensuring all referenced entity ids (e.g., prices, coupons) are valid and automatic tax liability is correctly specified if enabled.
Why this helps
Customer agreement changes may not reach billing promptly when collaboration updates happen outside Stripe.
- Connect relevant agreement changes to subscription maintenance.
- Reduce manual follow-up after collaboration details change.
- Avoid unsupported changes by requiring a known customer, subscription, and explicit instruction.
Setup
Build it in a few focused steps.
- 1Connect Box and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Describe in one instruction which collaboration changes should update a Stripe subscription, how Notis should identify the subscription, and to report unclear matches or requested changes.
- 4Pick the Box Collaboration Details Changed trigger and choose where run reports should go.
- 5Test with one real collaboration change and verify the subscription in Stripe.
Questions about this workflow
Does a collaboration role map directly to a Stripe plan?
No mapping is provided automatically. Your instruction must state how a meaningful Box change relates to a supported Stripe subscription update, with any required Stripe identifiers and price details.
Can this cancel the subscription?
This package uses the Update Subscription action. To cancel at the end of the current billing period, use a separate workflow with the cancel subscription action.
What if the Box event does not identify a subscription?
Notis should report that it could not confidently find the subscription rather than update a guessed record.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Box to Stripe. A trigger fires from one place; an action lands in another.
Box triggers
Stripe actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Cancel subscription
Cancels a customer's active stripe subscription at the end of the current billing period, with options to invoice immediately for metered usage and prorate charges for unused time.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Confirm payment intent
Confirms a stripe paymentintent to finalize a payment; a `return url` is necessary if the payment method requires customer redirection.
Collaboration Details Changed
Triggers when a collaboration's details change (e.g., role, status, expiration). This trigger monitors a specific collaboration and detects when any meaningful field changes, such as role, status, expiration date, access type, or acknowledgment status.
Create Customer
Creates a new customer in stripe, required for creating charges or subscriptions; an email is highly recommended for customer communications.
Comment Changed
Triggers when a comment's content or details change in Box. This trigger monitors a specific Box comment and detects when any meaningful field changes, such as message text edits, tagged message changes, or modification timestamp updates.
Create an invoice
Creates a new draft stripe invoice for a customer; use to revise an existing invoice, bill for a specific subscription (which must belong to the customer), or apply detailed customizations.
New File Comment Added
Triggers when a new comment is added to a file in Box. This trigger monitors a specific Box file and fires when new comments are detected.
Create payment intent
Creates a stripe paymentintent to initiate and process a customer's payment; using `application fee amount` for a connected account requires the `stripe-account` header.
File Metadata Changed
Triggers when a file's metadata or properties change in Box. This trigger monitors a specific Box file and fires when changes are detected in key fields like name, description, size, modification time, parent folder, or status.
Create a price
Creates a new stripe price for a product, defining its charges (one-time or recurring) and billing scheme; requires either an existing `product` id or `product data`.
File Shared Link Changed
Triggers when a file's shared link settings change in Box. This trigger monitors a specific Box file's shared link and fires when changes are detected in the shared link configuration, such as access level, permissions, password protection, expiration date, or vanity URL.
Create product
Creates a new product in stripe, encoding the request as `application/x-www-form-urlencoded` by flattening nested structures.
New File Version Uploaded
Triggers when a new file version is uploaded to a file in Box. This trigger monitors a specific Box file and fires when new versions are detected.
Create Refund
Creates a full or partial refund in stripe, targeting either a specific charge id or a payment intent id.
Connect any two apps with Notis in the middle.
Box and Stripe, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Stripe.