Keep business customer records current
Start with a customer update request, review the supplied site, and apply only the details the request confirms.
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
Business details drift across records, and checking a site before updating Stripe adds another manual step.
- Review supplied public business information before making a requested update.
- Update only specified customer details while leaving other fields unchanged.
Setup
Build it in a few focused steps.
- 1Connect AgentQL and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3In one instruction, tell Notis to review the supplied site and update the specified customer using only details confirmed in the request.
- 4Pick a webhook trigger and choose where run reports should go.
- 5Test with one real update request and review the changes.
Questions about this workflow
Will Notis infer missing Stripe fields from the website?
Tell Notis to use only details that the request confirms. Do not rely on inferred or unavailable information.
Can it update an existing customer?
Yes. The workflow uses the supplied Stripe customer ID to update that customer.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Agentql to Stripe. A trigger fires from one place; an action lands in another.
Agentql 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.
Agentql 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.