Find the contact behind a canceled subscription
When a subscription ends, get the customer record in view before deciding whether a personal follow-up makes sense.
Trigger
Subscription Deleted Trigger
Triggered when a subscription is deleted in Stripe
Action
Get Contacts
This tool retrieves a list of contacts from amcards. it is used for managing contacts by providing details like limit, skip, and filters (e.g., last name, first name, email). the tool returns an array of contact objects containing fields such as id, first name, last name, email, created at, and updated at.
Why this helps
A cancellation can deserve a thoughtful review, but finding the right person often means another round of searching.
- Quickly look for the customer in Amcards after a subscription ends.
- Keep the contact lookup attached to a retention review report.
- Avoid assuming a reason for cancellation when the event does not provide one.
Setup
Build it in a few focused steps.
- 1Connect Stripe and Amcards once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for cancellation review.
- 3Ask Notis to search Amcards contacts using customer details in the deleted subscription event and summarize matches without inferring a cancellation reason.
- 4Choose the Stripe Subscription Deleted trigger and select where run reports should go.
- 5Test with one real deleted subscription and review the match and any missing data.
Questions about this workflow
Will the workflow tell me why a subscriber canceled?
Only if a reason is provided in the event data or your prompt context. The listed trigger description does not promise a cancellation reason.
Does it send a retention card?
No. This workflow uses the Amcards contact retrieval action to identify a possible contact for your review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Stripe to Amcards. A trigger fires from one place; an action lands in another.
Stripe triggers
Amcards actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Cards
This tool retrieves a list of all cards associated with the authenticated account. the action is completely independent and doesn't require any external resource ids or parameters beyond authentication. it allows users to monitor, track, and manage their cards.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Contacts
This tool retrieves a list of contacts from amcards. it is used for managing contacts by providing details like limit, skip, and filters (e.g., last name, first name, email). the tool returns an array of contact objects containing fields such as id, first name, last name, email, created at, and updated at.
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 Amcards, 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 Amcards.