Turn a passage request into a targeted customer update
When an incoming request includes a customer and the intended detail change, look up its scripture context and update 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
A small customer update can stall when the request, reference material, and billing record are spread across different tools.
- Handle a specific customer change from one incoming request.
- Keep the passage lookup attached to the update context.
- Avoid overwriting unspecified customer details.
Setup
Build it in a few focused steps.
- 1Connect Api bible and Stripe once in the Notis portal.
- 2Create an automation for scripture-related customer updates.
- 3In one instruction, tell Notis to search Api bible for the incoming reference and apply only the explicitly requested changes to the identified Stripe customer.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one real example that identifies the customer and states the intended change.
Questions about this workflow
What can this update change?
Stripe's Update Customer action applies only provided details and leaves unspecified fields unchanged. State the intended changes clearly.
Will Api bible decide customer details to change?
No. The request must specify the changes. Api bible provides passage lookup context, not customer data.
What if the webhook does not identify a customer?
The workflow needs a reliable customer identifier or search clue before it can target the existing Stripe record.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Api bible to Stripe. A trigger fires from one place; an action lands in another.
Api bible 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.
Api bible 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.