Check customer coverage between Billsby and Stripe
See which supplied Billsby customer records may not have a Stripe counterpart, without manually scanning customer lists.
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
Customer records spread across billing systems make it difficult to notice missing counterparts before a billing task needs them.
- Spot customer coverage gaps
- Avoid repeat list exports during routine checks
- Send uncertain matches for human review
Setup
Build it in a few focused steps.
- 1Connect Billsby and Stripe once in Notis.
- 2Create an automation and describe how to compare Stripe customers with the Billsby roster you will provide.
- 3Pick a recurring schedule and choose where run reports go.
- 4Test with one real roster sample and verify the reported matches.
Questions about this workflow
Can it add missing customers automatically?
This workflow only lists customers and reports gaps. A separate, explicit process would be needed to create Stripe customers.
How should uncertain matches be handled?
Ask Notis to report uncertain matches for review rather than treating them as missing records.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Billsby to Stripe. A trigger fires from one place; an action lands in another.
Billsby 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.
Billsby 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.