Collect payment for an Apiframe-generated asset
Let a checkout request kick off payment while you keep your attention on creating and delivering the asset.
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 paid asset request can get lost when you have to switch between generation work and payment setup.
- Creates a Stripe payment intent from an incoming checkout request.
- Keeps the payment request connected to the asset details included in the webhook.
- Reduces manual handoffs between asset creation and payment processing.
Setup
Build it in a few focused steps.
- 1Connect Apiframe and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for asset checkout.
- 3Tell Notis to create a Stripe payment intent for each incoming request that includes the asset and payment details needed by Stripe.
- 4Choose the webhook trigger and select a channel for run reports.
- 5Test with one real checkout request sent to the webhook.
Questions about this workflow
Does Apiframe start this workflow automatically?
No. Apiframe has no listed trigger events for this package. An HTTP request to the Notis webhook starts the workflow.
What information should the request include?
Include the payment details Stripe needs and enough asset context to recognize what the customer is purchasing. Notis cannot supply details that are absent from the request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Apiframe to Stripe. A trigger fires from one place; an action lands in another.
Apiframe 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.
Apiframe 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.