tc_activities
List, query, and export activity logs for Trimble Connect projects to track changes and audit project activities.
Instructions
Trimble Connect Activities (audit trail) and activity exports. Select the endpoint with the "action" parameter. Path placeholders {projectId}/{id}/{subId}/{extraId}/{version} are filled from the matching input parameters. Actions:
list: POST /activities/list — body: {objectType:'PROJECT', objectId, pageSize?, filters?}
list_by_query: GET /activities — query: {projectId, ...}
get: GET /activities/{id} — id=activityId
logs: GET /activities/{id}/logs — id=activityId
create_export: POST /activities/exports — body: export request
get_export: GET /activities/exports/{id} — id=exportId
Input Schema
TableJSON 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) |