Block 1 - Sticky Note 1
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
n8n Self Updater Workflow An automated n8n workflow originally built for DigitalOcean based n8n deployments , but fully compatible with any VPS or cloud hosting (e.g., AWS, Google Cloud, Hetzn...
n8n-nodes-base.stickynote, n8n-nodes-base.scheduletrigger, n8n-nodes-base.if, n8n-nodes-base.ssh, n8n-nodes-base.noop, n8n-nodes-base.emailsend, n8n-nodes-base.httprequest, n8n-nodes-base.set
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Muhammad Anas Farooq.
Original n8n.io source> An automated n8n workflow originally built for DigitalOcean-based n8n deployments, but fully compatible with any VPS or cloud hosting (e.g., AWS, Google Cloud, Hetzner, Linode, etc.) where n8n runs via Docker.
This workflow checks for the latest Docker image of n8n, notifies you via email for approval, and securely updates your n8n instance via SSH once approved.
Trigger: The workflow runs automatically every 3 days at 4 PM UTC (or manually if triggered).
Check Version: It retrieves your current n8n Docker version and image digest via SSH.
Compare: Fetches the remote digest from Docker Hub and compares it with the local one.
Notify via Email: If a new update is available, an approval email is sent with details:
Approval Logic:
Auto Update Execution:
Creates (if missing) a update_docker.sh script on the server.
Runs it in the background (nohup) to:
cd /opt/n8n-docker-caddy
docker compose pull
docker compose down
docker compose up -d
The delay ensures n8n restarts only after workflow completion.
SSH Access to your server (where n8n runs).
SMTP Connection for email notifications.
Configure in Credentials → SMTP.
Fill in:
[email protected]Docker-based n8n Deployment, e.g., n8n-docker-caddy setup.
Docker and docker-compose installed on the server.
Import the Workflow:
Set Up Credentials:
Create two credentials in n8n:
SSH Password → Your server's SSH credentials.SMTP → Your email provider's SMTP credentials.Edit the Email Node:
Replace:
fromEmail: [email protected] → with your email.toEmail: [email protected] → with your desired recipient.Enable Auto Trigger (optional):
Run the Workflow:
update_docker.sh file already exists, it reuses it safely.Author: Muhammad Anas Farooq
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
Showing the first 24 of 27 workflow blocks. Download the JSON for the full node graph.
| Workflow | Self update Docker-based n8n with email approval and SSH |
|---|---|
| Complexity | advanced |
| Nodes | 27 |
| Categories | DevOps |
| Author | Muhammad Anas Farooq |
| Published | 03 Nov 2025 |
Use the JSON export at /data/workflows/10471/10471.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
n8n Self Updater Workflow An automated n8n workflow originally built for DigitalOcean based n8n deployments , but fully compatible with any VPS or cloud hosting (e.g., AWS, Google Cloud, Hetzn...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your DevOps use case.