Autodesk Construction Cloud Integration
Construction & DevelopmentWhat It Does
Autodesk Construction Cloud (ACC) is the documents, coordination, and model environment that design and construction teams work inside from preconstruction through closeout. It rolls together the products you may know as PlanGrid (field documents and drawings), BIM 360 (model coordination and clash detection), and the newer ACC modules — Build, Docs, Cost, and Model Coordination. Where a project-financials platform tracks the money, ACC is where the drawings, RFIs, submittals, issues, and the federated 3D model actually live, version, and resolve. For a ground-up CRE development, it is the single source of truth for what is being built, what changed, and which questions are still open between the architect, engineers, and the general contractor.
Why Real Estate Professionals Use It
CRE developers running a design-build coordination effort sit downstream of a problem they rarely control directly: the drawings, RFIs, and the 3D model live inside the general contractor's Autodesk Construction Cloud tenant, while the schedule, the budget, and the lender relationship live with the owner. ACC's APS API closes that gap. Document version events, RFI status, submittal timing, and field issues can flow out of ACC and into the owner's schedule tracker, risk register, and reporting — so the development team sees a brewing problem when it is still a question on a drawing, not after it has hardened into a change order. For how ACC sits beside Procore, Northspyre, and the rest of the development stack, read our guide: /blog/best-cre-software-complete-stack.
AI Solutions for Construction
Ebook
CTO's Guide to AI Implementation
Technical framework for CTOs evaluating AI solutions with Build vs Buy analysis
Solution
Property Data Enrichment
Auto-enrich contacts with property ownership, tax records, and market data
Solution
Universal CRM Sync Hub
Keep HubSpot, Follow Up Boss, Salesforce, and spreadsheets in perfect sync
Key Features for Real Estate
Discover how Autodesk Construction Cloud powers real estate automation workflows
1 of 7
Feature
Document and Drawing Management (Docs / PlanGrid)
Central, version-controlled storage for plans, specifications, sheets, and project documents, with current-set tracking, markups, and a full version history exposed through the APS Data Management API.
Real Estate Impact
On a CRE development, the lender, owner's rep, and design team all need to be working from the current drawing set — not a superseded PDF emailed three revisions ago. Automating version events lets you push the latest construction set into your owner's data room and flag the moment a new revision lands, so nobody approves a draw against an outdated scope.
See how we automate Autodesk Construction Cloud
Get a personalized plan for your tech stack
Automation Workflows
Ready-to-deploy workflows powered by Autodesk Construction Cloud + NextAutomation
Workflow 1 of 4
Intermediate
RFI Created → Routing, SLA Tracking, and Schedule-Risk Escalation
When an RFI is created in Autodesk Construction Cloud, the automation logs it against the right development deal, starts an SLA clock based on the RFI due date, and escalates to the project executive — with the delay recorded in your schedule tracker — if it goes overdue without an answer. Closes the gap between an RFI sitting in the GC's queue and the owner's awareness of a brewing schedule risk.
Trigger: New RFI created or RFI status changed in ACC (ACC RFIs API; webhook where available, otherwise scheduled poll of the RFIs endpoint)
Workflow Steps
1n8n receives the ACC RFI event (or polls GET on the project RFIs endpoint on a schedule) for new or updated RFIs
2Map the ACC project ID to your internal deal ID via a lookup table so the RFI lands against the right development asset
3Record the RFI in your schedule/risk tracker (Airtable or Google Sheets) with subject, assignee, discipline, and due date
4Start an SLA timer keyed to the RFI due date or your firm's response standard (e.g., 7 business days)
+4 more steps
RFI delay becomes visible to the owner's team the day it crosses the SLA — not at the next monthly GC meeting. Critical-path questions get escalated while there is still time to protect the schedule.
Triggers & Actions
Connect Autodesk Construction Cloud to your workflows with powerful triggers and actions
Triggers
Document Version Added
Fires through the APS Webhooks service when a new version of a document or drawing is uploaded to a watched ACC project folder. This is among the most reliable, well-supported events on the platform.
When the GC publishes a new construction set, sync the current revision into the owner's data room and post a revision notice so nobody approves a draw against a superseded drawing.
RFI Created or Status Changed
Detects a new RFI or an RFI status change (open, answered, closed) via the ACC RFIs API. Where a published webhook isn't available, this runs as a scheduled poll of the RFIs endpoint.
When a structural RFI passes its due date without an answer, escalate to the project executive and log the delay in the development schedule-risk register.
Submittal Status Changed
Detects a submittal package moving between submitted, in-review, approved, or revise-and-resubmit. Submittals API coverage is lighter than Documents, so this is typically implemented as a scheduled poll.
When a long-lead steel submittal is approved, notify procurement to release fabrication and update the milestone log.
Issue Created or Updated
Fires when a field issue, deficiency, or quality observation is created or changes status via the ACC Issues API, including location and model references where present.
When open issues on an asset accelerate faster than they close, surface a punch-list and certificate-of-occupancy readiness risk to the development team.
Cost / Change-Order Item Updated
Detects a budget, contract, or change-order change inside the ACC Cost module. Cost API coverage is evolving and lighter than Documents, so this is framed as a scheduled poll and used only where your team runs cost inside ACC.
When a change order is recorded in ACC Cost, structure the line and recompute cost-to-complete against the development budget.
Folder or Project Structure Changed
Fires via APS Webhooks on folder-level data management events, letting an automation keep an external index aligned with the ACC project hierarchy.
When a new closeout folder is created, provision the matching owner data-room folder and start tracking documents filed into it.
Actions
Create RFI
Create a new RFI in ACC via the RFIs API from an external source — a field form, an email thread, or an AI-detected ambiguity in the drawing set — with assignee and due date.
When a site form flags a drawing conflict, automatically open an RFI in ACC addressed to the responsible design consultant with the relevant sheet referenced.
Upload Document / New Version
Upload a file or publish a new version into an ACC project folder through the Data Management API, preserving the version history.
After the owner countersigns a design change, upload the executed document into the ACC 'Owner Documents' folder so the full project team works from one record.
Create or Update Issue
Create a field issue or update its status and assignee via the Issues API, optionally tied to a location or model element.
After a third-party inspection report, auto-create ACC issues for each deficiency assigned to the responsible trade with a target close date.
Extract Model / Sheet Data
Use the Model Derivative API to extract sheets, object properties, and metadata from an uploaded model or drawing for indexing or downstream analysis.
On a new model version, extract the sheet index and key properties to build a searchable document index for the owner's data room.
Read Project Directory and Members
Query the ACC Account and project member directory via the APS Account/Admin APIs to resolve assignees, companies, and roles.
When routing an escalation, look up the project executive's contact from the ACC member directory rather than maintaining a separate, drifting list.
Setup Guide
Get started in approximately 1-2 hours for APS app registration, OAuth, and a first read test; 4-6 hours for a webhook-driven document-sync workflow; 1-2 days for a full RFI/submittal/cost automation including accounting and owner-report sync
Prerequisites
- Autodesk Construction Cloud account with the relevant modules (Docs/Build, and Cost or Model Coordination if those workflows apply) and project-admin access to grant your app entitlements
- Autodesk Platform Services (APS, formerly Forge) developer account at aps.autodesk.com to register an app and obtain a Client ID and Client Secret
- Decision on OAuth flow: two-legged (client-credentials) for server-to-server jobs, or three-legged (authorization-code) where the app must act on behalf of a specific project member
- n8n instance (cloud or self-hosted) with the HTTP Request node for APS API calls, or an equivalent automation layer
- A publicly reachable HTTPS endpoint to receive APS webhook callbacks (for real-time document/version triggers)
1
Register an App on Autodesk Platform Services
Sign in at aps.autodesk.com, create an app, and record the Client ID and Client Secret. Subscribe the app to the APIs you need — Data Management, BIM 360 / ACC Account & Admin, Issues, RFIs, Model Derivative, and Webhooks. Define a callback URL if you will use three-legged OAuth.
Request only the scopes your workflows actually use (e.g., data:read, data:write, account:read). Over-scoping an app makes the project-admin approval step slower and harder to justify to the GC who controls the ACC tenant.
2
Choose and Implement the OAuth 2.0 Flow
For background jobs that read documents and model data, use the two-legged client-credentials flow: POST to the APS authentication endpoint with your client_id, client_secret, and the requested scopes to get an access token. For actions taken on behalf of a project member (creating an RFI as a user), implement the three-legged authorization-code flow and store the refresh token securely. Tokens are short-lived — build refresh logic into the workflow.
Three-legged tokens act with a real member's permissions, so creating RFIs or issues shows the correct author in ACC. Use two-legged for read-heavy reporting jobs and three-legged only where authorship and write permissions matter.
3
Grant the App Access to the ACC Account and Projects
ACC data is gated at the account and project level. A BIM 360/ACC account admin must provision your APS app against the account (and the specific projects) before the Data Management, Issues, and RFIs APIs return that project's data. Confirm the entitlement covers each development project you intend to automate.
On developments where the GC owns the ACC tenant, you need their account admin to authorize your app. Get this in the integration kickoff — it is the single most common thing that blocks an otherwise-finished ACC automation from going live.
4
Subscribe to APS Webhooks for Real-Time Triggers
Register webhook subscriptions through the APS Webhooks service for the data-management events you handle — most reliably version-added and folder events on your watched project folders — pointing at your HTTPS callback. Validate the callback handshake and verify the payload signature before processing.
Document and version events are the strongest webhook surface. For RFIs, Submittals, and Cost, plan a scheduled poll as the trigger and treat any published webhook as a bonus — that keeps the automation honest and resilient across Autodesk API releases.
5
Map ACC Projects to Your Internal Deal IDs
Build a lookup table that maps each ACC project ID to your internal development deal ID, owner data-room folder, and Slack/notification channel. Every ACC event flows through this mapping so it lands against the right asset and routes to the right people.
Maintain this mapping in the same Airtable/Sheets base as your deal register. It is the bridge that lets an ACC RFI or version event reference the correct pro forma, data room, and project team automatically.
6
Test a Read Workflow, Then Wire Outputs
Start with a read-only job: fetch the current document versions or open RFIs for one real project via the relevant API and confirm the data shape. Once data flows reliably, connect the outputs — sync current sets to the owner's data room (Google Drive), post RFI/submittal alerts, push structured cost lines to QuickBooks, and write schedule-risk entries to your tracker.
Log raw API responses to a scratch sheet for 30 days while building. APS payload shapes differ across the Data Management, Issues, and RFIs APIs, and having real samples on hand removes most of the guesswork from workflow building.
Frequently Asked Questions
Common questions about Autodesk Construction Cloud integration
Related Integrations
Explore other tools that work great with your workflow
Ready to Automate Autodesk Construction Cloud?
Get a free AI roadmap showing how to connect Autodesk Construction Cloud with your existing tools for maximum impact.
Get Your Free AI Roadmap