Keep link context close when a payment fails
A failed payment can leave several loose ends. Get a current snapshot of your recent Cutt.ly links in the same report that flags the Stripe failure.
Trigger
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Action
View Last Shortened URLs
This action retrieves a list of recently shortened urls from your cutt.ly account. it allows users to view their latest shortened links and their details. note: due to api limitations, this action may not return all historical urls. for complete history, please use the cutt.ly dashboard.
Why this helps
After a failed payment, switching between Stripe and Cutt.ly to find related link context adds another task to an already busy day.
- See recently shortened links while reviewing a failed payment
- Keep the payment issue and link snapshot in one run report
- Reduce manual app switching during follow-up
Setup
Build it in a few focused steps.
- 1Connect Stripe and Cutt.ly once in the Notis portal.
- 2Create an automation from Automations, New Automation, then give it a name and prompt.
- 3In one instruction, ask Notis to retrieve recently shortened Cutt.ly URLs when a Stripe payment intent fails and include them in the run report.
- 4Pick the Stripe Payment Intent Failed trigger and choose where run reports go.
- 5Test with one real failed payment example.
Questions about this workflow
Does this identify which short link caused the failed payment?
No. The available Cutt.ly action returns recently shortened URLs, and the Stripe event is a failed payment intent. It does not establish a relationship between a specific URL and the failure.
Will the action return every link in my Cutt.ly account?
No. The action may not return all historical URLs due to API limitations. Use the Cutt.ly dashboard for complete history.
Can I ask Notis to include a concise link snapshot in its report?
Yes. Describe the desired summary in the automation prompt. Notis can summarize the returned list without adding unsupported link attribution.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Stripe to Cutt ly. A trigger fires from one place; an action lands in another.
Stripe triggers
Cutt ly actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
View Last Shortened URLs
This action retrieves a list of recently shortened urls from your cutt.ly account. it allows users to view their latest shortened links and their details. note: due to api limitations, this action may not return all historical urls. for complete history, please use the cutt.ly dashboard.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
Invoice Payment Succeeded Trigger
Triggered when an invoice payment is successful in Stripe
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Product Created Trigger
Triggered when a product is created in Stripe
Subscription Added Trigger
Triggered when a subscription is added in Stripe
Connect any two apps with Notis in the middle.
Stripe and Cutt ly, 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 Cutt ly.