ManualTrigger Automate

Target Audience

• Developers: Those who need to automate the backup of workflows to GitHub.
• Project Managers: Individuals managing projects that require regular updates to workflows.
• Data Analysts: Analysts who want to ensure their workflows are safely stored and versioned.
• Automation Enthusiasts: Anyone interested in automating their tasks and improving efficiency.

Problem Solved

This workflow automates the process of backing up n8n workflows to GitHub, ensuring that:

• Workflows are consistently saved with meaningful filenames (e.g., ID.json).
• Users can easily track changes and updates to their workflows over time.
• It reduces the risk of losing important workflow configurations and allows for quick recovery.

Workflow Steps

1. Schedule Trigger: The workflow is triggered at 7 AM daily.
2. Globals Node: Sets up repository details such as repo.owner, repo.name, and repo.path.
3. Get File Data: Fetches existing workflow data from GitHub using the provided repository details.
4. Check File Size: Determines if the fetched file is too large or not.
5. Merge Items: Combines data for further processing.
6. isDiffOrNew: Compares the fetched workflow with the current one to check for differences.
7. Check Status: Evaluates the comparison result:
   • If the file is the same, it does nothing.
   • If the file is different, it prepares to update the existing file.
   • If the file is new, it creates a new file in the repository.
8. Create/Edit File: Based on the status, either a new file is created or an existing file is edited in GitHub.
9. Return: Ends the workflow, confirming the action taken.