Keep Stripe customer details current from Billsby
Route customer detail updates into Stripe when a Billsby request arrives, and surface cases that need identification or review.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Update Customer
Updates an existing stripe customer, identified by customer id, with only the provided details; unspecified fields remain unchanged.
Why this helps
Customer details can diverge when teams update one billing system and forget to update the other.
- Cut repeat profile edits
- Make the requested customer change easier to track
- Flag requests that do not identify a Stripe customer
Setup
Build it in a few focused steps.
- 1Connect Billsby and Stripe once in Notis.
- 2Create an automation and describe which supplied customer details Notis should update in Stripe.
- 3Pick the webhook trigger and choose where run reports go.
- 4Test with one real update request and verify the customer record.
Questions about this workflow
Will the automation overwrite every Stripe field?
Describe only the details that should change. The Stripe action updates provided details while unspecified fields remain unchanged.
What if the request cannot identify a Stripe customer?
Include an instruction to report the missing identifier and leave the Stripe record unchanged.
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.