Aconex document filing with AI: stop renaming PDFs by hand.

Can AI file Aconex documents automatically?

Yes. Aconex lets a registered integration download documents and mail through its API, rename each file as it comes down and send it to a set location. An AI step on top reads each file, works out what it is and which project folder it belongs in, and files it in SharePoint or Dropbox the same way every time.

The manual version is familiar to anyone on a project: open the transmittal, download the drawing or the RFI response, save it as a PDF, rename it to your own convention, find the right folder, drop it in. Multiply that by every document on a large job and it becomes a real chunk of someone's week, done slightly differently by each person.

The automated version has three parts. Aconex supplies the files. A filing step decides the name and the folder. Your own storage, usually SharePoint or Dropbox, holds the result with a retention rule on it. The AI part is the middle step, and it is the smallest of the three. Most of the work is agreeing the naming convention and folder structure first, because the machine will follow it exactly, including any bad habits you give it.

What can you get out of Aconex without the API?

Quite a lot. You can select documents in the Document Register and download them as a zip, export register and mail reports to Excel, and order archives of your project documents and mail. None of these rename or sort files for you, which is the part that eats the time.

If all you need is a clean record at handover, the archive options may be enough on their own. Ask your Aconex project administrator what your organisation is entitled to before you build anything. If the problem is the weekly grind of filing as the job runs, the API is the route.

What does the Aconex API allow?

The Aconex APIs cover Mail, Documents, Directory, Projects and Tasks. Oracle's own help pages say the APIs can keep local copies up to date as new revisions arrive, send each file to a different destination and rename each file as it downloads. Every integration has to be registered, and a customer can register one for its own internal use.

A few practical points from Aconex's getting started guide that matter to an owner rather than a developer:

• You can do this for yourself. Aconex customers can register integrations for their own organisation. You do not need to be an Oracle partner to automate your own filing.
• You test before you touch a live job. The guide describes testing in a practice environment first, then setting up separate credentials for production.
• Sign-in method matters. Oracle recommends OAuth and says it plans to retire the older Integration IDs toward the beginning of 2027. Anything built now should use OAuth so it does not need rebuilding next year.
• Keep access narrow. Give the integration the projects and permissions your document controller would have, and no more. Your IT person will ask, and it is the right answer.

When we checked, we did not find a ready-made Microsoft connector for Aconex, so linking it to Microsoft 365 usually means a small custom connector or a short script on the API. That is a build, not a setting you switch on, and it is the piece most firms want help with. If you are already on Microsoft 365, our guide to Power Automate for small business explains how the Microsoft side of a flow like this fits together.

Should Aconex files go into SharePoint or Dropbox?

Put them wherever your team already works and where you can set a retention rule. For most firms on Microsoft 365 that is SharePoint, because retention policies and labels can be applied to whole sites or single files. Dropbox works too if that is where the business lives. What matters most is one agreed folder structure.

Before anything is automated, settle three things on paper:

1. The naming convention. For example: project number, document number, revision, short title. Aconex already holds most of this in the register, so the filing step can build the name from it rather than guess.
2. The folder structure. One project folder, then a fixed set of subfolders such as drawings, RFIs, variations, correspondence, and reports. Keep it shallow. Deep trees are where filing goes wrong.
3. What not to file. Superseded revisions, duplicate transmittals and internal chatter do not all need a copy. Deciding this up front stops the over-filer problem being automated.

The AI step earns its keep on the things the register does not say outright: which variation an email is really about, whether an attachment is a revised drawing or a marked-up copy, which subfolder a loosely titled report belongs in. It reads the document, applies your rules, and files. Where it is unsure, it should put the file in a review folder and tell someone, not guess. That one rule is the difference between a system people trust and one they quietly stop using.

On Microsoft 365, Copilot and the wider Microsoft AI tools can then search and summarise across the filed documents, which is far more useful once everything sits in one consistent place.

How long do you need to keep construction project documents?

It depends on the record and the state, so ask your lawyer and accountant for your own list. As a guide, the ATO generally asks for business records to be kept for five years, company financial records are commonly kept for seven, and building claims in some states can be brought up to ten years after completion.

The ATO's record keeping rules start at five years, with some records needing longer. Company financial records under the Corporations Act are commonly kept for seven years. In Victoria, the Building Act sets a ten-year limit on building actions, generally counted from the occupancy permit or certificate of final inspection, and other states have their own rules. A consultancy that may need to show what it advised, and when, on a job finished nine years ago has every reason to keep the full project record.

Two points worth acting on:

• Do not rely on Aconex alone as your archive. The project belongs to whoever runs it, and your access ends with the job unless you arrange an archive. Your own copy, in your own storage, is the record you control.
• Make retention automatic. In SharePoint, a Microsoft 365 retention policy can keep content for a set period, and keep a copy even if someone edits or deletes the original. That protects you from the person who tidies up a folder in year four.

What does a daily Aconex digest look like?

A short email or Teams message each morning listing the Aconex mail and documents that need a decision from you: RFIs awaiting a response, new revisions on drawings you are working from, variations, anything overdue. Everything else is filed and searchable, but not in front of you.

Aconex already sends notifications. The problem is volume, not visibility. On a busy project, the one RFI with a deadline tomorrow sits among a pile of routine transmittals. A digest reads them all and sorts them into three groups: needs you today, worth knowing, filed. It can also flag the gap that costs money on a job, such as a response that was due yesterday and has not gone out.

The same approach works on your normal inbox. Our email automation work often starts here: a morning summary of the urgent unread mail, with filing handled underneath. If you would rather build the digest inside Microsoft 365, the Copilot Studio examples post shows what an agent like this looks like in practice.

Is it safe to connect AI to Aconex, Outlook and Dropbox?

It can be, if it is built to a short written plan your IT person can check: which accounts it signs in with, what it can read and write, where files go, which AI service processes them, and whether that service trains on your data. A good build answers all of that before it touches a live project.

In our experience, the IT review is not a blocker, it is the fastest way to a yes. What wins it is a plain-English explainer of how the pieces connect and a live run on one of your own documents, so nobody is approving something they have not seen work. Settle these with your IT person:

• The integration uses its own registered credentials, with OAuth, not a staff member's password.
• It has read access to Aconex and write access to one destination folder, nothing broader.
• The AI service is on a business plan where your content is not used for training.
• There is a log of every file it moved, so filing can be audited.

How we handle access and data on every build is on our security page.