Keep Stripe customer details aligned with approved Bika corrections
Route vetted customer detail changes to the billing record with less copying.
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
Approved address or contact changes are easy to record in one system and forget in another.
- Reduces repeat customer detail edits
- Uses the supplied Stripe customer id to target the update
Setup
Build it in a few focused steps.
- 1Connect Bika and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3In one instruction, ask Notis to update the Stripe customer identified by the provided customer id with only the approved fields in the request.
- 4Choose notis_webhook as the trigger and configure Bika to send approved corrections to the Notis webhook URL.
- 5Choose a report channel, then test with one real correction example.
Questions about this workflow
Can the workflow find a customer from a name alone?
The update action requires a customer id. Include the id in the Bika request or use another workflow to locate and verify the customer first.
Will it overwrite fields that were not supplied?
The action updates only the provided details, leaving unspecified fields unchanged.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bika.ai to Stripe. A trigger fires from one place; an action lands in another.
Bika.ai 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.
Bika.ai 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.