Connect · Construction accounting and ERP
Connect Sage 300 CRE to Claude and ChatGPT
Early access · Through the Junction agent
How Junction connects to Sage 300 CRE
Sage 300 CRE is usually reached only from the machine it runs on, through a 32-bit ODBC driver. The Junction agent is installed on that server, copies the tables it needs into a local file every 15 to 60 minutes, and answers questions from the copy, so the live system is never queried. Every answer shows when the data was last copied.
Questions you could ask about Sage 300 CRE
- “Which jobs have costs ahead of billings?”
- “What is the status of every open subcontract?”
- “Which vendors are owed more than 60 days?”
Answers come from your own system, with the source rows and the time the data was last updated.
What to know
- This is the case other AI connectors tend to skip: older on-premise systems with no cloud API.
- Early access: the Sage 300 CRE mapping needs the real table list from a design partner and has not been built yet.
- The agent connects outward only. You open no inbound ports.
Frequently asked questions
- Does Sage 300 CRE work with Claude or ChatGPT?
- Not directly. A Junction agent on your Sage server reads a copy of the data, and Junction answers questions from it when your Claude or ChatGPT asks. Sage 300 CRE support is in early access.
- How fresh is the data?
- As fresh as the last copy, usually within 15 to 60 minutes. Every answer says when the data was last updated.
- What do I install?
- A small program on the server that has the Sage ODBC driver. It dials out to Junction, runs only queries it builds from a signed data model, and can be switched off from your portal.
Run Sage 300 CRE? Tell us.
We bring each system online with a customer who uses it. Early customers shape what we build first.
Reach out to salesSage 300 Construction and Real Estate is a product of Sage. Junction is not affiliated with, endorsed by or sponsored by Sage; product names are used only to describe compatibility.