< Back to all integrations

Rootstock

ERP & Finance

Connect AI agents and workflows to Rootstock ERP on Salesforce: items, sales orders, work orders, inventory, purchase orders and shipments.

Book a demo
[ Rootstock + engini ]

Rootstock for AI agents and workflows.

engini lets your AI agents and workflows work in Rootstock, the manufacturing, distribution and supply chain ERP built on Salesforce: read items, inventory by site and location, sales orders, work orders and purchase orders, enter sales orders and purchase orders, follow production and shipments, and start a workflow when records change. Rootstock runs next to Sales Cloud, and engini connects it to the systems outside Salesforce. Connect from Claude, ChatGPT or Cursor over MCP, from your code, or build in Workflow Studio.

MCPPython and TypeScript SDKCLIREST APIWorkflow Studio
Sign-inYour Salesforce org, with Rootstock installed
ReachItems, inventory, sales orders, work orders, purchase orders, receipts and shipments
TriggersNew and changed Rootstock records
[ 01 / What agents can do ]

What your agent can do in Rootstock. Every tool is one you allow or leave out.

The Rootstock tools in engini, grouped by what they change. In an ERP a write moves material and money, so write tools go only to the agents that need them.

Read

Get Items, Get Inventory

Read items and stock by site and location.

Read
Get Sales Orders, Get Shipments

Read orders and what shipped.

Read
Get Work Orders

Read production with its status.

Read
Get Purchase Orders, Get Receipts

Read purchasing.

Read

Write

Create Sales Order, Update Sales Order

Enter and change orders.

Write
Create Purchase Order

Raise an order to a supplier.

Write
Create Work Order

Open production for an item.

Write
Create or Update Item

Keep items current.

Write

Any endpoint

Send API Request

Call any Salesforce or Rootstock API, with the sign-in added for you.

Any call

Triggers

Check for New or Changed Records

Sales orders, work orders or shipments added or changed.

Scheduled

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.

[ 02 / Connect your agent ]

Connect your AI agent to Rootstock. Four ways in, one set of permissions.

MCP

Claude, ChatGPT, Cursor

Create an MCP server in engini with your Rootstock 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 →
SDK

Python and TypeScript

Hand your agent a toolset of Rootstock tools. The SDK gives OpenAI and Anthropic models the tools in the format they expect and runs the ones they pick.

SDK guide →
CLI

For coding agents

The engini CLI connects Rootstock and runs its tools from a terminal, with machine-readable output, so an AI coding agent can drive it without getting stuck.

CLI guide →
REST API

Any language

Every Rootstock tool is an endpoint. Call it with exact inputs from a scheduled job or a sync, with no model in the loop.

API reference →
MCP in four steps
In engini, connect Rootstock and create an MCP server with that connection and the tools this agent may use.
Claude: Settings, Connectors, Add custom connector, then paste the server address.
Cursor: add the address to .cursor/mcp.json. Claude Code: claude mcp add.
Sign in through engini when the client asks. The agent sees only the tools you chose.
Cursor, connected to Rootstock through engini
// .cursor/mcp.json: Cursor, connected to Rootstock through engini
{
"mcpServers": {
"engini-rootstock": {
"url": "<your engini MCP server address>"
}
}
}

Create the MCP server in engini with your Rootstock 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.

Try asking your agent
“Which sales orders for Acme ship this week?”
“How many of item 100-220 are on hand at site MAIN?”
“Which work orders are late?”
“Enter a sales order for 50 of item 100-220 for Acme.”
“Which purchase orders for steel are past due?”
“What shipped yesterday?”

Each request runs through the Rootstock tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.

[ 03 / What teams build ]

What teams build on Rootstock. Agents and workflows, across systems.

Order to cash

EDI and store orders into Rootstock

Orders from EDI partners and Shopify become Rootstock sales orders, and ship notices go back.

EDI (X12, EDIFACT, AS2)ShopifyRootstock
Finance

Rootstock and the general ledger

Shipments and receipts flow to NetSuite, Sage Intacct or QuickBooks when finance runs outside Salesforce.

RootstockNetSuiteSage Intacct
Production

Late work orders, flagged

When a work order falls behind, the planner and the account owner hear in Slack.

RootstockSlack
Sales

Answers on the account

An agent answers stock, order and ship-date questions from Rootstock. Its toolset holds read tools only.

SalesforceRootstock

Every integration runs both ways, so any of these flows can also run in reverse. These are examples, not the limit: any flow between Rootstock and another system engini connects is available.

[ 04 / Agent Policy ]

You decide what each agent may do in Rootstock. engini enforces it on every call.

Toolsets

Only the tools you allow

A toolset lists the Rootstock 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.

MCP servers

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.

Identity

Whose permissions apply

Connect a person's own Rootstock account and engini acts as that person, with their Rootstock permissions. Use a shared integration account and it acts as that account. Every run is recorded under the user who started it.

Credentials

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.

Audit

Every call on record

Every call lands in History and the audit log, which you can export or stream to your SIEM.

Environments

Test before production

Workspaces keep teams apart, and development, staging and production environments keep a test agent away from live data.

SOC 2 Type IIISO 27001GDPRSecurity at engini →
[ 05 / Set up ]

Connect Rootstock in three steps. Then decide what each agent may do.

Step 01

Sign in to Rootstock

Add a Rootstock connection by signing in to the Salesforce org where Rootstock is installed, with a user that holds only the Rootstock permission sets the workflows need.

Step 02

Choose the tools

Add the connection to an MCP server or a toolset with only the tools each agent needs.

Step 03

Build or ask

Use the connection as a step in a workflow, or ask your agent to work in Rootstock from Claude, ChatGPT, Cursor or your own code.

[ 06 / Questions ]

Rootstock and engini. Straight answers.

Can an AI agent write to Rootstock, or only read?

Both. engini has tools to enter and change sales orders, raise purchase orders, open work orders and keep items 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.

How is this different from the Salesforce connection?

Rootstock lives in Salesforce, so its data sits in Salesforce objects. This page adds named Rootstock tools on top of the same Salesforce sign-in.

Does the agent act as me in Rootstock?

It acts as the Salesforce user behind the connection, with that user's Rootstock permission sets. Every run is recorded under the person who started it.

Can a change in Rootstock start work?

Yes. Scheduled triggers check for new or changed sales orders, work orders and shipments. A workflow can include an AI agent step.

What if the tool I need is not listed?

Use Send API Request to call any Rootstock API endpoint through the same connection, and give it only to the agents that need it.