Autodesk Construction Cloud
Planned: add daily reports, file photos and log issues in Autodesk Construction Cloud (Autodesk Build) by text from the jobsite.
Not available yet. This page describes what's planned for Autodesk Construction Cloud. Ask in your thread and we'll text you when it's ready.
Status: planned — not available to connect in Tack yet. These steps prepare the integration; creating vendor credentials does not enable it in the app.
Planned workflows
Section titled “Planned workflows”Planned for Autodesk Construction Cloud:
| You text | What would happen in Autodesk Construction Cloud |
|---|---|
| “Daily for 12 Oak: 6 framers, framing 80% done” | Fills in a daily report form |
| (photo) Water damage in unit 4 subfloor | Creates an issue with the photo |
These are intended workflows, not a guarantee that every operation is exposed by the vendor. Each must pass the API and permission checks below before release.
Before you start
Section titled “Before you start”Identify the customer’s hub, project and Autodesk product. Current Autodesk Docs administration uses Autodesk Forma terminology; older deployments may still show ACC or BIM 360 labels.
Developer setup — once
Section titled “Developer setup — once”- Create an application in Autodesk Platform Services and record its client ID.
- Select authentication and scopes from the reference for each intended API. A Docs file API and an issue API need separate endpoint and permission checks.
- For a constrained background integration, configure a Secure Service Account (SSA) before the customer adds the integration. Do not treat a legacy two-legged integration as equivalent to restricted user access.
Customer setup — repeat for each hub
Section titled “Customer setup — repeat for each hub”- A hub admin opens Custom integrations → Add custom integration.
- Enter the APS client ID, integration name and description, then continue.
- Attach the intended SSA. With one SSA it is attached automatically; with several, specify its email.
- Invite the SSA to the intended projects and assign only the required permissions. Review the per-project integration access.
- Confirm the integration is Active. If no SSA exists, Autodesk warns the integration can receive hub-admin access; stop and review this with the admin before accepting it.
Autodesk documents the custom integration and SSA behavior, including these access differences.
Verify write access
Section titled “Verify write access”Read a designated project, create a test issue or upload a test document only where the chosen API supports it, and verify the result in the product. Confirm a project outside the permitted set is inaccessible. Document product IDs, folder permissions and any separate issue permissions; a successful hub lookup proves none of those writes.
Disconnect and troubleshoot
Section titled “Disconnect and troubleshoot”In Custom integrations, set the integration to Inactive to pause it, or use its More → Delete integration action to remove it. Review SSA project membership too. Existing integrations without an SSA must be recreated to attach one. Administration instructions.
Who completes the work?
Section titled “Who completes the work?”An agent/developer can implement the connector, field mappings and automated checks. A customer administrator must authorize account access and permissions; the vendor must approve any restricted partner access. A business operator verifies the test records before production use. Follow the shared setup and release checklist for credential handling, approval gates and launch checks.
Setup guidance reviewed October 23, 2026. Vendor menus and entitlements can change; unresolved details are called out above.