Skip to main content

Keyboard Shortcuts and Remote Triggers

This workflow is for simple, repeatable triggers from outside the panel.

Use it when you want to start a saved Automation Agent for Adobe Premiere script from:

The basic idea is simple:

  1. save a reusable script in your Automation Agent library
  2. open that script in the Library panel
  3. copy its Remote Execution URL from the details view
  4. use that URL in your external trigger tool

What This Is Good For​

This is a good fit when you already know which automation you want to run and just want a fast trigger.

Typical examples:

  • start a recurring project cleanup script from a shortcut
  • run an import helper from Stream Deck
  • launch a utility script from Touch Portal
  • trigger a script and then answer a follow-up dialog inside Premiere if needed

What This Is Not​

This is not the same as the MCP workflow.

Use remote triggers when you want:

  • one saved script
  • one predictable action
  • one local URL that another tool can call

Use MCP when you want:

  • an agent to inspect the current project state
  • multi-step decision making
  • open-ended task execution in the active project

How To Use It​

  1. Save the script in the Library.
  2. Select it in the Library panel.
  3. In the details view, open Remote Execution.
  4. Copy the generated local URL.
  5. Paste that URL into your shortcut or button tool.

When that URL is opened, the saved script runs automatically.

The URL always points to the saved library entry, not to whatever is currently open in the editor.

Requirements​

Remote triggers are available when the local Automation Agent helper is running.

The generated URL is local to your machine and uses 127.0.0.1, so the trigger tool needs to run on that same machine.

Important Behavior​

The saved script is the source of truth​

Remote triggering always runs the saved library version of the script.

If the editor currently contains unsaved changes, those are not part of the remote run.

Renaming or moving the script changes the URL​

The URL is derived from the current library location of the script.

If you rename or move the script inside your library, copy the new URL again in the Library details panel and update it in your trigger tool.

Scripts may still ask for user input​

Remote triggering does not mean fully headless execution.

A saved script may still:

  • show dialogs
  • ask for files or folders
  • require additional confirmation or interaction

That is often useful. For example, you can trigger a script from a shortcut and then answer a small follow-up prompt in the normal Premiere workflow.

Any tool that can open a local URL or run a small HTTP GET request can trigger Automation Agent scripts.

AutoHotkey on Windows​

AutoHotkey is a very practical choice when you want a normal keyboard shortcut on Windows.

  1. Install AutoHotkey.
  2. Create a new .ahk file.
  3. Paste a script like this and replace YOUR_REMOTE_EXECUTION_URL with the copied Library URL. In this example, F11:: means that pressing the F11 key triggers the request:
F11::
{
    url := "YOUR_REMOTE_EXECUTION_URL"
    whr := ComObject("WinHttp.WinHttpRequest.5.1")
    whr.Open("GET", url, false)
    whr.Send()
}
  1. Run that .ahk file.
  2. Press the shortcut to launch the script.

If you only want the shortcut while Premiere has focus, use a version like this instead:

F11::
{
    if WinActive("Premiere")
    {
        url := "YOUR_REMOTE_EXECUTION_URL"
        whr := ComObject("WinHttp.WinHttpRequest.5.1")
        whr.Open("GET", url, false)
        whr.Send()
    }
}

That way, pressing F11 only triggers the request while Premiere is the active window.

If that does not work on your machine, replace "Premiere" with the exact window title shown by your installed version. Depending on version, language, or OS integration, that may still be something like "Premiere Pro".

Shortcuts on macOS​

Shortcuts is the best built-in Mac option if you want a modern Apple-native setup without installing extra tools.

  1. Open the Shortcuts app and create a new shortcut.
  2. Add a URL action and paste the copied Library URL.
  3. Add a Get Contents of URL action so the shortcut sends the local HTTP request.
  4. Open the shortcut details and add a keyboard shortcut.

This gives you a simple built-in Mac trigger that works well for launching one saved script from a hotkey.

Note that a keyboard shortcut assigned in Shortcuts is a global macOS shortcut, not a Premiere-only shortcut. If you want the trigger to be active only while Premiere has focus, use Keyboard Maestro or another app-specific hotkey tool instead.

If you prefer the older built-in workflow, Automator still works too: create a Quick Action, add Run Shell Script, and call the same URL with curl "YOUR_REMOTE_EXECUTION_URL".

Keyboard Maestro on macOS​

Keyboard Maestro is the most direct Mac option when you want a reliable hotkey, app-specific activation, and richer automation later.

  1. Create a new macro.
  2. Add a Hot Key trigger.
  3. Add a Get URL action and paste the copied Library URL.
  4. Optionally put the macro into a Macro Group that is active only in Premiere.

This setup is a good fit when you want a Mac shortcut that stays neatly scoped to Premiere instead of being global all the time.

Stream Deck​

Stream Deck works well when you want a dedicated hardware button for one script.

  1. Create a new button action.
  2. Use the action that opens a website or URL.
  3. Paste the copied Library URL.
  4. If your Stream Deck setup offers a background GET option, enable it so the request runs silently instead of opening a visible browser tab.

This is especially useful for cleanup scripts, import helpers, or recurring utility actions you want on one physical key.

Touch Portal​

Touch Portal is a good fit when you want the same kind of trigger button on a phone or tablet.

  1. Create a button.
  2. Add an HTTP Get action.
  3. Paste the copied Library URL.

Touch Portal example

This gives you a simple remote control surface for repetitive editing actions without needing extra hardware.

Raycast, Alfred, and similar launcher tools​

Launcher tools such as Raycast and Alfred are also a good fit.

In practice, you usually create one of these:

  • a quicklink that opens the copied local URL
  • a small shell-command action that runs curl "YOUR_REMOTE_EXECUTION_URL"
  • a hotkey that triggers one of those actions

That gives you a very lightweight keyboard-driven setup without needing a full macro package.