🛠️ Auto n8n updater (Docker)
Keep your self-hosted automation engine current without the manual overhead of tracking releases. This intelligent assistant monitors Docker Hub, uses AI to summarize GitHub release notes, and lets you trigger seamless updates directly through a Telegram approval bot. It’s the ultimate 'set and forget' solution for maintaining a cutting-edge n8n instance.
Start BuildingWhat This Recipe Does
This IT Operations automation provides a robust monitoring and incident response framework for your critical server infrastructure. By combining scheduled health checks with remote server execution, the workflow proactively identifies system performance issues, service outages, or security anomalies before they impact your business operations. Instead of manually checking logs or relying on complex monitoring suites, this automation executes secure commands directly on your infrastructure and processes the results in real-time. If an issue is detected, the system filters out redundant alerts and instantly notifies your team via Telegram, ensuring that technical staff can respond to critical events immediately. This reduces downtime, improves system reliability, and allows your IT team to focus on strategic improvements rather than constant manual oversight. It bridges the gap between raw server data and actionable communication, transforming technical logs into clear, timely updates for your operations team.
What You'll Get
Forms, dashboards, and UI components ready to use
Background automations that run on your schedule
REST APIs for external integrations
SSH (key-based auth), DaySchedule, Telegram configured and ready
How It Works
- 1
Click "Start Building" and connect your accounts
Runwork will guide you through connecting SSH (key-based auth) and DaySchedule
- 2
Describe any customizations you need
The AI will adapt the recipe to your specific requirements
- 3
Preview, test, and deploy
Your app is ready to use in minutes, not weeks
Who Uses This
- System Administrators who need real-time alerts on server health and disk space usage without checking dashboards.
- DevOps teams monitoring application uptime and service status across multiple remote environments.
- IT Managers who want to receive instant security or performance notifications directly on their mobile devices via Telegram.
Frequently Asked Questions
What kind of server checks can this automation perform?
The automation uses secure SSH commands, meaning it can check anything your server can report, including CPU load, memory usage, service status, or specific log entries.
How does the duplicate filtering work?
The workflow includes a logic step that identifies if an issue has already been reported. This prevents your team from being flooded with repetitive notifications for the same ongoing incident.
Do I need to install software on my servers?
No additional software is required on your servers. The automation connects via standard SSH protocols to execute checks and retrieve status updates securely.
Can I adjust how often the checks occur?
Yes, the schedule trigger is fully customizable. You can run checks every minute for critical systems or once a day for routine maintenance reports.
Importing from n8n?
This recipe uses nodes like Set, Ssh, HttpRequest, If and 6 more. With Runwork, you don't need to learn n8n's workflow syntax. Just describe what you want in plain English.
Based on n8n community workflow. View original
Related Recipes
Incident response workflow - Part 3
This IT Operations automation serves as a centralized incident command center, bridging the gap between detection, documentation, and communication. In the high-stakes environment of system outages or critical bugs, manual coordination often leads to delays and fragmented information. This solution synchronizes PagerDuty, Jira, and Mattermost to ensure your technical teams and stakeholders remain perfectly aligned. When a critical issue arises, a single action triggers a coordinated response: it logs a structured ticket in Jira for long-term tracking, alerts the relevant team members in Mattermost for immediate collaboration, and updates PagerDuty to reflect the current status. By automating these repetitive administrative tasks, your senior engineers can focus entirely on technical resolution rather than updating multiple dashboards. The result is a significant reduction in mean time to resolution and a more transparent communication loop for the entire organization. This automation transforms a chaotic incident response into a streamlined, repeatable process that protects your service level agreements and maintains customer trust.
Incident response workflow - Part 3
This incident response automation bridges the gap between alert detection and team resolution. By connecting PagerDuty, Jira, and Mattermost, it ensures that critical system issues are never missed and are handled with a standardized process. When an incident is triggered, the automation instantly creates a documented trail in Jira for tracking and compliance while simultaneously alerting the relevant team members in Mattermost. This eliminates the manual effort of duplicating information across different platforms and ensures that communication remains centralized. The result is a significant reduction in mean time to resolution and improved visibility for stakeholders. Organizations can maintain higher service availability by replacing chaotic manual coordination with a structured, automated workflow that keeps technical teams focused on solving the problem rather than managing the tools.
Set DevOps infrastructure with Docker, K3s, Jenkins & Grafana for Linux servers
Setting up a reliable DevOps environment manually is a time-consuming process often prone to human error. This automation transforms your Linux server into a fully functional infrastructure in seconds, eliminating the need for complex command-line interactions or manual script execution. By standardizing the deployment process, your team can focus on building products rather than managing servers. This workflow handles the heavy lifting of environment configuration, ensuring that every server is set up identically and according to best practices. For business leaders, this means a significant reduction in technical debt and faster deployment cycles. Whether you are launching a new project or scaling existing services, this automation provides a stable foundation that scales with your growth. It bridges the gap between raw hardware and a production-ready environment, allowing non-technical stakeholders to initiate infrastructure builds with total confidence. By removing the technical barriers to server management, your organization achieves greater agility and operational consistency.
Set DevOps infrastructure with Docker, K3s, Jenkins & Grafana for Linux servers
Setting up a production-ready DevOps environment manually is a time-consuming process prone to human error and configuration drift. This automation eliminates the technical bottleneck by deploying a complete DevOps infrastructure on any Linux server in seconds. By standardizing the environment setup, your team ensures consistency across development, staging, and production tiers. This workflow handles the heavy lifting of server preparation, software installation, and environment configuration through a secure SSH interface. For business owners and IT managers, this means faster time-to-market for new applications and a significant reduction in engineering overhead. Instead of spending hours running manual commands and troubleshooting dependencies, your technical team can focus on building core product features while the infrastructure handles itself. It transforms a complex series of IT tasks into a single-click operation, providing a reliable foundation for all your software deployment needs.
Ready to build this?
Start with this recipe and customize it to your needs.
Start Building Now