Handle Stripe refunds from Bitly-linked requests
Give refund requests a clear path from intake to Stripe without losing the payment reference.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create Refund
Creates a full or partial refund in stripe, targeting either a specific charge id or a payment intent id.
Why this helps
Refund requests can linger when the team has to find the payment, confirm the request, and create the refund manually.
- Creates a Stripe refund from an incoming authorized request.
- Lets the instruction specify whether the refund is full or partial.
- Makes each workflow run easier to review through its report.
Setup
Build it in a few focused steps.
- 1Connect Bitly and Stripe once in Notis.
- 2Create an automation in the portal or tell Notis the outcome you want.
- 3In one instruction, define which incoming requests qualify and how to identify the charge or payment intent.
- 4Choose the Notis webhook trigger and the channel for run reports.
- 5Test using one real, authorized refund example and review the result.
Questions about this workflow
Does a Bitly click automatically authorize a refund?
No. The webhook request must represent a refund you have authorized and provide a Stripe charge or payment intent reference.
Can the refund be partial?
Yes. The request and instruction should specify the intended refund amount when a partial refund is needed.
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.