Skip to content
Notis

Prepare customer support context in one request

Give support a Stripe customer snapshot and checked location context when a request arrives.

Trigger

Webhook received

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

Action

Retrieve customer

Retrieves detailed information for an existing stripe customer using their unique customer id.

Why this helps

Support replies slow down when customer details and address checks require separate searches.

  • Pair an existing customer record with submitted location context.
  • Reduce the number of manual lookups before a support reply.
  • Keep the incoming request and customer reference together.

Setup

Build it in a few focused steps.

  • 1Connect Big data cloud and Stripe once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and give it a name and prompt.
  • 3Tell Notis to retrieve the Stripe customer identified in the webhook and validate the submitted address for a concise support handoff.
  • 4Pick the webhook trigger and choose where run reports should go.
  • 5Test with one real support request and customer ID.

Questions about this workflow

What does the webhook need?

Include the Stripe customer ID and the address or location details from the support request.

Does this update the customer?

No. It retrieves the customer and enriches location context for the handoff.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Big data cloud to Stripe. A trigger fires from one place; an action lands in another.

Big data cloud triggers

Stripe actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Confirm payment intent

Confirms a stripe paymentintent to finalize a payment; a `return url` is necessary if the payment method requires customer redirection.

ActionInstant

Create Customer

Creates a new customer in stripe, required for creating charges or subscriptions; an email is highly recommended for customer communications.

ActionInstant

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.

ActionInstant

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.

ActionInstant

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`.

ActionInstant

Create product

Creates a new product in stripe, encoding the request as `application/x-www-form-urlencoded` by flattening nested structures.

ActionInstant

Create Refund

Creates a full or partial refund in stripe, targeting either a specific charge id or a payment intent id.

ActionInstant

Connect any two apps with Notis in the middle.

Big data cloud 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.