Keep donor customer records in sync for follow-up
Catch donor records that may need a Stripe customer entry before the next billing task.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
List customers
Retrieves a list of stripe customers, with options to filter by email, creation date, or test clock, and support for pagination.
Why this helps
A donor may be present in ChMeetings but missing from Stripe when it is time to arrange payment or follow up.
- Surface potential gaps between donor and customer records.
- Use Stripe customer lookup to support a scheduled check.
- Create records only when available details support a clear match decision.
Setup
Build it in a few focused steps.
- 1Connect ChMeetings and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3Ask Notis to retrieve donor details and Stripe customers, identify clear matches using available contact information, create a customer only for an unmatched donor, and report ambiguous cases.
- 4Choose a recurring schedule and select where run reports should go.
- 5Test with one real sample and review any newly created customer.
Questions about this workflow
How does Notis decide whether a customer already exists?
It can compare available identifying details, such as email, using Stripe customer search or listing. Ask it to report ambiguous matches rather than create duplicates.
Can this recover missing donor details?
No. It can only use information available from ChMeetings and Stripe. The report should identify fields that are missing.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Chmeetings to Stripe. A trigger fires from one place; an action lands in another.
Chmeetings triggers
Stripe actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Cancel subscription
Cancels a customer's active stripe subscription at the end of the current billing period, with options to invoice immediately for metered usage and prorate charges for unused time.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Confirm payment intent
Confirms a stripe paymentintent to finalize a payment; a `return url` is necessary if the payment method requires customer redirection.
Create Customer
Creates a new customer in stripe, required for creating charges or subscriptions; an email is highly recommended for customer communications.
Create an invoice
Creates a new draft stripe invoice for a customer; use to revise an existing invoice, bill for a specific subscription (which must belong to the customer), or apply detailed customizations.
Create payment intent
Creates a stripe paymentintent to initiate and process a customer's payment; using `application fee amount` for a connected account requires the `stripe-account` header.
Create a price
Creates a new stripe price for a product, defining its charges (one-time or recurring) and billing scheme; requires either an existing `product` id or `product data`.
Create product
Creates a new product in stripe, encoding the request as `application/x-www-form-urlencoded` by flattening nested structures.
Create Refund
Creates a full or partial refund in stripe, targeting either a specific charge id or a payment intent id.
Connect any two apps with Notis in the middle.
Chmeetings and Stripe, 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 Stripe.