Anyone Automated Adobe InDesign with UiPath? Looking for Integration Options & Feasibility Insights

Hi everyone,

I’m currently working on a requirement involving Adobe InDesign(Indd file format), where the goal is to fill data into a template and generate a final PDF. I wanted to check if anyone in the community has successfully automated InDesign or integrated it with UiPath.
Here are my findings so far:

  • UiPath is not able to recognize or interact with InDesign UI elements, so traditional UI automation isn’t possible.
  • Tried UiPath Computer Vision — but due to vertical + horizontal scrolling and the need to replace whole text rows inside frames, CV couldn’t maintain stable anchors.
  • I Data can be manipulated inside InDesign using ExtendScript/JavaScript. I tested triggering a script through CMD using the -runScript parameter. The script runs fine directly from CMD, but I’m unsure whether invoking it from UiPath is stable or recommended.

Any insights, experiences, or recommendations would be really helpful.

we would suggest to try the script invoke via

  • CMD
  • or Powershell
    done with essential UiPath Activities cmd: Invoke Process, Powershell: Invoke Powershell

Also check if current Indesign can use XML Data (approach was done at least in older Indesign versions for catalogue creations) or check out the current capabilities from Indesign on this

1 Like

@s.dineshbabu
Yes, you can automate InDesign with UiPath — but NOT via UI automation.
The only reliable method is using ExtendScript/JavaScript automation triggered from UiPath.

Build 100% of the logic inside ExtendScript.
Use UiPath ONLY to:

Prepare data (Excel/CSV/JSON)
Trigger the script
Wait for PDF output
Move/rename files
Handle downstream workflow

This is the only fully reliable enterprise-grade solution for automating Adobe InDesign.

Use this one-liner from UiPath → Start Process

“C:\Program Files\Adobe\Adobe InDesign 2023\InDesign.exe” -runScript “C:\Scripts\FillTemplate.jsx”

UiPath → Start Process

  • FileName: InDesign.exe
  • Arguments: -runScript “path”

This is stable, because:

  • InDesign handles all script execution internally
  • UiPath only triggers the script (does not depend on UI)

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.