Find the right Amcards contact after a failed charge
A failed payment needs attention. Let Notis check Amcards for the customer so you can act without hunting through two systems.
Trigger
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
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
Switching between Stripe and a mailing list to identify who needs a payment follow-up creates extra work and makes it easier to miss someone.
- Quickly surface a likely contact using customer details included with the charge event.
- Keep the lookup attached to the failed payment run report.
- Reduce manual searching before deciding how to follow up.
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 give it a clear name.
- 3Tell Notis to search Amcards contacts using the customer details available in a failed charge event, then summarize likely matches and missing details.
- 4Choose the Stripe Charge Failed trigger and select where run reports should go.
- 5Test with one real failed charge and review the contact match.
Questions about this workflow
Does this workflow retry the failed payment?
No. The available Amcards action retrieves contacts. It can help identify a contact for follow-up, but it does not retry a Stripe payment.
What if the failed charge has no customer email?
Notis can report that the event lacks a usable identifier. Provide another search clue in your prompt if your event includes one.
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.