Clear selected ASIN requests when a subscription ends
When a subscription ends, a known set of related research requests may no longer need to stay in the collection. Tell Notis which request IDs to remove and review the run report.
Trigger
Subscription Deleted Trigger
Triggered when a subscription is deleted in Stripe
Action
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.
Why this helps
Requests tied to ended accounts can remain in a shared research collection and create unnecessary review work.
- Remove a selected set of request entries from an existing collection.
- Reduce stale research items in a shared collection.
- Automate cleanup when a Stripe subscription is deleted.
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 subscription-end cleanup.
- 3Describe the outcome in one instruction: when a subscription is deleted, clear only the ASIN collection request IDs you provide from the named collection.
- 4Pick the Stripe Subscription Deleted trigger, then choose where run reports go.
- 5Test with one real subscription deletion and confirm the intended request IDs are removed.
Questions about this workflow
Can the workflow discover which request IDs belong to the deleted subscription?
The clear action requires request IDs. Supply those IDs or another supported source of them in your instruction; the listed action does not identify related requests by itself.
Does it clear every request in the collection?
No. The action deletes multiple selected requests by IDs from a collection.
Can I undo a cleared request?
The available action deletes selected entries. Confirm the IDs in your instruction and inspect the run report; no restore action is listed here.
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.