group trimble connect model objects into custom hierarchies with the organizer api
domain: developer.trimble.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Complete the standard Trimble Connect Get Started access flow (app registration plus OAuth access token) before calling the Organizer Service.
Create a Forest as a namespace container, then create Trees within it to hold hierarchical Nodes.
Add Links to each Node that point to external resources such as BIM model objects, using FRN notation, rather than storing the items themselves.
Define access control policies on the tree to set read/write/no-access permissions per user or group.
Follow the special API and access-control conventions required to make the hierarchy visible inside Trimble Connect's own Organizer panel.
Known gotchas
If the special Trimble Connect ecosystem conventions aren't followed, Organizer trees are created successfully but won't appear inside Trimble Connect's own applications.
A valid Trimble Connect license is required to fully use Organizer data inside Trimble Connect apps, separate from having API access.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?