This article will explain how you can create a custom render Action and introduce you to AppleScript.  

Say, for instance, you want an Action that will always render a 16-bit 44.1kHZ AIFF file and uses the Goodhertz SRC with your preferred settings. With Triumph, you can run through your workflow once and combine these steps into a single Action.  

I'm starting with an 88.2kHZ file. It's been normalized and a dither 'effect' has been applied, so now I'm ready to render my file to 16-bit 44.1kHz.

I'll go to File > Render.

Then select my output format options.

On the last pane, I can either render the audio and keep it inside of my project, or I can go ahead and save it somewhere else. It's at this point that I realize I'm tired of selecting all of the options over and over again, so I think I'll make an Action that does both of these things.

The first Action will save the render inside of the project, but the second will always save it to my desktop...for now.

To create the Action, I can just click Create Custom Action. The Action will then be added to my Actions List under the Custom heading with a generic name. I can change it later, though.

I want to see what this Action really looks like, so I click the disclosure triangle to open the popover.

Here I can change the Action's name, add a keyboard shortcut, and even edit the Action script.

The first thing I anticipate is getting tired of changing the name of the render after the fact, so why not give it a name when I run the Action? I need to present a dialog, enter some text and return it to the Action script. Fortunately, I can do that by adding one line.

Underneath the line that reads 'tell front document,' I'll add this:

set renderName to text returned of (display dialog "Name this Render:" default answer "My Render" buttons {"OK"} default button 1)

'renderName' is the container or variable for the text. I can name this variable anything I want. 

'display dialog' generates a text box and a single 'OK' button. I can also return which button is pressed, but that's not important. I want whatever is typed sent back, so I set 'renderName' to the 'text returned' from my dialog box.

But, that doesn't change the name of the render when I run the Action - it just gets the name from me. In order to set the name, I need to make one modifcation to the 'render' process portion of the script. I'll replace the static text, "My Render", with renderName, which contains the text I've typed.

That's one completed script. I'm going to modify my second Action to ask me where I want to save it, instead of always saving it to the Desktop.

Woah, what are all of those numbers and letters? Turns out that it's a secure connection between Triumph and the folder that I selected when I originally created the Action - my Desktop, in this case. I can ignore all of that since I want this Action to ask me where to save.

I can replace everything between save aRender in and end tell with choose folder. 

'choose folder' will present a Finder window where I can navigate to the save location of my choice.

 It would be a good idea for me to add the modifications from the first script, too, since it's a pretty handy addition.

Now I have two completed custom Actions: One will render the workspace with my preferred settings and allow me to name the render beforehand. The second will do all of that and then ask me where to save it outside of the project.