Keep Stripe company customer details current
Send an existing Stripe customer ID and an updated company tax identifier. Notis validates the identifier and updates the customer from the company details available through 44API.
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
Company records change, and updating billing details across tools is easy to forget.
- Validate the new tax identifier before changing customer details.
- Apply only the details supplied by the 44API response.
- Receive a report if the customer ID or validation result needs review.
Setup
Build it in a few focused steps.
- 1Connect 44API and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Describe that Notis should validate the submitted tax identifier and update the specified Stripe customer using the returned company details.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real customer ID and company identifier, then review the report.
Questions about this workflow
Does this create a new Stripe customer?
No. The request should include the ID of an existing Stripe customer for Notis to update.
Will unspecified customer details be replaced?
The Stripe update action applies provided details, while unspecified fields remain unchanged.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link 44API to Stripe. A trigger fires from one place; an action lands in another.
44API 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.
44API 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.