Update a Stripe customer after an unsubscribe
When an unsubscribe has a billing record consequence, tell Notis what Stripe customer change to make.
Trigger
Unsubscribe Trigger
Triggered when a subscriber unsubscribes from Mailchimp
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 can retain outdated details after someone changes their relationship with your business.
- Bring customer record follow-up into the unsubscribe workflow
- Apply only the record change your instruction specifies
- Reduce manual cross checking
Setup
Build it in a few focused steps.
- 1Connect Mailchimp and Stripe once in the Notis portal.
- 2Create an automation in the portal or tell Notis from any channel what outcome you want.
- 3In one instruction, specify how to find the related Stripe customer and what provided customer details to update.
- 4Choose the Mailchimp unsubscribe trigger, select a report channel, and test with one real example.
Questions about this workflow
What customer fields can be updated?
The Stripe action updates provided details. Your instruction should name the change and provide the necessary values.
Does this cancel a subscription too?
No. This workflow uses the Stripe customer update action. Subscription cancellation requires a separate action and instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Mailchimp to Stripe. A trigger fires from one place; an action lands in another.
Mailchimp 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.
Campaign Trigger
Triggered when a campaign is sent or experiences an event in Mailchimp
Create Customer
Creates a new customer in stripe, required for creating charges or subscriptions; an email is highly recommended for customer communications.
Profile Update Trigger
Triggered when a subscriber's profile is updated in Mailchimp
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.
Subscribe Trigger
Triggered when a subscriber subscribes to Mailchimp
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.
Unsubscribe Trigger
Triggered when a subscriber unsubscribes from Mailchimp
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.
Mailchimp 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.