Keep subscriber contact changes in Stripe
When a subscriber shares updated contact details, send them through a Notis webhook and refresh the corresponding Stripe customer.
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
Updated contact details in a subscriber system may not reach Stripe, making later customer communication harder.
- Reduce manual edits to customer contact records.
- Apply only the details supplied in the request.
- Make customer communication details easier to keep current.
Setup
Build it in a few focused steps.
- 1Connect AimTell and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name and prompt.
- 3In one instruction, ask Notis to find the Stripe customer using the supplied identifier and update only the provided contact details.
- 4Pick the Notis webhook trigger and choose where run reports should go.
- 5Test with one real subscriber update and check the customer in Stripe.
Questions about this workflow
How does Notis know which customer to update?
The webhook request should include a Stripe customer ID or another identifier Notis can use to locate the customer. If it is missing or ambiguous, ask Notis to report that instead of guessing.
Will unspecified customer fields be cleared?
Stripe's update action changes only the provided details; unspecified fields remain unchanged.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link AimTell to Stripe. A trigger fires from one place; an action lands in another.
AimTell 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.
AimTell 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.