Skip to content
Notis

Save corrected delivery information to the customer record

When a customer sends a corrected address, validate it and update the Stripe record with the accepted details.

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

Corrections can remain in messages while the Stripe customer record continues to hold an outdated address.

  • Turn a validated correction into an updated customer record.
  • Reduce the chance of using outdated delivery details again.
  • Keep correction handling in one workflow.

Setup

Build it in a few focused steps.

  • 1Connect Addresszen and Stripe once in the Notis portal.
  • 2Create an automation and give it a clear name.
  • 3Tell Notis to validate the corrected delivery address and update the identified Stripe customer with the accepted details.
  • 4Choose a webhook trigger and select where run reports should go.
  • 5Test with one real corrected address.

Questions about this workflow

Will the previous customer information be overwritten?

Only the details you direct Notis to provide to Stripe will be updated.

What should happen when validation fails?

Instruct Notis to report the issue and leave the existing Stripe customer details unchanged.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Addresszen to Stripe. A trigger fires from one place; an action lands in another.

Addresszen triggers

Stripe actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Confirm payment intent

Confirms a stripe paymentintent to finalize a payment; a `return url` is necessary if the payment method requires customer redirection.

ActionInstant

Create Customer

Creates a new customer in stripe, required for creating charges or subscriptions; an email is highly recommended for customer communications.

ActionInstant

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.

ActionInstant

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.

ActionInstant

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`.

ActionInstant

Create product

Creates a new product in stripe, encoding the request as `application/x-www-form-urlencoded` by flattening nested structures.

ActionInstant

Create Refund

Creates a full or partial refund in stripe, targeting either a specific charge id or a payment intent id.

ActionInstant

Connect any two apps with Notis in the middle.

Addresszen 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.