Command
RequiredTextAny shell command. Insert values from Shortcuts or an earlier step with {…}.
uptime
Run a shell command on the server and get what it printed.
First, connect SSH in Services. Then open Actions → + → SSH and choose Run Command.
Running or testing this action does something on the computer itself.
Runs the command in the user's login shell, from their home folder, exactly as typed. Output is what the command printed; Error Output is what it printed as errors. A command that ends with a non-zero exit code stops the action, unless Stop on Failure is off — then Exit Code says how it ended.
Open an input to choose its value. Keep a fixed value with Text, receive it from Shortcuts, ask when the action runs, or use an Earlier Step. Read how input sources work.
Any shell command. Insert values from Shortcuts or an earlier step with {…}.
uptime
On, a command that fails stops the action with its message. Off, the action carries on and Exit Code says what happened.
Default: true
In the action editor, open Output → Returned Value to choose fields for your shortcut. These are the response fields described by the app; a service may omit an optional field or return an empty list. JSON File contains the full response.
| Returned field | Type | Meaning |
|---|---|---|
output | string | What the command printed. |
errorOutput | string | What the command printed as errors. |
exitCode | integer | 0 when the command succeeded. |
If the result is unexpected, open Logs in Shortcutify, select the run, and inspect this step’s inputs and response.
On the computer: command, over a signed-in SSH session. No web request is made.
Action identifier: ssh.command.run.v1
No additional per-action permissions are declared in the app’s catalog. The integration’s connection and account access rules still apply.
| Input | Key |
|---|---|
| Command | command |
| Stop on Failure | failOnError |