Turn Bitly campaign checkout requests into Stripe payment intents
Move from campaign response to payment setup without re-entering details by hand.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
A customer can be ready to buy after clicking a campaign link, while payment setup still depends on manual follow-up.
- Starts payment setup from a request your process sends to a Notis webhook.
- Keeps payment intent creation and run reporting in one workflow.
- Reduces manual copying between campaign and payment tools.
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 in plain language.
- 3In one instruction, describe how to start a Stripe payment intent from a Bitly campaign checkout request.
- 4Choose the Notis webhook trigger and select where run reports should go.
- 5Test with one real example, including the amount and currency your request supplies.
Questions about this workflow
Does Bitly itself start this workflow when someone clicks a link?
No Bitly trigger events are available here. A request sent to the Notis webhook starts it; your process needs to send that request.
What payment details should the request include?
Specify the amount and currency, along with any other details needed for the payment intent. Test with a real example before relying on it.
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.