Confirm payment intents after Celigo signals readiness
Move payment intents to confirmation when your Celigo flow signals the payment is ready.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Confirm payment intent
Confirms a stripe paymentintent to finalize a payment; a `return url` is necessary if the payment method requires customer redirection.
Why this helps
Payment confirmation can be missed when readiness is recorded in one workflow and action happens elsewhere.
- Reduce manual follow-up on payment-ready requests
- Keep confirmation tied to the originating flow
- Support redirect-required payment methods with a return URL
Setup
Build it in a few focused steps.
- 1Connect Celigo and Stripe once in the Notis portal.
- 2Create the automation and tell Notis when a payment intent should be confirmed.
- 3Choose a webhook trigger and report destination, then test with one real payment example.
- 4Have Celigo send an HTTP request with the existing payment intent and a return URL when redirection is required.
Questions about this workflow
Does every payment method need a return URL?
A return URL is necessary if the payment method requires customer redirection.
Does this create a new payment intent?
No. This workflow confirms an existing payment intent.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Celigo to Stripe. A trigger fires from one place; an action lands in another.
Celigo 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.
Celigo 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.