Engineers searching for “Power Automate convert CAD” are usually trying to solve one of two problems: they have a folder of DWG or STEP files that need to be converted on a schedule, or they want to trigger conversion when a file lands in SharePoint. Power Automate can do both — but the mechanism is different from what most people expect, because there are no native CAD connectors in Power Automate’s connector library.

Here’s what actually works.

The Two Approaches

Power Automate has two execution environments that are relevant for CAD conversion:

Desktop Flow (Power Automate Desktop): Runs on a local Windows machine. Can launch any application, run command-line tools, and interact with the file system directly. This is where local CAD conversion happens.

Cloud Flow: Runs in Microsoft’s cloud. Can trigger on SharePoint/OneDrive file events, call HTTP endpoints, and orchestrate work across systems. For CAD conversion, it either hands off to a Desktop Flow (via an on-premises gateway) or calls an external API like Autodesk Platform Services.

For most engineering teams, the Desktop Flow path is simpler and has fewer dependencies.

Path 1: Desktop Flow + ODA File Converter (DWG/DXF/DWF → PDF/DXF/SVG)

ODA File Converter is a free command-line tool from the Open Design Alliance that converts between DWG, DXF, DWF, and DGN formats. It’s the same engine behind many commercial tools. It runs silently on Windows with no GUI required, making it a good target for automation.

Installing ODA File Converter

Download the Windows installer from the Open Design Alliance website and install it. The default install path is:

C:\Program Files\ODA\ODAFileConverter\ODAFileConverter.exe

The ODA File Converter command

ODA File Converter takes parameters in this order:

ODAFileConverter.exe [InputFolder] [OutputFolder] [InputVersion] [OutputVersion] [Recurse] [Audit]

For DWG to PDF, the format string is:

ODAFileConverter.exe "C:\Input" "C:\Output" ACAD2018 PDF 0 1

For DWG to DXF:

ODAFileConverter.exe "C:\Input" "C:\Output" ACAD2018 DXF 0 1

The Recurse flag (0 or 1) controls whether subdirectories are processed. The Audit flag (0 or 1) controls whether the converter attempts to fix corrupt files before converting.

Building the Desktop Flow

In Power Automate Desktop, create a new flow. Use the following actions:

1. Set variables for paths:

Set variable InputFolder to: "C:\CAD\Input"
Set variable OutputFolder to: "C:\CAD\Output"
Set variable ODAPath to: "C:\Program Files\ODA\ODAFileConverter\ODAFileConverter.exe"

2. Run ODA File Converter: Use the “Run application” action:

  • Application path: %ODAPath%
  • Command line arguments: "%InputFolder%" "%OutputFolder%" ACAD2018 PDF 0 1
  • Wait for completion: Yes
  • Timeout: 600 seconds (adjust for large batches)

3. Optional: Move processed files to an archive folder: Use the “Move files” action to move source files after conversion, preventing re-processing.

4. Optional: Send notification: Use the “Send email” action or Teams notification to report conversion completion and file count.

This flow converts every DWG in the input folder to PDF and moves the results to the output folder. Run it on a schedule (Windows Task Scheduler or Power Automate’s built-in schedule trigger) or trigger it from a Cloud Flow.

Connecting a Cloud Flow trigger to the Desktop Flow

If you want conversion to fire when someone uploads a file to SharePoint, you need:

  1. A Cloud Flow with a SharePoint “When a file is created” trigger
  2. A Desktop connection (Power Automate Desktop must be installed on a machine that’s always on)
  3. The “Run a flow built with Power Automate for desktop” action in the Cloud Flow

The Cloud Flow fires when the SharePoint upload happens, calls the Desktop Flow on your gateway machine, and the Desktop machine runs ODA File Converter against a sync’d local copy of the SharePoint library.

This requires a per-user Power Automate license with the “Attended RPA” or “Unattended RPA” add-on ($40/user/month as of 2026). Unattended RPA runs without a logged-in session — necessary if the machine runs overnight without anyone logged in.

Path 2: Cloud Flow + Autodesk Platform Services API (DWG → SVF/PDF)

If you don’t want to run a local machine 24/7, Autodesk Platform Services (APS, formerly Forge) provides a cloud Model Derivative API that converts DWG, STEP, IGES, and other CAD formats to viewer-friendly or output formats.

The flow: upload DWG to APS object storage → trigger translation → poll for completion → download output → store in SharePoint.

APS API authentication

APS uses OAuth 2.0 client credentials. In your Power Automate Cloud Flow, use an HTTP action to get a token:

POST https://developer.api.autodesk.com/authentication/v2/token
Content-Type: application/x-www-form-urlencoded

