Review Stripe customers for campaign operations
Keep customer follow-up organized with a recurring review of Stripe customer records.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
List customers
Retrieves a list of stripe customers, with options to filter by email, creation date, or test clock, and support for pagination.
Why this helps
Customer records and campaign activity can drift apart when there is no regular review.
- Retrieves Stripe customers for a scheduled review.
- Summarizes available records without inventing link attribution.
- Makes customer review a repeatable part of campaign operations.
Setup
Build it in a few focused steps.
- 1Connect Bitly and Stripe once in Notis.
- 2Create an automation in the portal or describe the customer review outcome.
- 3In one instruction, define any customer filters and campaign fields that are available for review.
- 4Choose a recurring Notis schedule and select where run reports should go.
- 5Test a run and check that the customer summary uses only available information.
Questions about this workflow
Can this identify every customer who clicked a Bitly link?
No. Stripe customer records do not inherently establish Bitly click activity. A reliable reference must be available in your data.
Can the customer list be narrowed?
The Stripe action supports filters such as email and creation date. Specify the useful criteria in your instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bitly to Stripe. A trigger fires from one place; an action lands in another.
Bitly 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.
Bitly 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.