Backup n8n Workflows with Versioning & Notion Tracking

This workflow automates the backup of n8n workflows from a source instance to a destination 'slave' repository. Inspired by existing solutions, it enhances functionality by prefixing copied workflow names with the current date (e.g., '2025_08_03_PDF Summarizer'), allowing multiple versions for easy tracking and rollback. It fetches workflows via the n8n API, creates prefixed copies on the destination, deletes old versions based on a configurable retention policy, and logs key metrics like execution date and workflow count to a Notion database.

The process includes advanced logic: calculating retention dates by subtracting days from today, limiting operations for safety, and central Notion tracking for audit trails. A rolling retention example keeps 2-3 days of versions, automatically purging older ones to manage storage efficiently.

Benefits include disaster recovery, version control without manual exports, and centralized monitoring. Ideal use cases: development teams syncing prod-to-dev workflows, agencies backing client automations, or solo users maintaining historical versions for debugging. Saves hours of manual copying and reduces risk of data loss.

Setup is straightforward: create a Notion database with specific fields, input API credentials for both n8n instances and Notion, adjust retention days, and test with a low limit.