Prepare customer follow-up from pending activity
Give yourself a focused follow-up list with Stripe customer context for transaction activity that clearly identifies a customer.
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
Potential follow-up can be missed when pending activity has to be manually connected to customer records.
- Retrieve customer context for clearly identified records.
- Turn available activity into a concise follow-up report.
- Keep ambiguous customer relationships out of the confirmed list.
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 customer details only for explicit Stripe customer IDs, and list follow-up candidates.
- 4Choose a recurring schedule trigger and select where run reports should go.
- 5Test with one real activity record containing a known customer ID.
Questions about this workflow
Can it contact the customer?
No. This workflow prepares a report; it does not send a message.
What happens when there is no customer ID?
The report should mark the customer context as unavailable and avoid guessing.
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.