So there is a chain i want to create and I wonder if this is possible without getting into python scripting :
What is the purpose of Step 2? If it’s simple QuickTime or proxy generation, you could use the Draft integration from the SMTD submitter (see the Integration tab), so no scripting is needed there. However, I think step 3 would require some scripting.
Can I ask what motivates the requirement of not using scripting?
Thanks for your answer.
First of all i forgot to mention that i am mostly talking about stills.
I am not really familiar with Draft as i never used it (because i am doing 95% still images) , i will look into it and maybe it has what i need.
So why i need step 2 is because i can have several scene “presets” made in Nuke and what i want is render output be processed in different preset for different kind of scene. Interior / exterior / morning / evening / night and etc. Each of them will be different preset and i will choose which one to use.
About why i am asking to do that without scripting is just the matter of time. To learn to do this stuff will take certain amount of time and it is actually targeted only for doing this task. If 3dsmax would be Houdini for example , where Python is being used everywhere than yeah , there would be sense to get into it, but in 3dsmax maxscript is enough for my tasks and there is plenty of free scripts around. Well that’s kind of reason.
Am i mistaken and this is much simpler than i am thinking ? 
I think you should be able do all that during the max render submission. But it would mean that you’d need to modify at least the logic part of the submitter (maxscript), probably also the Functions file. We are currently doing something similar with still renders for one of our clients, we just use Fusion for the comp.
Yeah i understand what you want to say , i can submit a Nuke job via maxscript. Actually a good idea. Still thinking about python , how hard it will be to implement something like this
As panze mentioned, you could extend the SMTD script. Or, if your submissions are very consistent, you could create your own submission script that chains the Max, Nuke, and command line jobs together.
An alternative would be to create a Deadline Event script that watches for job submissions and uses some matching criteria to then submit the dependent jobs. There are some examples of various kinds of Event scripts on the Thinkbox GitHub repository.
Whichever approach you decided to take, you can always post questions here if you get stuck.
Thanks a lot James , i will keep this updated , maybe this will be useful for someone else also !
Just to clarify we did it like this, we just used the basic submission scripts as a base. We also have one dedicated event script that is tied to these jobs that does some post render naming and relocating.