ManualTrigger Automate

Who should use this workflow

• Developers looking to automate backups of their workflows to GitHub.
• Project Managers who want to ensure that their workflows are regularly saved and versioned.
• Teams that require a reliable method to track changes in their automation scripts.
• GitHub Users who manage multiple workflows and need an efficient way to maintain them.

What problem does this workflow solve

• Automates the backup of n8n workflows to GitHub, ensuring that no changes are lost and previous versions can be accessed.
• Reduces the risk of manual errors associated with saving files, providing a systematic approach to version control.
• Helps in maintaining a history of workflow changes, making it easier to revert to previous versions if needed.

Detailed explanation of the workflow process

1. Trigger: The workflow can be triggered manually or scheduled to run every 2 hours.
2. Get File Data: It retrieves the existing workflow data from GitHub using the provided repository details.
3. Check File Size: It checks if the file is too large or if there are errors in the retrieval process.
4. Merge Items: Combines retrieved data with new workflow data for comparison.
5. Compare Workflows: A JavaScript function determines if the retrieved workflow is the same, different, or new.
6. Conditional Logic: Based on the comparison, the workflow will either do nothing, create a new file, or edit an existing file on GitHub.
7. File Operations: If the file is new, it creates a new file in the specified GitHub repository. If the file is different, it edits the existing file with the updated content.
8. Return Status: Finally, it returns a status indicating the success of the operation.