Update Stripe customer details from Bitly-linked requests
Keep customer records current when a customer submits a change through your campaign or account flow.
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 updates can be missed when requests arrive in one workflow and billing records live elsewhere.
- Applies submitted changes to an existing Stripe customer.
- Updates only details stated in the instruction or request.
- Leaves a run report for checking the outcome.
Setup
Build it in a few focused steps.
- 1Connect Bitly and Stripe once in Notis.
- 2Create an automation from the portal or explain the outcome in plain language.
- 3In one instruction, define which customer changes to apply and how to identify the existing Stripe customer.
- 4Choose the Notis webhook trigger and where run reports should go.
- 5Test with one real, authorized customer update request.
Questions about this workflow
Will this create a customer if no match exists?
No. This action updates an existing customer. The request needs a reliable Stripe customer identifier.
Can it change unspecified customer fields?
The action updates provided details; unspecified fields remain unchanged.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bitly to Stripe. A trigger fires from one place; an action lands in another.
Bitly 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.
Bitly 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.