Turn completed Stripe checkouts into Chaser customers
A completed checkout can start your customer follow-up without another manual entry.
Trigger
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
Action
Create Customer
Tool to create a new customer record in chaser. use after obtaining basic auth credentials.
Why this helps
New customers can be easy to miss when their details stay in Stripe and your payment follow-up happens in Chaser.
- Reduce duplicate customer entry after a purchase.
- Keep new customer details available in Chaser.
- Start follow-up with less app switching.
Setup
Build it in a few focused steps.
- 1Connect Stripe and Chaser once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Tell Notis to create a Chaser customer from each completed Stripe Checkout Session, checking for an existing customer first.
- 4Pick the Stripe Checkout Session Completed trigger and choose where run reports should go.
- 5Test with one real completed checkout and review the created customer.
Questions about this workflow
What starts this automation?
A Stripe Checkout Session Completed event starts it.
What if the customer already exists in Chaser?
Tell Notis in the automation instruction to check for an existing customer before creating a record. Review the test run to confirm the match is reliable.
Which customer information can it use?
It can use details returned with the Stripe event. Ask Notis to omit details that are missing rather than assume them.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Stripe to Chaser. A trigger fires from one place; an action lands in another.
Stripe triggers
Chaser actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Invoice
Tool to create a new invoice record in the organization. use after ensuring the customer exists in chaser.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Credit Notes
Tool to retrieve a list of credit notes. use after authenticating this detail.
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
Get Customer by ID
Tool to retrieve details for a specific customer by their external (source system) id. use after obtaining the external id when you need specific customer information.
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
Get Customers
Tool to retrieve a list of all customers associated with the organization. use when you need to display or process complete customer contact and status information.
Invoice Payment Succeeded Trigger
Triggered when an invoice payment is successful in Stripe
Get Organization
Tool to retrieve information about the connected organizations. use when you need organization ids, currency, timezone, or legal details before other operations.
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Create Credit Note
Tool to create a new credit note record in the organization. use after confirming invoice adjustments.
Product Created Trigger
Triggered when a product is created in Stripe
Create Customer
Tool to create a new customer record in chaser. use after obtaining basic auth credentials.
Subscription Added Trigger
Triggered when a subscription is added in Stripe
Update Customer
Tool to update an existing customer's information using their unique externalid. use after confirming the customer's externalid. e.g., "update contactemailaddress for externalid cust abc123."
Connect any two apps with Notis in the middle.
Stripe and Chaser, 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 Chaser.