Automated Purging of n8n Execution History in MySQL

Overview

This workflow automates the removal of old n8n execution history records from a MySQL database, ensuring optimal database performance and efficient storage management.

Key Features

• Scheduled Cleanup: Utilizes a cron node to trigger the purge process at defined intervals.
• Manual Execution: Allows on-demand purging via a manual trigger for immediate cleanup needs.
• Database Integration: Connects directly to MySQL to execute deletion queries targeting execution history tables.

Benefits

• Improved Performance: Prevents database slowdowns by regularly removing obsolete execution data.
• Reduced Maintenance: Minimizes manual intervention, saving time and reducing human error.
• Scalable Solution: Supports both scheduled and ad-hoc purging, adaptable to varying operational needs.

Use Cases

• Organizations running n8n with MySQL backends seeking to automate routine maintenance.
• Teams aiming to comply with data retention policies by regularly clearing outdated workflow logs.
• Businesses looking to optimize infrastructure costs by managing database size proactively.

Integrations & Processes

• n8n: Orchestrates the workflow and triggers.
• MySQL: Stores and purges execution history data.
• Cron: Schedules automated purging tasks.

Automation Benefits

This workflow streamlines database maintenance, reduces manual workload, and ensures n8n environments remain efficient and compliant.