--- title: "Lemon Squeezy Integration" description: "Connect AI agents to Lemon Squeezy, the merchant of record for digital products. Agents read stores, products, orders, subscriptions, and customers, create customer records, cancel subscriptions, and generate hosted checkout URLs for buyers." url: https://flowrunner.ai/integrations/lemon-squeezy date_modified: 2026-08-04T10:04:16-07:00 --- # Lemon Squeezy [Payments](https://flowrunner.ai/integrations/category/finance-accounting) Connect AI agents to Lemon Squeezy, the merchant of record for digital products. Agents read stores, products, orders, subscriptions, and customers, create customer records, cancel subscriptions, and generate hosted checkout URLs for buyers. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 12 actions · API key · available [Lemon Squeezy website](https://lemonsqueezy.com/) · [Platform Documentation](https://docs.lemonsqueezy.com/api) · Capability data verified 2026-08-12 1. A quote request lands from the pricing page form with the buyer's email and requested plan 2. List Customers filters on the email so a returning buyer is recognized instead of duplicated 3. Create Customer records the new buyer with name, email, and country 4. The founder approves the custom price before a discounted checkout exists anywhere 5. Create Checkout builds the hosted checkout for the product variant with the approved price override and the buyer's email prefilled 6. The pay link goes to the buyer by email with its expiration window noted 7. A scheduled List Orders pass confirms the purchase and matches it back to the request 8. Get Order pulls the totals, tax, and receipt URL for the ledger entry and the CRM record ## What This Integration Enables Lemon Squeezy's pitch is that a small software team should not need a finance department to sell globally: as merchant of record it absorbs tax, compliance, and payment processing. What it does not absorb is the operations around the selling, the ledger entries, the CRM records, the custom deals, the churn watch. That is the layer FlowRunner agents run. Agents read stores, products, orders, subscriptions, and customers through the API, create customer records, generate hosted checkout URLs with prefilled buyer details, and cancel subscriptions when a person says so. - Deal desk: generate expiring, prefilled checkout URLs for specific variants, with optional price overrides - Revenue visibility: sync orders, totals, tax, and receipt URLs into sheets and CRM records on a schedule - Customer directory: match buyers by email before creating records, keeping the store's uniqueness rule intact - Retention: watch subscription status, renewal dates, and card details that predict failed payments The two operations that change what a customer pays or whether they keep access, the price override and the cancellation, run through [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) gates. Everything else runs on schedule without anyone watching. ### Without FlowRunner **Revenue lives in a browser tab**: Sales totals, MRR movement, and new orders are things you go look at, not things that reach you **Pay links made by hand**: Every custom deal means someone builds a checkout in the dashboard and pastes the URL into an email **Churn discovered at renewal**: Past-due subscriptions sit unnoticed until the customer is already gone ### With FlowRunner **The ledger syncs itself**: Agents walk orders and customers on a schedule and keep the spreadsheet, CRM, and dashboards current **Checkouts on demand**: Agents generate prefilled, expiring checkout URLs the moment a deal needs one, at a price a person approved **Subscription health watched daily**: Past-due and cancelled states surface with customer context the day they happen ## Use Case Scenarios ### Custom deals without dashboard archaeology A prospect asks for team pricing on an annual license. The agent checks List Customers for the email, creates the record if needed, and drafts a Create Checkout for the right variant with the negotiated price override, the buyer's details prefilled, and a seven-day expiration. The founder approves the number, the checkout URL goes out through [Gmail](https://flowrunner.ai/integrations/gmail-service), and a scheduled List Orders pass picks up the completed purchase and writes the order number and receipt URL back onto the deal record. The whole exchange happens in one thread, and no one built a checkout by hand. ### The sales ledger that closes itself Every night the agent runs List Orders across stores from List Stores, appending new orders to a running ledger in [Google Sheets](https://flowrunner.ai/integrations/google-sheets) with totals, tax, currency, and status. New buyers from List Customers land in [Airtable](https://flowrunner.ai/integrations/airtable) as directory records with aggregate revenue and order counts attached. Refund statuses picked up by Get Order flag the corresponding ledger rows instead of leaving the sheet quietly wrong. Monthly reporting becomes reading a sheet that was never stale. ### Retention with a person deciding who gets grace A daily pass over List Subscriptions filters for past-due status. For each, Get Subscription pulls the renewal date, card brand, and last four digits, and the agent posts the case to the billing channel in [Slack](https://flowrunner.ai/integrations/slack): customer, product, how long past due, lifetime revenue from the customer record. A person decides: reach out, extend grace, or end it. Only on that decision does Cancel Subscription run, and because Lemon Squeezy keeps the subscription active until the period ends, the customer keeps access exactly as long as they paid for. The agent never fires a cancellation on its own clock. ## Human-in-Loop Highlight Cancel Subscription ends a recurring revenue relationship, and it does not come back with an apology email. The subscription stops renewing, access lapses at the period's end date, and winning that customer a second time costs more than keeping them ever did. So in FlowRunner retention workflows, the agent's job stops at the case file: status, renewal date, payment history, lifetime value, all assembled from List Subscriptions and Get Subscription. A person names the outcome. The same discipline covers Create Checkout's price override, because a discounted checkout URL is a price commitment the moment it reaches a buyer's inbox. Agents prepare both operations perfectly and execute neither without a signature. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via email Human decides Agent resumes with decision ## Agent Capabilities 12 actions ### Stores 2 - **List Stores** Lists every store on the account with name, currency, domain, plan, and aggregate revenue and sales counters. The starting point for cross-store reporting. - **Get Store** Retrieves one store's details and aggregate revenue and sales statistics. ### Products 2 - **List Products** Lists products with name, description, price, status, and hosted buy-now URL, filterable by store. - **Get Product** Retrieves one product's pricing, status, and buy-now URL. ### Orders 2 - **List Orders** Lists orders with customer, totals, tax, currency, order number, receipt URL, and status. The feed behind ledgers and CRM sync. - **Get Order** Retrieves one order including refund status and the first order item, for matching purchases back to deals. ### Subscriptions 3 - **List Subscriptions** Lists subscriptions filterable by store or status, with billing state, renewal and end dates, card details, and management URLs. The retention watchlist. - **Get Subscription** Retrieves one subscription's full billing picture: status, variant, trial period, card brand and last four digits, and customer-portal URLs. - **Cancel Subscription** Cancels a subscription so it stops renewing at the end of the current billing period. The action this page's human gate exists for. ### Customers 2 - **List Customers** Lists customers filterable by store or email, with location, aggregate revenue, and order counts. The uniqueness check before any create. - **Create Customer** Creates a customer record with name and email, plus optional location. Emails must be unique per store, so match first. ### Checkouts 1 - **Create Checkout** Creates a custom hosted checkout for a store and product variant and returns the URL. Prefill the buyer's email, name, and billing address, attach metadata, override the price, and control which fields appear. The URL expires after a configurable period, which makes it a clean instrument for approved, time-boxed offers. ## Frequently Asked Questions ### What can FlowRunner do with Lemon Squeezy? FlowRunner agents can run List Stores, Get Store, and List Products in Lemon Squeezy, plus 9 more actions. ### Does connecting Lemon Squeezy to FlowRunner require OAuth? No. Lemon Squeezy connects to FlowRunner with an API key, no OAuth flow required. ### Can Lemon Squeezy trigger a FlowRunner workflow automatically? Lemon Squeezy doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Lemon Squeezy?** This integration exposes Lemon Squeezy to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/lemon-squeezy. Site index: https://flowrunner.ai/llms.txt