Backup Squarespace code Injections to Github

This workflow is designed for:

• Web Developers who manage Squarespace sites and need to backup header and footer code injections to GitHub regularly.
• Digital Marketers who require a systematic way to archive website changes for compliance or record-keeping.
• Small Business Owners using Squarespace, providing them a safety net for their website customizations.
• Technical Teams looking for automation in their development workflow, ensuring that all changes are tracked and stored efficiently.

This workflow addresses the challenge of managing and backing up Squarespace code injections. It automates the process of fetching header and footer injections from a Squarespace site and storing them in a GitHub repository. This ensures that users:

• Avoid data loss by regularly saving their custom code.
• Maintain version control, allowing them to revert to previous versions of their code if needed.
• Streamline updates to their website by having a reliable backup system in place.

1. Triggering the Workflow: The workflow can be initiated either manually by clicking 'execute' or automatically every 2 hours via a scheduled trigger.
2. Fetching Squarespace Data: The workflow retrieves the site's header and footer injections using an HTTP request to the Squarespace URL.
3. Cleaning Up the Data: The fetched data is then processed:
   • Clean up Footers: Unwanted elements are removed from the footer data to ensure only relevant information is stored.
   • Clean up Headers: Similar cleaning is performed on the header data, ensuring that only necessary code remains.
4. Merging Injections: The cleaned header and footer data are merged into a single output for further processing.
5. Looping Over Items: The workflow processes the merged data in batches of 2 to manage multiple injections efficiently.
6. Setting Global Variables: Global variables for GitHub repository details are set, including owner, name, and path.
7. Creating or Editing Injection Data: Depending on whether the injection data already exists, the workflow either creates new files or edits existing ones in the GitHub repository, with appropriate commit messages indicating the backup time.