Keep Stripe customer details current from BotMape
Carry a corrected customer detail from an agent conversation into the right Stripe record with the customer ID in hand.
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 corrected email or customer detail can remain stuck in a conversation instead of reaching the billing record.
- Update the identified Stripe customer record from supplied details.
- Avoid searching Stripe manually when a customer correction arrives.
- Leave unspecified customer fields unchanged.
Setup
Build it in a few focused steps.
- 1Connect BotMape and Stripe once in the Notis portal.
- 2In Automations, choose New Automation and give it a name.
- 3Tell Notis to update only the Stripe customer identified by the ID in the webhook request, using the corrected details supplied there.
- 4Choose the webhook trigger and where run reports should go.
- 5Test with one real example and verify the intended customer record.
Questions about this workflow
What identifies the Stripe record?
The request should include the unique Stripe customer ID. The action updates an existing customer identified by that ID.
Will omitted fields be cleared?
No. The action updates only provided details; unspecified fields remain unchanged.
Can the workflow use a corrected email from a conversation?
Yes, if the request includes the customer ID and the corrected email detail.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link BotMape to Stripe. A trigger fires from one place; an action lands in another.
BotMape 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.
BotMape 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.