The action Execute program/script

Purpose

Launches an external program or script from the scenario and passes command parameters (arguments). Use it to trigger helper utilities, custom processors, or any external automation that must run when a file is processed.

Where to add

Place this action at the point you need to start an external tool (after conversion, before/after notifications, etc.). The action launches the program/script for the current pipeline item.

Main fields

• Program or script
  Full path to the executable or interpreter you want to start (example: C:\Tools\processor.exe or C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe).
• Command parameters
  The arguments to pass to the program. Use the Fields button to insert field (filename, metadata) so parameters are dynamic for each processed file.

Important behavior notes and limitations

• Detached / asynchronous launch
  The action starts the external process and does not wait for it to finish. It will not receive the program’s exit code, output (stdout/stderr) or completion status.
  Because the action does not wait, downstream actions in the scenario will execute immediately after the process is launched unless you add explicit synchronization (see suggestions below).
• No result capture
  The action cannot capture or parse program output.

Best practices and tips

• Use full absolute paths for both the Program and any files referenced in parameters. Do not rely on relative paths or mapped drive letters when the scenario runs as a service — prefer UNC paths for network shares.
• Quote arguments containing spaces: wrap tokens and paths in double quotes: "%FILE_PATH%" or "/out:\"C:\My Folder\%FILENAME_FULL%\"".
• If you are calling a script, launch it via the interpreter and pass the script path as an argument (e.g., powershell.exe -File "C:\Scripts\do-work.ps1" "%FILE_PATH%").
• When running under a service account:
  Ensure the account has permissions to execute the program and access any file system or network resources used by the program.

Summary

Use this action to start external programs or scripts with arguments. It launches the process asynchronously (does not wait) and does not receive output or exit codes. Provide absolute paths, quote arguments, secure credentials, and add explicit synchronization in the scenario if you must wait for the external task to finish.