Check whether a Stripe checkout buyer is in Amcards
Know whether a new buyer already appears in your contacts before you plan the next conversation.
Trigger
Checkout Session Completed Trigger
Triggered when a checkout session is completed 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 completed checkout can be easy to celebrate and easy to forget to add to your customer context.
- Check for an existing contact after a completed checkout.
- Keep the buyer lookup tied to the checkout event.
- See when the checkout details do not include enough information to identify a contact.
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.
- 3In one instruction, ask Notis to search Amcards for the completed checkout buyer using available customer details and summarize likely matches.
- 4Choose the Stripe Checkout Session Completed trigger and select where run reports should go.
- 5Test with one real completed checkout and review the result.
Questions about this workflow
Does it add the buyer to Amcards if no match exists?
No. The available action only retrieves contacts. It can report that no likely match was found.
Can it determine what the buyer purchased?
Notis can use details included in the Stripe event. If product details are not included, that information must be supplied separately.
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.