SamCart
E-commercePull products, orders, customers, subscriptions, and charges from your SamCart checkout platform. Agents reconcile revenue over date ranges, monitor subscription status for churn signals, and sync buyers into CRMs and reporting systems.
What This Integration Enables
SamCart is where the sale happens, and for most sellers it is also where the data stops. Orders, subscriptions, and charges accumulate behind the checkout while the CRM, the email platform, and the finance sheet all run on partial copies typed in later. This connector turns the SamCart Admin API into the feed those systems should have had from the start. FlowRunner agents pull products, orders, customers, subscriptions, and charges on schedules or on demand, reconcile them against each other, and hand the results to the systems where the follow-up work actually happens. The API is read-only, and that shapes the design honestly: SamCart is the source of truth about money collected, and agents are its couriers and analysts, not its editors. - Sync orders and customers into CRMs, spreadsheets, and warehouses with purchase context attached - Monitor subscriptions by status to track recurring revenue, churn, and past-due drift - Reconcile charges over date ranges for finance reporting that matches the processor - Chase failed payments with reviewed dunning outreach instead of month-end surprises - Drive win-back campaigns from canceled subscriptions, with a person curating the list
Without FlowRunner
With FlowRunner
Use Case Scenarios
The buyer who exists everywhere at once
An order lands. The next sync picks it up via List Orders, calls Get Customer for the full profile, and List Order Subscriptions to see whether the purchase created recurring billing. The buyer is upserted into [HubSpot](/integrations/hubspot) with product and amount on the record, added to the right sequence in [Brevo](/integrations/brevo), and appended to the revenue sheet in [Google Sheets](/integrations/google-sheets). When the customer emails support two weeks later, the person answering can see what they bought without asking.
Churn watched as a status, not a feeling
Weekly, List Subscriptions runs three times: active for the recurring revenue base, past due for the rescue list, canceled for the win-back pool. The agent computes movement against last week's snapshot and posts the deltas to [Slack](/integrations/slack). Past-due subscribers feed the dunning workflow. Canceled ones accumulate into a win-back list that the marketing owner curates before any offer goes out, because a canceled status says nothing about why someone left.
The reconciliation that finance stops dreading
At month close, List Charges pulls every payment attempt in the period with amount, currency, and status, and List Orders pulls the orders they belong to. The agent matches charges to orders, flags orphans in both directions, and writes the reconciled set to the finance workbook. Discrepancies arrive as a short exception list with order IDs attached, so the bookkeeper investigates five rows instead of eyeballing five hundred.
Human-in-Loop Highlight
The costly move in a SamCart workflow is not a delete, the API will not let an agent delete anything. It is the outreach the data seems to justify. List Charges hands you failed payment attempts; List Subscriptions hands you cancellations. Both look like invitations to automate email about money, and money email is the easiest way to burn a customer relationship at machine speed. The failed charge that already cleared on retry, the subscriber who canceled because a refund is in progress, the past-due customer mid-conversation with support: each one receives an automated payment demand as an insult. So FlowRunner workflows put the list, not just the send, in front of a person. The agent assembles each candidate with their charge history from List Charges and current status from Get Subscription, and the revenue owner strikes names before anything sends. Machine speed for the assembly, human judgment for the send list. That order is the whole design.
Agent Capabilities
10 actionsProducts
2- List Products Pages through the account's products with pricing, type, and status. The catalog read behind reporting joins and product pickers.
- Get Product Retrieves one product's full detail, including pricing options and configuration. Used when a workflow needs more than the list view carries.
Orders
3- List Orders Pages through orders with totals, currency, customer, and line items, filterable by creation date range and customer email. The backbone of daily revenue sync and CRM enrichment.
- Get Order Retrieves one order's full detail: line items, taxes, totals, purchaser, and any associated subscription. The context call before support follow-ups and dispute research.
- List Order Subscriptions Returns the subscriptions a specific order created, with status, interval, and billing details. The step that tells fulfillment whether a sale was one-time or the start of a relationship.
Customers
2- List Customers Pages through customers with contact details and lifetime purchase context, filterable by email. The sync source for CRM and marketing lists.
- Get Customer Retrieves one customer's full profile by ID. The enrichment call before any record lands in another system.
Subscriptions
2- List Subscriptions Pages through subscriptions filterable by status: active, canceled, past due, or completed. The single most decision-rich read in the connector, and the source for churn, rescue, and win-back lists.
- Get Subscription Retrieves one subscription's interval, amount, current status, customer, and Stripe plan reference. The freshness check that runs before anyone gets a dunning message.
Charges
1- List Charges Pages through individual payment attempts, successful and failed, with amount, currency, status, and their order and customer, filterable by date range. The reconciliation feed and the dunning trigger, in one action.
Frequently Asked Questions
What can FlowRunner do with SamCart?
FlowRunner agents can run List Products, Get Product, and List Orders in SamCart, plus 7 more actions.
Does connecting SamCart to FlowRunner require OAuth?
No. SamCart connects to FlowRunner with an API key, no OAuth flow required.
Can SamCart trigger a FlowRunner workflow automatically?
SamCart doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with SamCart
$100 in credits. No card required. Connect in minutes.