Skip to main content

Automated server log cleanup via email alerts with SSH - Nginx, Docker, System

Workflow preview

Workflow preview
100%
Automated server log cleanup via email alerts with SSH - Nginx, Docker, System preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

This n8n workflow monitors email alerts for disk utilization exceeding 80%, extracts the server IP, logs into the server, and purges logs from Nginx, PM2, Docker, and system files to clear disk spa...

Best for

  • DevOps automation workflows
  • intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.emailreadimap, n8n-nodes-base.code, n8n-nodes-base.set, n8n-nodes-base.ssh, n8n-nodes-base.stickynote

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Oneclick AI Squad.

Original n8n.io source

1.1 Workflow description

Title
Automated server log cleanup via email alerts with SSH - Nginx, Docker, System
Workflow name
Automated server log cleanup via email alerts with SSH - Nginx, Docker, System

This n8n workflow monitors email alerts for disk utilization exceeding 80%, extracts the server IP, logs into the server, and purges logs from Nginx, PM2, Docker, and system files to clear disk space.

Key Insights

  • Ensure email alerts are consistently formatted with server IP details.
  • SSH access must be properly configured to avoid authentication failures.

Workflow Process

  1. Initiate the workflow with the Check Disk Alert Emails node when an email triggers on high disk usage.
  2. Parse the email to extract the server IP using the Extract Server IP from Email node.
  3. Set up SSH credentials and paths manually with the Prepare SSH Variables node.
  4. Execute cleanup commands to delete logs from Nginx, PM2, Docker, and system files using the Run LogCleanup Commands via SSH node.

Usage Guide

  • Import the workflow into n8n and configure email and SSH credentials.
  • Test with a sample email alert to verify IP extraction and log deletion.

Prerequisites

  • Email service (e.g., IMAP or API) for alert monitoring
  • SSH access with valid credentials

Customization Options

Modify the Prepare SSH Variables node to target specific log directories or adjust cleanup commands for different server setups.

1.2 Logical Blocks

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.

2. Block-by-Block Analysis

Block 1 - Check Disk Alert Emails

Type / Role
n8n-nodes-base.emailReadImap - emailReadImap
Config choices
Version 2

Block 2 - Extract Server IP from Email

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 3 - Prepare SSH Variables

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 4 - Run Log Cleanup Commands via SSH

Type / Role
n8n-nodes-base.ssh - ssh
Config choices
Version 1

Block 5 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 6 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 7 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 8 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

3. Summary Table

Workflow Automated server log cleanup via email alerts with SSH - Nginx, Docker, System
Complexity intermediate
Nodes 8
Categories DevOps
Author Oneclick AI Squad
Published 27 Jun 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/5406/5406.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

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.

Frequently asked questions

What does Automated server log cleanup via email alerts with SSH - Nginx, Docker, System do?

This n8n workflow monitors email alerts for disk utilization exceeding 80%, extracts the server IP, logs into the server, and purges logs from Nginx, PM2, Docker, and system files to clear disk spa...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

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.