Keep Stripe customer details current from Basecamp requests
Turn a clear change request into a targeted Stripe customer update, while leaving unspecified customer details untouched.
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 detail updates get delayed when a change request has to be copied manually into a separate billing system.
- Apply requested changes without retyping them
- Preserve existing details that were not part of the request
- Keep a report of completed updates and unresolved requests
Setup
Build it in a few focused steps.
- 1Connect Basecamp and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for customer detail updates.
- 3Tell Notis to update only the specified details for the Stripe customer identified in the incoming Basecamp request, and report missing or ambiguous identifiers.
- 4Choose notis_webhook as the trigger and select where run reports should go.
- 5Test with one real customer detail change request.
Questions about this workflow
Does this replace every Stripe customer detail?
No. Stripe updates only the provided details, and unspecified fields remain unchanged.
What if the customer ID is unclear?
Ask Notis to report the ambiguity for follow-up instead of updating a customer it cannot confidently identify.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Basecamp to Stripe. A trigger fires from one place; an action lands in another.
Basecamp 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.
Basecamp 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.