Make failed payment intents visible in Box
A failed payment can call for a quick review. Add a comment to the relevant Box account file so the context is easy to spot.
Trigger
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Action
Create comment
Adds a comment by the user to a specific file, or as a reply to an other comment.
Why this helps
Payment failures can be buried in Stripe while the people handling customer follow-up are working in Box.
- Put a payment issue in the team's Box workspace
- Make account review easier to notice
- Keep the event details beside an existing account file
Setup
Build it in a few focused steps.
- 1Connect Stripe and Box once in the Notis portal.
- 2In Automations, choose New Automation and give it a name.
- 3Tell Notis to comment on the specified Box account file when a payment intent fails, including only relevant details returned by Stripe.
- 4Pick the Stripe Payment Intent Failed trigger and choose where run reports should go.
- 5Test with one real failed payment intent and confirm the comment is useful and accurate.
Questions about this workflow
Will this find the right Box file automatically?
Specify the Box file to comment on in your instruction. The listed action creates a comment on a specific file.
Does a failure always include a reason?
Only include a reason if Stripe returns one with the event. Otherwise, ask Notis to state that the payment intent failed without guessing why.
Can this trigger on all failed payment types?
This workflow uses the Stripe Payment Intent Failed event specifically.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Stripe to Box. A trigger fires from one place; an action lands in another.
Stripe triggers
Box actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add classification to file
Adds a classification to a file by specifying the label of the classification to add. this api can also be called by including the enterprise id in the url explicitly, for example `/files/:id//enterprise 12345/securityclassification-6vmvochwuwo`.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add classification to folder
Adds a classification to a folder by specifying the label of the classification to add. this api can also be called by including the enterprise id in the url explicitly, for example `/folders/:id/enterprise 12345/securityclassification-6vmvochwuwo`.
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
Add domain to list of allowed collaboration domains
Creates a new entry in the list of allowed domains to allow collaboration for.
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
Add initial classifications
When an enterprise does not yet have any classifications, this api call initializes the classification template with an initial set of classifications. if an enterprise already has a classification, the template will already exist and instead an api call should be made to add additional classifications.
Invoice Payment Succeeded Trigger
Triggered when an invoice payment is successful in Stripe
Add or update user avatar
Adds or updates a user avatar.
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Add shared link to file
Adds a shared link to a file.
Product Created Trigger
Triggered when a product is created in Stripe
Add shared link to folder
Adds a shared link to a folder.
Subscription Added Trigger
Triggered when a subscription is added in Stripe
Add shared link to web link
Adds a shared link to a web link.
Connect any two apps with Notis in the middle.
Stripe and Box, 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 Box.