Where do shell commands run?

They execute on the computer where the Stream Deck desktop plugin is installed (usually your local machine). You can set a working directory for each command.

Can I run multi-line scripts?

Yes. Save the script to a file and call it from the command field, or use && and ; operators for one-liner chains.

Default is 30 seconds (30000ms). You can raise this in the action settings if your script takes longer.

What if a command fails?

The non-zero exit code triggers failure routing in your workflow. You can add a retry, fallback, or alert node after the shell action.

Are shell actions safe?

Commands run with the same permissions as the Stream Deck desktop app. Avoid destructive operations, and review generated workflows before saving.

Shell + Stream Deck

System · 4 actions

Execute shell commands on the local system. Trigger Shell actions from your Stream Deck with a single button press and configure any required fields in the workflow builder.

Build a Shell workflow — free See how it works

No code
Free tier
One Stream Deck press
Pairs with OBS & Elgato tools
OAuth & keys handled in-builder

Triggers & actions

Steps your workflow can perform in Shell.

Execute Command

Run a shell command and capture its output.

Run Command

Run a shell command and capture its output (alias for execute_command).

Open URL

Open a URL in the default browser.

Press Keyboard Shortcut

Simulate pressing a keyboard shortcut.

Use cases

Run build scripts from your desk

Trigger long-running build, test, or deploy scripts with one Stream Deck button — no need to switch to a terminal window.

Automate macOS and Windows shortcuts

Run AppleScript, PowerShell, or Bash snippets directly from your Stream Deck to control system-level tasks.

Chain commands with workflow logic

Use Conductor Deck conditions to run different shell commands based on the output of earlier steps.

Surface custom output on Stream Deck buttons

Capture stdout and stderr from any command, then feed results into later workflow nodes — including dynamic button labels.

How to connect

Sign up for free

Create your Conductor Deck account — no credit card required.

Open the workflow builder

Start a new workflow and choose Shell from the built-in tools. There is no OAuth connection or separate app authorization step.

Build a workflow

Add a Shell action to your visual workflow canvas. Configure the options you need, then connect it to other steps.

Assign to Stream Deck

Sync your workflow to any Stream Deck button. Press once to trigger the entire sequence.

Frequently asked questions

Where do shell commands run?: They execute on the computer where the Stream Deck desktop plugin is installed (usually your local machine). You can set a working directory for each command.
Can I run multi-line scripts?: Yes. Save the script to a file and call it from the command field, or use && and ; operators for one-liner chains.
Is there a timeout?: Default is 30 seconds (30000ms). You can raise this in the action settings if your script takes longer.
What if a command fails?: The non-zero exit code triggers failure routing in your workflow. You can add a retry, fallback, or alert node after the shell action.
Are shell actions safe?: Commands run with the same permissions as the Stream Deck desktop app. Avoid destructive operations, and review generated workflows before saving.

Automate Shell with your Stream Deck

Get started free View pricing

Related System integrations