n8n-nodes-lazyssh

This is an n8n community node for SSH connections with inline credentials, designed for DevOps scenarios where you need to connect to multiple servers dynamically.

Why LazySsh?

The standard n8n SSH node requires credentials to be stored in the credential store. For DevOps scenarios where you need to connect to hundreds of servers back-to-back, this approach is impractical. LazySsh allows you to provide SSH connection parameters (host, port, username, password/key) directly in the node, making it ideal for:

• Bulk server operations
• Dynamic server connections from workflow data
• CI/CD pipelines
• Infrastructure automation

Installation

Follow the installation guide in the n8n community nodes documentation.

Operations

Command Resource

• Execute: Run commands on remote servers

File Resource

• Upload: Upload files to remote servers
• Download: Download files from remote servers

Authentication Methods

• Password: Connect using username and password
• Private Key: Connect using SSH private key (with optional passphrase)

Configuration

All connection parameters are provided directly in the node:

1. Host: Server hostname or IP address
2. Port: SSH port (default: 22)
3. Username: SSH username
4. Authentication: Choose between Password or Private Key
5. Password (if password auth): Server password
6. Private Key (if key auth): SSH private key content
7. Passphrase (if key auth, optional): Private key passphrase

Example Usage

Execute Command on Multiple Servers

You can pass server details from previous nodes and execute commands dynamically:

- Set node with server list
- LazySsh node with expressions:
  - Host: {{$json.server_ip}}
  - Username: {{$json.username}}
  - Password: {{$json.password}}
  - Command: uptime

Upload Files to Remote Server

• Operation: File > Upload
• Provide server credentials inline
• Specify target directory and binary data

Download Files from Remote Server

• Operation: File > Download
• Provide server credentials inline
• Specify file path to download

Security Note

Since credentials are stored directly in the workflow, ensure your n8n instance has appropriate access controls and encryption. Consider using environment variables or secure storage for sensitive credentials.

Resources

• n8n community nodes documentation
• SSH Protocol

Version

0.1.0

License

MIT