Lightspeed eCom
E-commerceRead products, variants, orders, customers, and categories straight from your Lightspeed eCom store. Agents sync catalog and inventory data, export recent orders for reporting, and look up customer records to enrich fulfillment and support workflows.
What This Integration Enables
Lightspeed eCom holds the operational truth of the store: catalog, variants with real inventory numbers, orders with payment and shipment status, customers with their consent state. This connector is a deliberate read-only window onto all of it. FlowRunner agents cannot break your store; what they do is stop the store's data from being trapped in the admin panel, sweeping it outward into reporting, fulfillment, marketing, and ERP workflows that used to run on manual exports. - Sync product, variant, and inventory data into spreadsheets, databases, or the ERP - Export new and updated orders on a date window for reporting and downstream processing - Look up orders and customers by ID to enrich fulfillment, support, and accounting flows - Pull the category tree for navigation, mapping, and migration work - Build marketing lists from customer records, with newsletter subscription state attached Read-only does not mean risk-free: what leaves the store still deserves governance, and FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) orchestration governs it. Read-only is a feature here, not a limitation to apologize for. Fulfillment, accounting, and marketing workflows need the store's truth far more often than they need to change it, and a connector that cannot write is a connector whose blast radius is fully understood before the first flow runs. Teams that want agents in their commerce stack but hesitate at giving them write access to a revenue system get exactly the right first step: every report, alert, and sync this page describes, with the store itself untouched by construction.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The rolling order export nobody runs
Every morning, List Orders with an Updated After window pulls the last day's activity. Each order lands in [Google Sheets](/integrations/google-sheets) with number, status, payment and shipment state, and totals, and orders needing attention, paid but unshipped past the threshold, post to [Slack](/integrations/slack). The reporting spreadsheet the team already lives in stays current without anyone touching the admin panel.
Variant-level stock alerts before the sellout
A scheduled sweep calls List Variants, reading stock level, SKU, and price per variant. Anything under its reorder threshold posts to the merchandising channel with the product resolved via Get Product, so the team restocks the size 41 that is actually running out, not the product that looks fine in aggregate. The most common retail stockout, the popular variant hidden inside a healthy product line, stops being a surprise.
The marketing sync that respects the checkbox
Weekly, List Customers pages through the customer base. The agent filters on newsletter subscription state and syncs only opted-in customers to [Klaviyo](/integrations/klaviyo) with name, email, and purchase context from their order history. Customers who unsubscribed in the store drop from the audience on the same schedule. The list grows from the store automatically, and it never grows past what consent covers.
Human-in-Loop Highlight
The costly operation in a read-only connector is the read that leaves the building. List Customers returns names, emails, phone numbers, addresses, and each customer's newsletter subscription state, and the expensive mistake is an export that ignores that last field: push the full customer table into a campaign audience and you have emailed people who explicitly declined, which costs trust immediately and can cost real money under privacy rules. So FlowRunner agents treat customer exports as gated flows. The agent builds the audience, reports the counts, how many opted in, how many excluded, which destination, and a person confirms the scope before a single record syncs outward. Order and product reads flow freely; people data moves only after a human has seen exactly who is going where, and the approval itself becomes part of the audit trail.
Agent Capabilities
8 actionsCatalog
4- List Products Retrieves products with pagination up to 250 per page, brand and date-window filters, including titles, description, visibility, and links to variants, images, and categories. The catalog sweep behind syncs and audits.
- Get Product Retrieves one product in full: titles, content, visibility, pricing hints, and linked variants, images, categories, brand, and supplier. The detail read behind alerts and enrichment.
- List Categories Retrieves the catalog's category tree with titles, visibility, sort order, and parent links. The structural read for navigation, mapping, and migrations.
- List Variants Retrieves variants carrying the store's real inventory: stock level, price, SKU, article code, and weight, filterable by product. The read behind variant-level stock monitoring.
Orders
2- List Orders Retrieves orders with pagination, customer and order-number filters, and creation and update date windows, including status, payment and shipment state, and addresses. The export engine.
- Get Order Retrieves one order in full with totals, contact details, addresses, and links to invoices, shipments, and ordered products. The context step for fulfillment and support handoffs.
Customers
2- List Customers Retrieves customers with pagination, an email filter, and date windows, including name, company, addresses, and newsletter subscription state. The read this page's human gate governs.
- Get Customer Retrieves one customer in full: name, email, company, phone, billing and shipping addresses, subscription and confirmation state. The lookup behind support and accounting enrichment.
Frequently Asked Questions
What can FlowRunner do with Lightspeed eCom?
FlowRunner agents can run List Products, Get Product, and List Orders in Lightspeed eCom, plus 5 more actions.
Does connecting Lightspeed eCom to FlowRunner require OAuth?
No. Lightspeed eCom connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.
Can Lightspeed eCom trigger a FlowRunner workflow automatically?
Lightspeed eCom doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Lightspeed eCom
$100 in credits. No card required. Connect in minutes.