client_id=YOUR_CLIENT_ID&client_secret=YOUR_CLIENT_SECRET&grant_type=client_credentials&scope=data:read data:write data:create bucket:read bucket:create

Store the access_token from the response in a variable.

Upload file to APS

PUT https://developer.api.autodesk.com/oss/v2/buckets/{bucketKey}/objects/{objectKey}
Authorization: Bearer {access_token}
Content-Type: application/octet-stream

[binary file content]

In Power Automate, use “Get file content” from SharePoint and pipe it as the body of this HTTP action.

Trigger translation

POST https://developer.api.autodesk.com/modelderivative/v2/designdata/job
Authorization: Bearer {access_token}
Content-Type: application/json

{
  "input": {
    "urn": "[base64-encoded object URN]"
  },
  "output": {
    "formats": [{"type": "pdf"}]
  }
}

Poll for completion

Translation is asynchronous. Add a “Do until” loop in Power Automate that polls:

GET https://developer.api.autodesk.com/modelderivative/v2/designdata/{urn}/manifest
Authorization: Bearer {access_token}

Loop until the status field in the response equals "success" or "failed". Add a Delay action between polls (30–60 seconds) to avoid hitting rate limits.

Download output

When status is "success", extract the derivative URN from the manifest and download:

GET https://developer.api.autodesk.com/modelderivative/v2/designdata/{urn}/manifest/{derivativeUrn}
Authorization: Bearer {access_token}

Save the response body to SharePoint or another destination.

APS limitations for this use case

Output formats are limited. APS Model Derivative converts DWG/STEP/IGES to SVF2 (their 3D viewer format), OBJ, STEP, IGES, SVG, and PDF. It does not produce DXF output. For DXF, you need Path 1 (ODA on a local machine) or a different API.

Costs add up. APS charges per translation. As of 2026, each translation costs 1–25 tokens depending on file size, and tokens run $0.0035–0.007 each. A large DWG (50+ MB) can cost $0.05–0.15 per conversion. For hundreds of files per month, budget accordingly.

PDF output is view-quality, not plot-quality. APS PDF output is rendered from the viewer, not plotted from layout paper space like AutoCAD’s PUBLISH command. For engineering documentation that needs precise lineweights and plot styles, this is usually not acceptable. The ODA approach on Path 1 produces cleaner PDF output for most DWG workflows.

What Power Automate Can’t Do (Without Additional Tools)

Native SolidWorks conversion: There is no Power Automate connector for SolidWorks, and SolidWorks has no headless CLI mode. To automate SolidWorks exports (DXF, PDF, STEP) from within Power Automate, you need either a Task Scheduler script that calls a SolidWorks macro, or a dedicated SolidWorks add-in like CadShift that separates the export logic from the manual UI.

Reliable STEP-to-PDF conversion: No free CLI tool handles STEP-to-PDF reliably. FreeCAD can do it via Python scripting, and APS can do a viewport render, but neither produces proper 2D engineering PDF output.

File locking and PDM integration: Power Automate has no awareness of PDM check-out states. If you run a conversion flow while someone has a file checked out and partially modified, you’ll convert a stale version. For PDM shops, trigger conversions off PDM lifecycle transitions (file Released event) rather than file system watches.

Choosing the Right Path

ScenarioRecommended Approach
DWG → PDF, local machine, any scheduleDesktop Flow + ODA File Converter
DWG → DXF, batch processingDesktop Flow + ODA File Converter
DWG upload to SharePoint → PDF in SharePointCloud Flow + Desktop Flow via gateway
DWG → 3D web viewer (SVF2)Cloud Flow + APS Model Derivative
SolidWorks → DXF/PDF batchTask Scheduler + SolidWorks macro (not Power Automate)
SolidWorks → DXF from assemblies with BOMCadShift — Power Automate has no SolidWorks connector

For batch DWG conversion without any Power Automate setup, the batch DWG to PDF and DXF guide covers standalone tools that run without cloud integration.

Notes on Licensing and Gateway Setup

Power Automate Desktop is free to download and run for manual desktop flows. For unattended automation (running on a schedule without a logged-in user), you need either:

  • Power Automate per-user plan with unattended RPA add-on (~$40/user/month)
  • Power Automate per-flow plan (~$500/flow/month) — overkill for most teams

The on-premises data gateway (required for Cloud Flow → Desktop Flow communication) is a free Windows service, but it must run on a machine that’s always on and has internet access.

For small engineering teams doing occasional batch conversions, the simplest working setup is: schedule the Desktop Flow directly in Windows Task Scheduler rather than going through the Cloud Flow layer at all. Power Automate is most valuable when the trigger comes from an external system (SharePoint upload, Teams message, email attachment) rather than a fixed schedule.