0.7.0

Simpro runs on a connector we build and maintain ourselves, with 260 tools spanning jobs, quotes, customers, sites, contacts, invoicing, cost centres, catalogues, scheduling, assets, contracts, stock, work orders and recurring work.

Every one of those was exercised against a real Simpro build before release. That mattered more than usual here: Simpro's own documentation misstates several fields it treats as required, and the only way to find them is to run real work through it.

Connecting is a pasted key, not a sign-in redirect

Simpro does not offer integrations like ours the usual sign-in-and-approve flow. Instead, an admin on your build creates an API key under System → Setup → API → Applications and pastes it into FloConnector along with your build address.

Two things follow from that, and both are worth knowing before you make the key. It does not expire, so it keeps working until someone revokes it in Simpro. And what it can reach is governed by the security group of the Simpro user it belongs to, so a key made from a restricted user gives your AI exactly that restricted view. If you want your AI limited to quoting, make the key from a user who can only quote.

If the key reaches more than one company on the build, you choose which one the connection is for.