Find Stripe customer context for a transaction
Bring a transaction-related request into Notis and retrieve the relevant Stripe customer details when the identity is clear.
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
Customer context can be hard to find when transaction monitoring and Stripe customer records are in separate tools.
- Retrieve Stripe customer details from a clearly identified request.
- Keep transaction context with the customer lookup report.
- Avoid guessing when customer identity is unclear.
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 use the request's explicit Stripe customer ID to retrieve the customer and report if it is absent.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one real request containing a known customer ID.
Questions about this workflow
Can transaction data alone identify a Stripe customer?
Not necessarily. The request should include a Stripe customer ID or another clear identifier available to the workflow.
Does this change customer data?
No. It retrieves customer details for the report.
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.