Cin7 Core (DEAR)
ERPConnect AI agents to Cin7 Core (formerly DEAR Inventory). Agents check real-time stock availability across warehouses, read and search the product catalog, create sales orders from storefront events, audit purchase orders, and manage customers and suppliers.
What This Integration Enables
Cin7 Core (formerly DEAR Inventory) answers the question every product business runs on: can we actually sell this, right now, from this warehouse? Its availability model is honest in a way simple stock counts are not, splitting On Hand from Allocated from Available from On Order. This connector makes that honesty operational. FlowRunner agents check availability before promises are made, create sales for existing customers with SKU-level lines, keep catalogs, customers, and suppliers synced outward, and audit inbound purchase orders against what planning assumed. The stance this page takes: overselling is not an inventory problem, it is a sequencing problem. The check and the commitment happen in different systems at different times, and humans bridge the gap too slowly. Agents collapse the sequence to seconds: - Product Availability runs before Create Sale, always, so the order that enters DEAR was verifiable when it entered - Storefront buyers are matched to existing customers or created cleanly, keeping the customer file deduplicated - Sales flow onward to accounting with full line detail, closing the order-to-invoice loop - Scheduled availability sweeps catch downward trends and cross-reference List Purchases for what is already inbound - Catalog and supplier data feed spreadsheets and dashboards without export rituals The one decision agents do not make: what to do when stock falls short of demand. That trade-off belongs to FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) layer.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The order that checked the shelf before saying yes
A [Shopify](/integrations/shopify) order fires the flow. The agent runs Product Availability for each SKU at the default location and reads Available, not On Hand, because allocated stock is already spoken for. Covered orders proceed: customer matched via List Customers, sale written via Create Sale, order number posted to [Slack](/integrations/slack). Short orders stop and route to an operator with the availability breakdown. Customers stop receiving the apologetic "actually out of stock" email, because the promise was checked before it was made.
Sales that invoice themselves
Nightly, the agent pulls List Sales filtered to the day's completed orders, fetches full detail with Get Sale, and raises a matching invoice in [Xero](/integrations/xero) for each: lines, quantities, prices, customer reference. Finance reconciles against DEAR order numbers instead of chasing operations for what shipped. The gap where sales sat unbilled for a week, purely because invoicing was a manual batch job, closes to a day.
The reorder signal that arrives with context
Twice daily, the agent sweeps Product Availability across locations and logs the numbers to [Google Sheets](/integrations/google-sheets). SKUs trending toward their floor get cross-checked against List Purchases: if an inbound PO already covers the gap, the agent notes it and stays quiet; if not, it posts the SKU, the trend, the supplier from the product record, and the last purchase to the operations channel. The buyer makes the reorder call with the whole picture in one message, instead of assembling it from four tabs.
Human-in-Loop Highlight
The gated moment on this connector is Create Sale under shortage. When Product Availability shows demand exceeding Available stock, writing the sale anyway is a business decision wearing an API call's clothes: it allocates inventory you may not have, commits a delivery date you may miss, and if it triggers fulfillment, sends a warehouse hunting for goods that are not on the shelf. Whether to split the shipment, backorder, pull from another location, or decline entirely depends on customer importance, margin, and what List Purchases says is arriving Thursday, context an agent can assemble but should not adjudicate. So the agent stops, presents the availability breakdown and the options, and the operations owner chooses. Fully covered orders write autonomously at any hour. Orders that would promise what the warehouse cannot see are promises only a person gets to make.
Agent Capabilities
10 actionsProducts
2- List Products Retrieves a paginated list of products from the Cin7 Core (DEAR) catalog. Supports filtering by product Name and SKU, and pagination via Page and Limit. Returns the total record count plus an array of products with their SKU, name, category, prices, and unit of measure. Use the Product ID or SKU from a result with Get Product or Product Availability.
- Get Product Retrieves the full details of a single product by its Cin7 Core (DEAR) product ID, including SKU, name, category, brand, price tiers, dimensions, supplier, and attribute set values. The product endpoint identifies the record via an ID query parameter rather than a path segment.
Stock
1- Product Availability Returns real-time stock availability for products across warehouse locations, including On Hand, Allocated, Available, and On Order quantities. Filter by SKU, product Name, or Location to check inventory levels. Use this to verify stock before creating a sale or reordering.
Sales
3- List Sales Retrieves a paginated list of sales orders with summary fields such as order number, customer, status, order date, and totals. Supports filtering by Customer ID, order Status, and a Created/Updated date range. Use a sale's ID with Get Sale to fetch the full order.
- Get Sale Retrieves the complete details of a single sale order by its ID, including customer and contact, order/invoice/fulfilment lines, payments, shipping, and status. The sale endpoint identifies the record via an ID query parameter rather than a path segment.
- Create Sale Creates a new sale order in Cin7 Core (DEAR) for an existing customer. Requires the customer name (must already exist), location, and one or more order lines identified by SKU with quantity and price. Optional fields include price tier, currency, sales representative, and a customer reference. Returns the created sale with its generated ID and order number.
Purchases
1- List Purchases Retrieves a paginated list of purchase orders with summary fields such as order number, supplier, status, order date, and totals. Supports filtering by Supplier ID, order Status, and an Updated Since date. Use this to audit or reconcile inbound orders.
Customers
2- List Customers Retrieves a paginated list of customers with their name, contact details, currency, price tier, payment term, and account status. Supports filtering by Name and pagination via Page and Limit. Use a customer's ID or name with List Sales or Create Sale.
- Create Customer Creates a new customer record in Cin7 Core (DEAR). Requires a unique customer Name; optional fields include currency, price tier, payment term, tax rule, primary contact, email, phone, and account status. Returns the created customer with its generated ID.
Suppliers
1- List Suppliers Retrieves a paginated list of suppliers with their name, contact details, currency, payment term, tax rule, and account status. Supports filtering by Name and pagination via Page and Limit. Use a supplier's ID with List Purchases.
Frequently Asked Questions
What can FlowRunner do with Cin7 Core (DEAR)?
FlowRunner agents can run List Products, Get Product, and Product Availability in Cin7 Core (DEAR), plus 7 more actions.
Does connecting Cin7 Core (DEAR) to FlowRunner require OAuth?
No. Cin7 Core (DEAR) connects to FlowRunner with an API key, no OAuth flow required.
Can Cin7 Core (DEAR) trigger a FlowRunner workflow automatically?
Cin7 Core (DEAR) doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Cin7 Core (DEAR)
$100 in credits. No card required. Connect in minutes.