Review Stripe subscriptions for campaign follow-up
Start the day with a short list of subscription records that need attention in your campaign workflow.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
List subscriptions
Retrieves a list of stripe subscriptions, optionally filtered by various criteria such as customer, price, status, collection method, and date ranges, with support for pagination.
Why this helps
Subscription follow-up gets missed when campaign plans and billing status require separate manual checks.
- Retrieves Stripe subscriptions on a recurring schedule.
- Summarizes relevant records for follow-up without assuming Bitly has subscription events.
- Puts the review in the report channel you choose.
Setup
Build it in a few focused steps.
- 1Connect Bitly and Stripe once in Notis.
- 2Create an automation in the portal or describe the review you want.
- 3In one instruction, define which subscription statuses or campaign context the summary should cover.
- 4Choose a recurring Notis schedule and where run reports should go.
- 5Test with one real run and confirm the summary reflects Stripe data you can access.
Questions about this workflow
Can Stripe data identify which Bitly campaign generated a customer?
Only if your Stripe data or your instruction includes a reliable campaign reference. Do not assume that relationship is available.
How often can it run?
Choose the recurring schedule that suits your follow-up process when setting up the Notis cron trigger.
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.