ManualTrigger Automate

ManualTrigger Automate streamlines your workflow by automatically backing up credentials to GitHub every two hours. It checks for file changes, creating new files or editing existing ones as needed, ensuring your data is always up-to-date and securely stored. This automation reduces manual effort and enhances data integrity.

7/8/2025
24 nodes
Complex
schedulecomplexsticky notenoopgithubsplitinbatchesschedule triggerexecutecommandexecuteworkflowexecuteworkflowtriggerautomationadvancedapiintegrationlogicconditionalroutingcron
Categories:
Schedule TriggeredComplex WorkflowTechnical Infrastructure & DevOpsBusiness Process Automation
Integrations:
Sticky NoteNoOpGitHubSplitInBatchesSchedule TriggerExecuteCommandExecuteWorkflowExecuteWorkflowTrigger

Target Audience

  • Developers looking to automate their GitHub workflows.
    - Data Engineers needing to backup and manage credentials efficiently.
    - Project Managers who want to ensure version control for their project files.
    - DevOps Engineers aiming to streamline deployment processes with automated backups.

    • Problem Solved

    This workflow addresses the challenge of maintaining up-to-date backups of credentials in GitHub, ensuring that any changes are tracked and managed effectively. It eliminates the risk of losing important configuration data and provides a systematic way to handle file versions, whether they are new, unchanged, or modified.

    Workflow Steps

  • Schedule Trigger: The workflow is initiated every 2 hours to ensure regular backups.
    2. Execute Command: It runs a command to export all credentials in a decrypted format, ensuring sensitive information is captured correctly.
    3. JSON Formatting: The output from the command is processed to ensure it is in a valid JSON format.
    4. Loop Over Items: Each credential is processed individually to handle them effectively.
    5. Get File Data: For each credential, the workflow checks if a corresponding backup file exists in GitHub.
    6. If File Too Large: If the file is too large, it handles the situation accordingly.
    7. Merge Items: The workflow merges the data from the exported credentials with existing files.
    8. Check Status: It determines if the file is the same, different, or new compared to the existing backup.
    9. Create/Edit File: Depending on the status, it either creates a new file or edits the existing one in GitHub.
    10. Return: Finally, it concludes the workflow, marking the operation as complete.

    • Customization Guide

  • Changing the Schedule: Modify the Schedule Trigger parameters to adjust how frequently the workflow runs.
    - Updating Repository Information: In the Globals node, update the repo.owner, repo.name, and repo.path to reflect your GitHub repository details.
    - Customizing File Handling: Adjust the logic in the isDiffOrNew and Check Status nodes to change how file differences are handled based on your specific requirements.
    - Adding New Nodes: Incorporate additional nodes for further processing or notifications, such as sending alerts via email or messaging platforms when a file is changed.