Carry customer detail updates into Stripe
When a verified request arrives, update only the customer details it asks you to change.
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 detail changes can get lost when a support conversation and billing records are handled in different places.
- Apply requested updates to an existing Stripe customer.
- Avoid re-entering details from a support handoff.
- Leave unspecified customer fields unchanged.
Setup
Build it in a few focused steps.
- 1Connect Ayrshare and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Describe in one instruction how to update the specified Stripe customer using only the approved details in the request.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real example containing a valid customer id and a clearly scoped update.
Questions about this workflow
What does the webhook request need?
It needs the existing Stripe customer id and the details that should be updated. Only provided details are changed by this action.
Will this update the customer based on a social handle alone?
A social handle is not a Stripe customer id. Provide a reliable way to identify the Stripe customer before requesting an update.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Ayrshare to Stripe. A trigger fires from one place; an action lands in another.
Ayrshare 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.
Ayrshare 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.