Automation

Stripe Checkout Session Action

Updated 2026-09-02·3 min read

Overview

The Stripe Checkout Session action turns any automation into a paid flow. Call the action with a price, line item, or product ID and Taskade returns a hosted Stripe URL your user can pay on.

TL;DR: Point a form, button, or webhook at this action to accept payments in a Taskade Genesis app. Call it with a price, line item, or product ID, and Taskade returns a hosted Stripe URL your user can pay on. Pairs with the Stripe integration triggers to close the loop.

Here is the hosted page your buyer lands on once the action returns the checkout URL:

┌──────────────────────────────────────────────┐
│  🔒  Secure Checkout                         │
├──────────────────────────────────────────────┤
│  Pro Coaching Session               $150.00  │
│                                              │
│  Email  [ [email protected]                 ]    │
│  Card   [ 4242 4242 4242 4242   12/28 123 ]  │
│                                              │
│          [        Pay $150.00        ]  ✅   │
└──────────────────────────────────────────────┘

When to use it

  • Sell a course, ebook, or template directly from a published Taskade Genesis app
  • Charge clients from a client portal
  • Take a deposit inside a booking form
  • Run a recurring subscription checkout from an internal tool

Inputs

Field Type Notes
Line items Array of { price, quantity } Accepts Stripe price IDs or ad-hoc prices
Mode payment / subscription / setup Defaults to payment
Success URL URL Where to send the buyer after payment
Cancel URL URL Where to send the buyer if they abandon
Customer email Email (optional) Pre-fills the checkout form

Outputs

Field Type Notes
checkout_url URL The hosted Stripe page to redirect to
session_id String Stable ID for reconciliation
expires_at Timestamp Sessions expire after 24 hours

Example: paid download

  1. Trigger: new form submission on your Taskade Genesis app.
  2. Action: Stripe Checkout Session with a single line item.
  3. Action: Redirect the user to checkout_url.
  4. Trigger (follow-up): New Payment from the Stripe piece.
  5. Action: email the asset via Gmail.

Reconciling payments

Pair this action with the existing New Payment and Payment Failed triggers from the Stripe integration. Use session_id to match the triggered event back to the checkout that created it.

Was this helpful?