--- title: "Big Cartel Integration" description: "Read a Big Cartel storefront from your flows. Agents pull the product catalog, categories, orders, and account settings to drive fulfillment, bookkeeping, and catalog syncs in downstream systems." url: https://flowrunner.ai/integrations/big-cartel date_modified: 2026-08-01T02:40:32-07:00 --- # Big Cartel [E-commerce](https://flowrunner.ai/integrations/category/e-commerce) Read a Big Cartel storefront from your flows. Agents pull the product catalog, categories, orders, and account settings to drive fulfillment, bookkeeping, and catalog syncs in downstream systems. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 6 actions · API key · available [Big Cartel website](https://bigcartel.com/) · [Platform Documentation](https://developers.bigcartel.com/api/v1) · Capability data verified 2026-07-27 1. The morning fulfillment run starts before the studio opens 2. Get Account confirms the connected store, its currency, and its time zone before any totals are interpreted 3. List Orders pulls the unshipped queue with customer details, totals, and shipping status 4. Get Order expands each order into line items, transactions, and adjustments 5. Payment status, address completeness, and unusual totals are screened on every order 6. The owner reviews the exceptions, the order whose payment has not settled, the address that fails validation, before anything is handed to fulfillment 7. Clean orders go to the 3PL, the exception decisions are logged, and the day's rows land in the bookkeeping sheet ## What This Integration Enables Big Cartel is the storefront of choice for makers and independent brands precisely because it stays small: a clean catalog, a simple order stream, no operations department implied. The gap is everything that happens after the sale, and that gap is usually filled by the founder's evenings. FlowRunner closes it by reading the store and running the back office around it: agents pull products, categories, orders, and account settings into fulfillment, bookkeeping, and channel syncs, so the store stays simple while the operation behind it grows up. - Hand unshipped orders to a 3PL or shipping workflow daily, screened first - Log every sale into a ledger with line items, transactions, and adjustments - Mirror the product catalog into spreadsheets, databases, and other storefronts - Report on the catalog by storefront category without manual grouping - Verify store settings like currency and time zone before downstream systems assume them ### Without FlowRunner **Orders processed one tab at a time**: Fulfillment means reading the dashboard and retyping each order into the shipping tool **Books catch up at month end**: Sales get recorded in a batch, weeks after the money moved, when memory has already faded **Catalog truth lives in one head**: Whether an item is listed, priced right, or on sale across channels is checked by remembering ### With FlowRunner **The unshipped queue clears itself**: Orders are screened and handed to fulfillment daily, and only the exceptions cost a human minute **Every sale hits the ledger same-day**: Order rows arrive with totals, payment status, and line items while the sale is still fresh **The catalog syncs outward**: Products and categories mirror into spreadsheets and other channels on a schedule ## Use Case Scenarios ### Fulfillment handed off, not retyped Each morning the agent calls List Orders filtered to unshipped, expands each with Get Order, and creates matching fulfillment orders in [ShipBob](https://flowrunner.ai/integrations/shipbob) with the shipping address and line items carried over field by field. Orders that fail screening, unsettled payment, incomplete address, hold for review instead. The maker spends the morning making things, and the queue is empty by the time the 3PL picks. ### A ledger and a bell for every sale A scheduled sweep spots new orders, and Get Order pulls each one's totals, payment status, and items. A row lands in [Google Sheets](https://flowrunner.ai/integrations/google-sheets) with everything the bookkeeper needs at close, and [Slack](https://flowrunner.ai/integrations/slack) posts the sale to the team channel with the product names. The month-end ritual shrinks from reconstructing the month to confirming it. ### One catalog, many places Nightly, List Products walks the catalog and List Categories maps its groupings. The agent mirrors both into the master sheet and diffs against the [Shopify](https://flowrunner.ai/integrations/shopify) listing where the brand also sells, flagging items that exist in one channel but not the other, or carry different prices. Get Product supplies full details, images and options included, wherever a listing needs to be rebuilt. The two-storefront strategy stops depending on someone remembering to update both. ## Human-in-Loop Highlight The reads on this page feed a write that leaves the building: the fulfillment handoff. Once an order screened from List Orders becomes a shipment at the 3PL, the package is picked, labeled, and gone, and no API call brings it back. The costly mistake is not reading the order wrong, it is shipping against an order whose Get Order detail shows a payment still unsettled or an address that two systems disagree on. So the agent screens every unshipped order and routes the exceptions to the owner with the evidence attached: "Order 1184, payment status pending, ship address missing postal code. Hold, fix, or release?" The [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) decision costs a minute. The unreviewed shipment costs the product, the postage, and the apology. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 6 actions ### Store 1 - **Get Account** Retrieves the connected store's name, subdomain, contact email, currency and locale settings, time zone, and feature flags. The grounding step that keeps downstream systems from assuming the wrong currency or clock. ### Catalog 3 - **List Products** Lists the catalog as a paginated JSON:API collection with name, permalink, status, description, default price, sale flag, and image URL. The backbone of catalog syncs and channel diffs. - **Get Product** Retrieves one product in full by ID, including relationships to options, categories, and images. The detail source when a listing is rebuilt elsewhere. - **List Categories** Lists all product categories with name, permalink, and display position. The grouping layer for catalog reporting and storefront organization. ### Orders 2 - **List Orders** Lists orders with customer details, item and money totals, shipping address, and shipping and payment status, with pagination, free-text search, and shipped or unshipped filtering. The fulfillment queue and the reconciliation feed. - **Get Order** Retrieves one order in full by ID with relationships to line items, transactions, and adjustments. The screening evidence behind this page's human gate and the detail behind every ledger row. ## Frequently Asked Questions ### What can FlowRunner do with Big Cartel? FlowRunner agents can run Get Account, List Products, and Get Product in Big Cartel, plus 3 more actions. ### Does connecting Big Cartel to FlowRunner require OAuth? No. Big Cartel connects to FlowRunner with an API key, no OAuth flow required. ### Can Big Cartel trigger a FlowRunner workflow automatically? Big Cartel doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Big Cartel?** This integration exposes Big Cartel 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/big-cartel. Site index: https://flowrunner.ai/llms.txt