It is that in the actual script. I simply copied the output parameter that filebot was providing. Sorry for the confusion

Current script cmd:

filebot -script fn:amc --action move "G:\***\Complete\TV Shows" --conflict auto -non-strict --log-file "C:\***\Logs\fb-tv-log.txt" --def pushover=*** --def ...

As requested sys info shows:

FileBot 4.8.4 (r5829)
JNA Native: 5.2.2
MediaInfo: 18.05
7-Zip-JBinding: 9.20
Chromaprint: 1.4.2
Extended Attributes: OK
Unicode Filesystem: OK
Script Bundle: 2019-01-16 (r540)
Groovy: 2.5.1
JRE: Java(TM) SE Runtime Environment 10.0.2
JVM: 64-bit Java HotSpot(TM) 64 ...

Changing the inner double quotes to single quotes took care of the ampersand issue. However now the {plex} variable is not working correctly and is being ignored.

Execute: curl.exe -d 'eventType=Manual&filepath=/mnt/unionfs/Media/' http://***:3468/***

Edit : So after reviewing it seems {plex ...

Adding curl.exe does send the correct exec command through. Thanks for that. However the argument is still interrupting at the &. I did also notice that there seems to be spaces inserted around that ampersand when the batch files run.

Saved as:

--def exec="curl.exe -d \"eventType=Manual&filepath ...

Running a cmd to send a curl to an 3rd party tool. Script is written as:

filebot -script fn:amc --action move "***\Complete\Movies" --conflict auto -non-strict --log-file "***\Logs\fb-movies-log.txt" --def pushover=*** --def movieFormat="G:/My Drive/Media/{plex}" --def clean=n --def exec="curl -d ...