Find customer context gaps in transaction reviews
See which transaction follow-ups have usable Stripe customer context and which need an identifier before you can proceed.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Retrieve customer
Retrieves detailed information for an existing stripe customer using their unique customer id.
Why this helps
Unclear customer ownership turns a quick transaction review into a manual investigation.
- Separate identified customer records from cases needing more information.
- Retrieve Stripe details for explicit customer IDs.
- Make missing context visible in the scheduled report.
Setup
Build it in a few focused steps.
- 1Connect Blocknative and Stripe once in Notis.
- 2Create an automation from any channel or in Automations, New Automation.
- 3In one instruction, ask Notis to review available pending activity, retrieve details for explicit Stripe customer IDs, and report records that lack customer context.
- 4Choose a recurring schedule trigger and select where run reports should go.
- 5Test with one real review containing identified and unidentified records.
Questions about this workflow
Will this create or update customer records?
No. It retrieves details for identified customers and reports gaps.
Can it determine customer identity from an address alone?
Only if the connected information and instruction provide a reliable way to do so. Otherwise, it should report the missing identifier.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Blocknative to Stripe. A trigger fires from one place; an action lands in another.
Blocknative 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.
Blocknative 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.