FlowRunner
By team All teams DevelopersSecurity & ITFinance & OperationsRevOpsSupport & CXData & Platform By industry All industries HealthcareFinancial ServicesLogistics By use case All use cases Invoice validationApproval routingClient intakePrior authorizationData reconciliationComplaint triage
All Integrations AI & LLMsDatabases & WarehousesIdentity & SecurityCRM & SalesCommunication & MessagingFinance & Accounting
Pricing
ConceptsCompareGuidesSolution libraryBlog
Theme

Unleashed Software

ERP

Read products, stock on hand, customers, suppliers, warehouses, and sales and purchase orders from the Unleashed cloud inventory platform, and create new sales orders.

12 actions available
A new order arrives from a store or CRM
Agent reads the customer, product, and quantity
Agent calls Get Stock On Hand by Product to confirm availability
Agent confirms the warehouse has enough stock to fulfill
Agent runs Create Sales Order to record the order in Unleashed
The fulfillment team is updated with the order and stock position
An order that would push stock below a safety threshold is routed for a decision

What This Integration Enables

Agents read the operational inventory picture and record demand against it. On products they list and read (Get Products, Get Product). On stock they check availability warehouse by warehouse (Get Stock On Hand, Get Stock On Hand by Product). On the commercial side they read customers and suppliers (Get Customers, Get Customer, Get Suppliers), read and monitor orders (Get Sales Orders, Get Sales Order, Get Purchase Orders), read warehouses (Get Warehouses), and create new demand with Create Sales Order. The connector is read-mostly by design, which makes it a dependable availability-and-status layer for a fulfillment workflow: the agent confirms what is in stock and where, records the sale, and leaves inventory adjustments and purchasing to the systems and people that own them.

Without FlowRunner

Stock checked in spreadsheets Someone pulls inventory exports together to find where stock-out risk is
Orders keyed by hand Store and CRM orders are re-entered into Unleashed manually
Availability guessed at Orders are accepted without confirming warehouse-level stock first

With FlowRunner

Stock read on demand Get Stock On Hand by Product answers availability inside the flow
Orders recorded in-flow Create Sales Order writes the order the moment it arrives upstream
Availability confirmed first Fulfillment proceeds only when stock is verified, and low stock is flagged

Use Case Scenarios

Availability-Gated Fulfillment

A new order arrives. The agent calls Get Stock On Hand by Product to confirm the warehouse can cover it, and only when stock is sufficient does it proceed to fulfill, for example by creating the order in [ShipBob](/integrations/shipbob). Orders that would overcommit inventory are held and flagged instead of shipped and unwound later. Availability becomes a gate, not an afterthought.

Order Recording After Fulfillment

An order is fulfilled downstream. The agent calls Create Sales Order to record it against the customer in Unleashed, so the inventory system reflects the sale without a person entering it. The commercial record and the physical movement stay aligned because recording the order is a step in the same flow that fulfilled it.

Customer Sync to Accounting

Before invoicing a new account, the agent calls Get Customer to retrieve the record from Unleashed and syncs it into [QuickBooks Online](/integrations/quickbooks-online) with a Create Customer call. The account exists in accounting before the first invoice is raised, so billing does not stall on a missing customer record.

Human-in-Loop Highlight

Reading stock and recording orders is safe to run unattended. Committing an order that would drive a product below its safety stock is a judgment call about which customer gets the last units, and that is where an agent should stop and ask. Human-in-the-loop is the pattern where the agent pauses on the tradeoff, assembles the context, and resumes on a human's decision. When Get Stock On Hand by Product shows that fulfilling an order would push a product below a configurable safety threshold, the agent does not run Create Sales Order on its own. It presents the product, the current stock, the order quantity, and the resulting position, then routes to the ops lead in [Slack](/integrations/slack): "This order for 40 units of SKU-2213 would leave 6 in stock, below the safety level of 25. Record the order, partially fulfill, or hold?" The lead decides. On approval, the agent records the order and logs the decision. Orders that leave healthy stock proceed without a pause.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via Slack
Human decides
Agent resumes with decision

Agent Capabilities

12 actions

Products

2
  • Get Products Retrieves products from Unleashed.
  • Get Product Retrieves a product from Unleashed.

Stock

2
  • Get Stock On Hand Retrieves warehouse-level stock on hand across products.
  • Get Stock On Hand by Product Retrieves stock on hand for a specific product across warehouses. Used to gate fulfillment on availability.

Customers and Suppliers

3
  • Get Customers Retrieves customers from Unleashed.
  • Get Customer Retrieves a single customer from Unleashed.
  • Get Suppliers Retrieves suppliers from Unleashed.

Orders

4
  • Get Sales Orders Retrieves sales orders from Unleashed.
  • Get Sales Order Retrieves a single sales order from Unleashed.
  • Create Sales Order Creates a new sales order in Unleashed.
  • Get Purchase Orders Retrieves purchase orders from Unleashed.

Warehouses

1
  • Get Warehouses Retrieves warehouses from Unleashed.

Other ERP integrations

IntegrationAcumatica18 actionsIntegrationMicrosoft Dynamics 3657 actionsIntegrationERPNext10 actions

Start building with Unleashed Software

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us