Check your ASIN research queue after a failed payment
Payment recovery already needs attention. Let Notis include a fresh list of your chosen ASIN requests in the report so you can handle both follow-ups in one place.
Trigger
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Action
List Collection Requests
Tool to list all requests in a collection (paginated). use when you need to paginate through requests for a specific collection.
Why this helps
Failed payment follow-up competes with other operational work, making it easy to lose sight of ongoing product research.
- Include an ASIN collection snapshot in a failed payment report.
- Keep operational follow-up in one report channel.
- See open research requests without a separate manual check.
Setup
Build it in a few focused steps.
- 1Connect Stripe and Asin data api once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for payment recovery context.
- 3Describe the outcome in one instruction: when a payment intent fails, list requests in the ASIN collection you name and include them in the run report.
- 4Pick the Stripe Payment Intent Failed trigger, then choose where run reports go.
- 5Test with one real failed payment intent and verify the collection list appears in the report.
Questions about this workflow
Will this retry or refund the payment?
No. The target action only lists requests in an Asin data api collection.
Does it know which ASIN request relates to the failed payment?
Only if the returned data and details available to the automation establish that relationship. The action itself lists a collection and does not match payment records to requests.
Can I limit the list to particular requests?
The listed action retrieves collection requests with pagination. Any filtering depends on the returned data and instruction; no request-level filter is configured in the trigger.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Stripe to Asin data api. A trigger fires from one place; an action lands in another.
Stripe triggers
Asin data api actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Clear multiple collection requests
Tool to delete multiple requests from a collection by ids. use when you need to remove a selected set of request entries from an existing collection in a single call.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Collection Requests
Tool to list all requests in a collection (paginated). use when you need to paginate through requests for a specific collection.
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 Asin data api, 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 Asin data api.