Apply billing contact changes from Ascora in Stripe
Keep billing contacts current by carrying a customer change request through to the Stripe record.
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
Billing contacts change, but updating the customer record often becomes a separate task that gets missed.
- Reduce manual updates to billing contacts.
- Apply only the changes present in the request.
- Get a run report when the customer reference is missing or unclear.
Setup
Build it in a few focused steps.
- 1Connect Ascora and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to update the identified Stripe customer with billing contact details provided in the Ascora request and report unmatched customers.
- 4Choose the webhook trigger and where run reports should go.
- 5Test with one real contact change and confirm the Stripe customer update.
Questions about this workflow
Will the workflow overwrite other customer information?
The Stripe update action applies only provided details. Unspecified fields remain unchanged.
What if there is no Stripe customer id?
Provide a reliable matching detail in the request. Ask Notis to report uncertain or unmatched records for manual review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Ascora to Stripe. A trigger fires from one place; an action lands in another.
Ascora 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.
Ascora 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.