SSH Command Node

The SSH Command node executes commands on remote servers over SSH. It supports multiple sequential steps, password or private-key authentication, file upload/download, and output capture.

Overview

Connection

Using Saved Credentials (Recommended)

Select an SSH credential in the Credential field.

Manual Configuration

Authentication Methods

Configuration

Global Timeout

SSH Steps

The node supports multiple steps executed sequentially in the same SSH connection. Use + Add step to include commands, file uploads, and downloads.

All steps run in the same SSH session. Commands like cd /my/folder affect following steps when they use Current folder.

Command Step

Send File Step

With Destination = Current folder, QANode sends the file to the current SSH shell directory. This enables:

Step 1: cd /opt/my-app/uploads
Step 2: Send file → Destination: Current folder

With Destination = Remote path, provide the path directly. If it ends with /, the file is saved inside that folder.

Download File Step

If the extension is omitted from the remote path, QANode tries to resolve the file by name in the remote folder. For example, /tmp/data can find /tmp/data.csv when that file exists on the server.

The MIME type is inferred automatically from content and filename.

Wait for Match

Wait for Match lets a command step wait until specific text appears in the output. Useful for:

• waiting for services to start;
• waiting for interactive prompts;
• confirming that an operation completed.

Example:

Command: systemctl restart nginx
Wait for Match: true
Match String: "Active: active (running)"
Timeout: 10000

Outputs

Accessing Outputs

// Full output
{{ steps.ssh.outputs.stdout }}

// Exit code
{{ steps.ssh.outputs.exitCode }}

// Specific command result
{{ steps.ssh.outputs.commands[0].stdout }}
{{ steps.ssh.outputs.commands[0].exitCode }}

// Downloaded file by variable name
{{ steps.ssh.outputs.files.report }}

// Shortcut to the last downloaded file
{{ steps.ssh.outputs.fileRef }}

Practical Examples

Check service status

Step 1:
  Label: Check Nginx
  Command: systemctl status nginx

Application deploy

Step 1:
  Label: Go to directory
  Command: cd /opt/my-app

Step 2:
  Label: Pull repository
  Command: git pull origin main

Step 3:
  Label: Install dependencies
  Command: npm install --production

Step 4:
  Label: Restart service
  Command: pm2 restart my-app
  Wait for Match: true
  Match String: "online"

Send and download files in the current folder

Step 1:
  Label: Enter folder
  Command: cd /root/tests

Step 2:
  Label: Send data
  Type: Send file
  File: {{ steps["file-generate"].outputs.fileRef }}
  Destination: Current folder
  Keep file name: true

Step 3:
  Label: Download result
  Type: Download file
  Source: Current folder
  File name: result.csv
  Variable name: result

After the download:

{{ steps.ssh.outputs.files.result }}
{{ steps.ssh.outputs.fileInfo.result.name }}

Flow with Validation

[SSH Command: "deploy"]
    │
    ▼
[If: {{ steps.ssh.outputs.exitCode }} === 0]
    │ true → [HTTP Request: GET /health-check]
    │            │
    │            ▼
    │         [Assert: status === 200]
    │
    │ false → [Log: "Deploy failed: {{ steps.ssh.outputs.stderr }}"]
              → [Stop and Fail]

Tips

• Use saved credentials to avoid exposing passwords/keys in flows.
• Check exitCode: 0 indicates success, other values indicate errors.
• Use expressions in commands: echo "Deploy to {{ variables.ENVIRONMENT }}".
• Wait for Match is essential for long-running commands such as restarts and builds.
• All steps run in the same SSH session, so the working directory is preserved between steps.
• Use Current folder when a previous command already positioned the shell in the correct directory.
• Use Remote path when you want to be explicit and independent from a previous cd.
• For downloads, prefer clear Variable names, such as report, data, or evidence.
• Commands with {{ }} are evaluated before execution.