See which CRM customers may need a Stripe profile
Review customer coverage periodically and get a list of records that may need a Stripe customer profile.
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 team can discover a missing Stripe customer only when it is time to bill, adding avoidable backtracking.
- Compare the CRM customer set with Stripe customers using available identifiers.
- Surface likely missing profiles for review.
- Avoid creating records automatically when a match is uncertain.
Setup
Build it in a few focused steps.
- 1Connect CentralstationCRM and Stripe once in the Notis portal.
- 2Create an automation and name it for the customer coverage audit.
- 3Tell Notis to compare the intended CRM customer records with Stripe customers and report likely missing or ambiguous matches.
- 4Choose a recurring schedule and select where run reports should go.
- 5Test with a small real customer set and review the matching logic.
Questions about this workflow
Will this create the missing customers?
No. This workflow reports likely missing records for review. It does not create Stripe customers.
How are matches determined?
Notis can use identifiers available in both sets, such as email. Ambiguous matches should be reported for review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Centralstationcrm to Stripe. A trigger fires from one place; an action lands in another.
Centralstationcrm 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.
Centralstationcrm 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.