Update Stripe customer details for a release cohort
Keep customer records ready for a release-related billing change by reviewing the cohort and updates your team supplies.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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 details gathered for a release can be forgotten before the billing records are updated.
- Keep release-related customer updates moving
- Apply only supplied, approved changes
- Surface customer records that need human review
Setup
Build it in a few focused steps.
- 1Connect Beamer and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3In one instruction, ask Notis to use the supplied Beamer cohort and approved changes to update matching Stripe customers, reporting any ambiguous matches.
- 4Choose a recurring schedule and a channel for run reports.
- 5Test with one real cohort example and check the updated customer.
Questions about this workflow
Can Notis identify a cohort from Beamer automatically?
The schedule starts the workflow, and the prompt needs access to the relevant Beamer information or a supplied cohort. Beamer does not provide a listed trigger event.
What happens if a customer match is unclear?
Ask Notis to report the ambiguity for review rather than updating a possibly incorrect Stripe customer.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Beamer to Stripe. A trigger fires from one place; an action lands in another.
Beamer 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.
Beamer 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.