Cin7
Connect AI agents and workflows to Cin7: products, stock by location, sales, purchases, customers, suppliers and transfers, with webhooks.
Book a demoCin7 for AI agents and workflows.
engini lets your AI agents and workflows work in Cin7, the inventory and order management system for product brands, wholesalers and multichannel sellers: read products and stock by location, enter sales and purchases, move stock between locations, keep customers and suppliers current, and start a workflow the moment Cin7 reports a sale or stock change. Connect from Claude, ChatGPT or Cursor over MCP, from your code, or build in Workflow Studio.
Cursor, your code
audit log
in engini
What your agent can do in Cin7. Every tool is one you allow or leave out.
The Cin7 tools in engini, grouped by what they change. Read tools are safe to hand out widely. Write and delete tools go only to the agents that need them.
Read
Read products and stock by location.
Read orders, invoices and their status.
Read who you sell to and buy from.
Write
Enter an order and move it through fulfillment.
Raise an order to a supplier.
Move or correct stock.
Keep records current.
Any endpoint
Call any Cin7 API endpoint, with the key added for you.
Triggers
A sale was entered or changed.
Stock moved for a product you watch.
A trigger starts a workflow, and a workflow can include an AI agent step. In Code, a trigger delivers the event to your own endpoint.
Connect your AI agent to Cin7. Four ways in, one set of permissions.
Claude, ChatGPT, Cursor
Create an MCP server in engini with your Cin7 connection and only the tools you choose. Add its address to your client and sign in through engini. There is no key to copy.
MCP client setup →Python and TypeScript
Hand your agent a toolset of Cin7 tools. The SDK gives OpenAI and Anthropic models the tools in the format they expect and runs the ones they pick.
SDK guide →For coding agents
The engini CLI connects Cin7 and runs its tools from a terminal, with machine-readable output, so an AI coding agent can drive it without getting stuck.
CLI guide →Any language
Every Cin7 tool is an endpoint. Call it with exact inputs from a scheduled job or a sync, with no model in the loop.
API reference →.cursor/mcp.json. Claude Code: claude mcp add.// .cursor/mcp.json: Cursor, connected to Cin7 through engini
{
"mcpServers": {
"engini-cin7": {
"url": "<your engini MCP server address>"
}
}
}
Create the MCP server in engini with your Cin7 connection and the tools this agent may use, then paste its address. The client signs in through engini on first use. Claude, VS Code and other clients take the same address: see the MCP client setup guide.
Each request runs through the Cin7 tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.
What teams build on Cin7. Agents and workflows, across systems.
B2B orders from the CRM
Orders from HubSpot or Salesforce become Cin7 sales with the right price tier.
Cin7 and the books
Invoices and purchases reach Xero, QuickBooks or NetSuite with their coding.
Stock alerts that act
When a product falls below its minimum, a purchase is drafted and the buyer hears in Slack.
Sales and stock on request
An agent answers what sold, where stock sits and what to reorder. Its toolset holds read tools only.
Every integration runs both ways, so any of these flows can also run in reverse. These are examples, not the limit: any flow between Cin7 and another system engini connects is available.
You decide what each agent may do in Cin7. engini enforces it on every call.
Only the tools you allow
A toolset lists the Cin7 tools an agent may call and the connection each one uses. Give one agent read tools only and another the write it needs. engini refuses any call outside the toolset.
Scoped when you set them up
An MCP server exposes only the connections and tools chosen when it is created, and engini shows who uses each server.
Whose permissions apply
Connect a person's own Cin7 account and engini acts as that person, with their Cin7 permissions. Use a shared integration account and it acts as that account. Every run is recorded under the user who started it.
Kept out of prompts
Your agent never needs your credentials: engini stores them and adds them when it runs each call, so keys stay out of prompts and tool inputs.
Every call on record
Every call lands in History and the audit log, which you can export or stream to your SIEM.
Test before production
Workspaces keep teams apart, and development, staging and production environments keep a test agent away from live data.
Connect Cin7 in three steps. Then decide what each agent may do.
Sign in to Cin7
In Cin7, create an API application and copy the account ID and key, then add a Cin7 connection with them.
Choose the tools
Add the connection to an MCP server or a toolset with only the tools each agent needs.
Build or ask
Use the connection as a step in a workflow, or ask your agent to work in Cin7 from Claude, ChatGPT, Cursor or your own code.
Cin7 and engini. Straight answers.
Can an AI agent write to Cin7, or only read?
Both. engini has tools to create and update sales, purchases, stock transfers and adjustments, and keep products, customers and suppliers current. Whether a given agent may use them is up to you: give it a toolset or an MCP server with read tools only, and it cannot call the rest.
Does the agent act as me in Cin7?
It acts as the Cin7 account behind the connection. Every run is recorded under the person who started it.
Can a change in Cin7 start work?
Yes. Cin7 notifies engini when sales are created or changed and when stock levels move. A trigger starts a workflow, and that workflow can include an AI agent step.
What if the tool I need is not listed?
Use Send API Request to call any Cin7 API endpoint through the same connection, and give it only to the agents that need it.