Claude + Autodesk Construction Cloud: What the Integration Can (and Can't) Do in 2026
Not for Construction Cloud — there’s no official Claude connector for Autodesk Construction Cloud (ACC) or Autodesk Build. There’s a real subtlety here worth clearing up. Autodesk does have an official connector in Anthropic’s directory, but it’s Autodesk Fusion — the CAD/3D design tool, part of the “Claude for CAD” push with Blender. That’s for turning words into 3D geometry, not for RFIs, submittals, issues, or daily logs. For the construction side — ACC and Build — nothing is in the directory. What you get instead is a real, self-serve Autodesk developer platform that a technical person can build against, plus a few community-built connectors that wrap it.
Here’s what’s actually available for ACC, how you’d wire it up, where the limits bite, and what to use if you want project work that runs on its own.
The one place Autodesk is official: Fusion, not the field
If you searched “Claude Autodesk” and found a connector, read the fine print. The directory connector is Autodesk Fusion — design and modeling, plain language in and geometry out. It’s genuinely official and genuinely useful if you’re a designer. It does nothing for a project engineer chasing overdue submittals in Autodesk Build.
Autodesk has also shipped an official Revit connector (2026) — again, the desktop design side, not the cloud project-management side. So the pattern is clear: Autodesk’s first-party Claude work is landing in the design tools first. ACC and Build are still on the do-it-yourself path.
The Autodesk data is reachable — but the rules just changed
The good news for ACC is that Autodesk runs a proper developer platform that opens up ACC and Autodesk Build data — projects, issues, RFIs, submittals, forms, and the files and folders — to an outside app through an API key. It can even notify an app when something changes (a new issue, an updated RFI), and it offers a safe test environment to try things against.
Two things to know before you budget time:
- The rules changed in December 2025. Autodesk moved to Free and Paid tiers, and every developer had to re-enroll and move their apps to a new developer hub. Firms that didn’t finish by January 16, 2026 had their access suspended until they enrolled (details). The free tier is real but metered; heavier use is paid.
- Someone with account rights has to authorize the app against your ACC hub before it can touch live projects — the same gate as any ACC integration.
So a technical team can absolutely build against ACC. It’s a build-and-maintain project with a billing dimension, not a connector you toggle on.
How you’d actually connect Claude to ACC today
No first-party ACC connector exists, so the routes are your own build or a community one:
- Community-built connectors. Several wrap the ACC/Build data — for example an ACC Issues connector, an Autodesk Build connector for issues, RFIs, and submittals, and an experimental one for ACC/BIM 360 data. All unofficial — vet before handing over credentials.
- Your own connector. Create an app at aps.autodesk.com, enroll in a plan, set up access, and point a small connector at the ACC data. Autodesk’s own how-to blog walks the pattern.
Either way, you’re adding Autodesk to Claude as a custom connector — in the AI world these are called MCP connectors, which just means a small piece of software someone technical builds and runs to sit between Claude and the app. The remote kind needs a paid Claude plan; local ones run through the Claude Desktop app or Claude Code. There’s no mainstream Zapier connector for ACC either — Autodesk’s own middleware (Forma Construction Connect) is built for wiring business apps to each other, not for bridging to Claude.
The limits that actually matter
Even with a community connector running, the shape is “an assistant you operate,” not “an agent that runs”:
- No triggers, no monitoring. Autodesk can notify an app when a new issue, RFI, or submittal changes — but Claude can’t receive those notifications. Its tools only run inside a conversation you start. Nobody’s watching the ball-in-court clock while you’re on site.
- Conversation-only. Claude pulls open RFIs or yesterday’s issues when you ask; it doesn’t sit on your hub and follow up. Close the chat and nothing continues.
- Can’t send on its own. Claude’s built-in email drafts messages in both Gmail and Outlook but doesn’t send them, and only while you’re in the chat. You could pay a developer to build sending in too, but it’s one more thing to maintain and it still only fires while you’re driving the chat.
- Laptop-bound for anything scheduled. The closest thing to autopilot is Claude’s scheduled tasks, which fire on a fixed clock, not on events — Cowork has no inbox of its own to receive work, and each check counts against your Autodesk usage tier.
So Claude via a community connector is a decent “query my projects in a chat” tool for a technical team, and not built for “keep RFIs and submittals moving on their own.”
If you want ACC work that runs on its own: Carly
Construction runs on clocks — ball-in-court days, submittal due dates, daily logs piling up across active jobs. None of it waits for someone to open a chat.
That’s the difference that matters here. ACC isn’t a Claude connector — Fusion (CAD) is, ACC isn’t — and the do-it-yourself route means building and babysitting your own connector, so a Claude setup stays a desk-side lookup you drive by hand. Carly is an AI executive assistant built to act on triggers: it works ACC through those same Autodesk credentials — paste them on carlyassistant.com/integrations (same authorization gate as any ACC integration) — but on events and schedules, 24/7 in the cloud:
- When a new RFI is opened, Carly summarizes the question, pulls the relevant sheet and spec context, drafts a response for the PM, and starts the ball-in-court reminder clock.
- When a submittal is received, Carly logs it, routes it to the responsible reviewer, and drafts the acknowledgment to the architect — then nudges again as the due date nears.
- When an issue is opened or a sheet is updated, Carly flags the affected trades and drafts the notice so nothing changes silently on the field.
- When daily logs are due, yesterday’s logs across active projects roll up into one 6am exec digest — manpower, weather, delays, safety notes.
- Actually sends — drafts and sends email across Gmail and Outlook, updates tasks and records.
- No-code setup. Describe the workflow in plain English; Carly interviews you and builds it with you.
- Connects to anything — 200+ native integrations (see integrations), plus any tool with an API via your own key.
AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited.
Claude’s Autodesk options vs Carly
| Claude (community setup) | Carly | |
|---|---|---|
| Read ACC issues, RFIs, submittals | Yes, via community connectors | Yes, via your Autodesk credentials |
| Reacts when an RFI or issue lands | No | Yes, on events |
| Morning cross-project digest, unprompted | No | Yes, on a schedule |
| Runs on event triggers | No | Yes (cloud) |
| Sends the emails itself, not just drafts | No — drafts only | Yes (Gmail + Outlook) |
| What it takes to set up | Build & run your own connector (or use a community one) + admin authorization | Paste your Autodesk credentials (same admin authorization applies) |
| Pricing | Pro $20 / Max $100–$200 + Autodesk usage + upkeep | AI agents from $35/mo |
Claude over a community connector is a query console for your projects. Carly is a project coordinator that works the clock between site visits.
Frequently Asked Questions
Does Claude work with Autodesk Construction Cloud?
Not officially. There’s no ACC or Autodesk Build connector in Claude’s directory. The official Autodesk connector in Anthropic’s directory is Autodesk Fusion (CAD/design), and Autodesk’s other first-party work is on Revit — neither touches ACC project data. For ACC you use community-built connectors or your own connector against the Autodesk developer platform, both of which need your own developer app and account authorization.
Isn’t there an official Autodesk Claude connector?
Yes, but for the wrong tool if you’re in the field. It’s Autodesk Fusion — 3D CAD, words-to-geometry — part of the “Claude for CAD” release. ACC, Build, and BIM 360 are not covered by a directory connector.
How do I connect Claude to Autodesk Build’s RFIs and submittals?
Create an app at aps.autodesk.com, enroll in an Autodesk developer plan (the tiers changed in December 2025), set up access, and run a community connector or your own against the ACC data, added to the Claude Desktop app or Claude Code. It works for in-chat queries; there are no triggers.
What if I want ACC to act on its own — RFI alerts, submittal nudges, daily-log digests?
That’s outside what Claude does; it responds inside a chat and can’t receive Autodesk’s notifications. Carly connects to ACC via your Autodesk credentials, fires on events and schedules 24/7 in the cloud, and can email reviewers, nudge on due dates, update records, and send digests. AI agents start at $35/month.
More: Claude + Procore · Claude + Jobber · Claude connectors · Can Claude send emails · Claude vs Carly
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
