--- title: "SureCart Integration" description: "Read your SureCart store from your flows. Agents list products, prices, orders, and subscriptions, look up order and customer details, monitor subscription status for retention workflows, and register new customers." url: https://flowrunner.ai/integrations/surecart date_modified: 2026-08-01T02:40:32-07:00 --- # SureCart [E-commerce](https://flowrunner.ai/integrations/category/e-commerce) Read your SureCart store from your flows. Agents list products, prices, orders, and subscriptions, look up order and customer details, monitor subscription status for retention workflows, and register new customers. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 10 actions · API key · available [SureCart website](https://surecart.com/) · [Platform Documentation](https://developer.surecart.com/) · Capability data verified 2026-07-27 1. A scheduled sweep runs against the store every hour 2. List Subscriptions filtered by status surfaces subscriptions that just moved to past\_due 3. Get Customer pulls the subscriber's name, email, and portal URL 4. Get Subscription retrieves the plan, current period, and price detail 5. The agent scores the account: subscription age, order history from List Orders, and amount at risk 6. For high-value accounts, the retention owner reviews the situation and picks the outreach before anything is sent 7. The chosen follow-up goes out with the customer's portal URL, where they can fix their own payment method ## What This Integration Enables SureCart is built for stores that run on WordPress and run lean, often a single operator wearing every hat. The connector leans into that reality: it gives FlowRunner agents a clean read of everything the store knows, products, prices, orders, customers, and subscriptions, so the reporting, syncing, and monitoring work stops competing with actual selling. The one write, Create Customer, registers buyers ahead of orders and subscriptions. - Sync products and prices into catalogs, spreadsheets, or downstream stores - Watch subscription status for retention plays: active, trialing, past\_due, canceled - Route new paid orders to fulfillment tools and team channels as they happen - Register customers from external forms or checkouts before orders exist - Look up order, customer, or subscription detail to enrich any other automation The retention sweep is where [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) orchestration matters most: agents find the at-risk accounts at machine speed, and a person decides how to treat the ones worth a personal touch. There is also a compounding effect worth naming. Each of these reads is small on its own; composed, they become an operations layer the store never had. The order sweep feeds the revenue log, the revenue log feeds the weekly digest, the subscription sweep feeds the retention queue, and the same agent tends all of it on a schedule that never slips. For a store run by one or two people, that is the difference between selling and administering, and it is precisely the work worth handing to an agent, because none of it requires taste, only reliability. ### Without FlowRunner **Churn discovered at month end**: A past\_due subscription sits unnoticed until the revenue report shows the hole **The store is a silo**: Orders, customers, and subscriptions live in WordPress while the CRM, email list, and spreadsheets drift out of date **Every question means an admin login**: Checking an order status or a subscriber's plan means opening the dashboard and clicking around ### With FlowRunner **Payment failures caught the same hour**: Agents sweep subscription status on a schedule and route at-risk accounts while the card can still be fixed **Store data flows outward**: Products, prices, orders, and subscribers sync into the CRM, the email platform, and the reporting sheet automatically **Answers pulled in-flow**: Agents look up orders, customers, and subscriptions mid-workflow and hand the answer to whoever asked ## Use Case Scenarios ### New paid orders, announced and logged An hourly sweep calls List Orders with the expand parameter pulling line\_items and customer inline. New paid orders post to the team channel in [Slack](https://flowrunner.ai/integrations/slack) with product, amount, and customer name, and each one appends to a revenue log in [Google Sheets](https://flowrunner.ai/integrations/google-sheets). Fulfillment-relevant orders route onward. Nobody refreshes the dashboard, and the first question of every morning, did we sell anything overnight, answers itself. ### Subscribers become segments When List Customers surfaces new buyers, the agent calls Get Customer for full detail and mirrors each one into [Klaviyo](https://flowrunner.ai/integrations/klaviyo) with their purchase context. Subscription holders get tagged by plan using List Subscriptions, so lifecycle campaigns can tell a trialing subscriber from a three-year loyalist. The store stays the source of truth; the marketing platform stays current without manual exports. ### The past\_due save List Subscriptions filtered to past\_due runs every hour. For each hit, the agent pulls the subscriber with Get Customer, checks their order history with List Orders, and calculates what the account is worth annually. Low-value accounts get the standard recovery email with their portal URL. High-value accounts pause at a human step: the owner sees the full picture and decides between a personal email, a call, or a grace period. The agent does the finding; the person does the saving. ## Human-in-Loop Highlight Create Customer is the connector's only write, and it deserves more respect than it usually gets. In SureCart the customer record anchors everything: orders, subscriptions, and the customer portal URL where a subscriber manages their own billing. Register the same person twice, once from a form and once from a checkout with a different email, and their history splits across two records with two portals, and every retention workflow downstream reads half a customer. So when a FlowRunner agent processes an inbound registration and List Customers returns a near-match, same name, different email, it does not guess. It shows both records to a person and asks: same customer or new one? A duplicate takes seconds to prevent and months of confused reporting to unwind. 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 10 actions ### Products and Prices 3 - **List Products** Lists store products with full-text search, sorting, and pagination. Use expand to inline prices. The catalog read behind syncs and audits. - **Get Product** Retrieves a single product with status, metrics, and configuration. Expand pulls prices or variants inline. - **List Prices** Lists prices across the store, optionally scoped to one product. Prices carry the amount, currency, and billing interval, which makes this the read that distinguishes one-time from recurring revenue. ### Orders 2 - **List Orders** Lists orders with full-text search and filters for order, fulfillment, and shipment status, scoped to a customer if needed. The sweep behind order notifications and revenue logging. - **Get Order** Retrieves a single order in full, with expand for line\_items, customer, checkout, or charge. The context step before fulfillment or support handoffs. ### Customers 3 - **List Customers** Lists customers with full-text search and pagination, including name, email, and portal URL. The matching step before any customer write. - **Get Customer** Retrieves a single customer in full, including phone and portal URL, with expand for addresses and payment method. - **Create Customer** Creates a customer record with a required email. The write this page's human gate exists for: a duplicate here splits a subscriber's history in two. ### Subscriptions 2 - **List Subscriptions** Lists subscriptions with status filtering, scoped to a customer if needed. The read behind every retention sweep. - **Get Subscription** Retrieves a single subscription with status, current period, and associated customer and price. The detail step before a save attempt. ## Frequently Asked Questions ### What can FlowRunner do with SureCart? FlowRunner agents can run List Products, Get Product, and List Prices in SureCart, plus 7 more actions. ### Does connecting SureCart to FlowRunner require OAuth? No. SureCart connects to FlowRunner with an API key, no OAuth flow required. ### Can SureCart trigger a FlowRunner workflow automatically? SureCart doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at SureCart?** This integration exposes SureCart 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/surecart. Site index: https://flowrunner.ai/llms.txt