Keep Stripe customer names current from newsletter details
Use updated subscriber details to keep customer records recognizable when you review billing activity.
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 records with incomplete or outdated names are harder to recognize during support and finance work.
- Keeps customer records easier to identify.
- Avoids repeatedly editing customer names by hand.
- Limits changes to the name when the request includes a clear match.
Setup
Build it in a few focused steps.
- 1Connect Beehiiv and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for customer profile refreshes.
- 3Tell Notis to use the Stripe customer id in each qualifying webhook request and update the customer name from the provided subscriber details.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real subscriber update and verify the Stripe customer.
Questions about this workflow
What if a webhook request does not include a Stripe customer id?
Have the instruction report the request for review rather than guessing which customer to update.
Can this update customer name and email together?
Yes, if the request provides both and your instruction explicitly asks for both. This workflow focuses on the name.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Beehiiv to Stripe. A trigger fires from one place; an action lands in another.
Beehiiv 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.
Beehiiv 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.