Start a payment from an order request
Move an order request toward payment with a prompt that considers the supplied order details and any useful external API context.
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
Payment setup can stall while order context is scattered across requests and external services.
- Start payment intent creation when an order request arrives.
- Use supplied order details and relevant API results in one instruction.
- Send run reports to a channel where payment setup is visible.
Setup
Build it in a few focused steps.
- 1Connect Apiverve and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, with a name and prompt.
- 3In one instruction, tell Notis how to use the request and relevant Apiverve results to create a payment intent.
- 4Choose the webhook trigger and a report destination.
- 5Test with one real order request and confirm the payment details are appropriate.
Questions about this workflow
Will this workflow complete every payment?
It creates a payment intent. Payment completion may require confirmation or customer redirection, depending on the payment method.
Can the workflow look up missing order details?
Only when you provide enough input for an available Apiverve API lookup. Otherwise, include those details in the webhook request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Apiverve to Stripe. A trigger fires from one place; an action lands in another.
Apiverve 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.
Apiverve 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.