Keep recruiting client billing contacts current in Stripe
A scheduled check can catch changed client contact details in Ashby and update the matching Stripe customer so billing communications reach the right person.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Update Customer
Updates an existing stripe customer, identified by customer id, with only the provided details; unspecified fields remain unchanged.
Why this helps
Billing notices can go to an outdated contact when client changes are recorded in Ashby but not Stripe.
- Reduce manual customer record maintenance
- Use Ashby as the reference for confirmed contact changes
- Get a report when a matching Stripe customer is unclear
Setup
Build it in a few focused steps.
- 1Connect Ashby and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to compare client billing contacts in Ashby with Stripe customers and update only records with a clear match and confirmed new details.
- 4Choose a recurring schedule and where run reports should go.
- 5Test with one real client whose billing contact has changed.
Questions about this workflow
Will this update unrelated Stripe customer fields?
The instruction can limit updates to confirmed contact details. Stripe keeps unspecified fields unchanged.
What happens when a client matches multiple Stripe customers?
Have Notis report the ambiguity for review rather than choosing a record without a clear match.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Ashby to Stripe. A trigger fires from one place; an action lands in another.
Ashby 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.
Ashby 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.