Exporting the full Content Center to Excel: zero AI, days of work saved

This add-in does not contain a single prompt. Zero AI. And it is one of the projects that best explains how I decide when to use artificial intelligence and when not to.

The problem

An industrial manufacturer needed to review and clean up its Content Center libraries: thousands of families and components accumulated over years of projects. To do that cleanup with judgment, the team needed to see all the content in a format they could filter, sort and annotate. In other words: Excel.

The Content Center does not offer that export out of the box. Doing it by hand, family by family, was unthinkable. That is the starting point of almost all my projects: a legitimate process the software does not cover, and that costs days when done manually.

The solution

I built an add-in for Vault Explorer 2025 that does exactly one thing and does it well: it walks the Content Center libraries and exports to Excel the files linked to the Item Master, which were the relevant ones for the cleanup.

The technical detail I like most: the add-in works with the user's own authenticated session. It does not ask for separate credentials, it does not create service accounts, it does not touch the server. If you have access to those libraries, so does the add-in; if you do not, neither does it. The same permission principle I apply in my AI agents, applied to a classic tool.

Why no AI

Because the problem is deterministic. The list of families is what it is, the links to the Item Master either exist or they do not, and the output Excel has a fixed format. There is no ambiguity to interpret and no natural language to understand. Putting an LLM in there would only add latency, cost and a new source of errors.

The right question is never "how do I add AI to this". It is "what is the simplest tool that solves the problem". Sometimes the answer is a conversational agent with 28 tools. Sometimes it is a good old add-in that runs in minutes and does not fail. Knowing which one applies is part of the job, and it is the difference between selling solutions and selling trending technology.

The result

The team went from being unable to audit its libraries to having the full inventory in Excel, ready to filter and decide what stays, what gets fixed and what gets removed. Days of manual work turned into a reproducible export they can run as many times as they want.

Classic automation done right: Autodesk API, judgment and testing. No hype.

How to decide in your case

Before automating anything I ask myself three questions. Is the process deterministic or does it require interpreting ambiguity? How many times will it repeat? What happens if it fails? Deterministic, frequent and with failures that are cheap to detect: classic automation. Ambiguous, conversational and surrounded by strong validations: that is where an agent makes sense.

If you have a process stuck in Inventor, Vault or the Content Center and you are not sure which of the two categories it falls into, that conversation is exactly my job. Write to me and we will look at it honestly: sometimes the answer is an agent, and sometimes it is a well-built Excel.