tc_organizer
Manage project breakdown structures and nodes in Trimble Connect. Create, update, and organize trees, nodes, and policies to control data hierarchy and access.
Instructions
Trimble Connect Organizer Service: forests, trees (breakdown structures like LBS), nodes, policies, changesets. forestId is usually the Trimble Connect projectId. Regional service URI is resolved automatically. Select the endpoint with the "action" parameter. Path placeholders {projectId}/{id}/{subId}/{extraId}/{version} are filled from the matching input parameters. Actions:
trees_list: GET /forests/{id}/trees — id=forestId (projectId)
tree_get: GET /forests/{id}/trees/{subId} — id=forestId, subId=treeId, query: {deleted?}
tree_create: POST /forests/{id}/trees — id=forestId, body: {name, type} e.g. type='LBS'
tree_update: PATCH /forests/{id}/trees/{subId} — id=forestId, subId=treeId, body: fields to update
tree_delete: DELETE /forests/{id}/trees/{subId} — id=forestId, subId=treeId
tree_policy_get: GET /forests/{id}/trees/{subId}/policy — id=forestId, subId=treeId
tree_policy_put: PUT /forests/{id}/trees/{subId}/policy — id=forestId, subId=treeId, body: policy
nodes_list: GET /forests/{id}/trees/{subId}/nodes — id=forestId, subId=treeId, query: {top?, skiptoken?}
node_get: GET /forests/{id}/trees/{subId}/nodes/{extraId} — id=forestId, subId=treeId, extraId=nodeId
node_create: POST /forests/{id}/trees/{subId}/nodes — id=forestId, subId=treeId, body: node
node_update: PATCH /forests/{id}/trees/{subId}/nodes/{extraId} — id=forestId, subId=treeId, extraId=nodeId, body
node_delete: DELETE /forests/{id}/trees/{subId}/nodes/{extraId} — id=forestId, subId=treeId, extraId=nodeId
node_links: GET /forests/{id}/trees/{subId}/nodes/{extraId}/links — id=forestId, subId=treeId, extraId=nodeId
node_versions: GET /forests/{id}/trees/{subId}/nodes/{extraId}/versions — id=forestId, subId=treeId, extraId=nodeId
node_version_get: GET /forests/{id}/trees/{subId}/nodes/{extraId}/versions/{version} — id=forestId, subId=treeId, extraId=nodeId, version
search_forest: GET /forests/{id}/search — id=forestId, query: search params
search_tree: GET /forests/{id}/trees/{subId}/search — id=forestId, subId=treeId, query: search params
batch_get_nodes: POST /batch-get — body: batch node keys
changeset: POST /forests/{id}/trees/{subId}/changeset — id=forestId, subId=treeId, body: changeset
changeset_async: POST /forests/{id}/trees/{subId}/changeset-async — id=forestId, subId=treeId, body: changeset
changeset_status: GET /changeset/{id} — id=changesetId
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Primary resource ID — required when the action path contains {id} | |
| body | No | JSON request body for POST/PUT/PATCH (and some DELETE) actions | |
| query | No | Query parameters as key-value pairs | |
| subId | No | Secondary resource ID — required when the action path contains {subId} | |
| action | Yes | Endpoint to call (see tool description) | |
| region | Yes | Trimble Connect region: us (North America), eu (Europe), ap (Asia-Pacific), ap-au (Australia) | |
| extraId | No | Tertiary resource ID — required when the action path contains {extraId} | |
| version | No | Version number — required when the action path contains {version} | |
| projectId | No | Project ID — required when the action path contains {projectId} | |
| bcfVersion | No | BCF API version for BCF actions (default 2.1) |