Automatic Squarespace Code Injection Backup to GitHub - n8n Workflow

Squarespace developers and designers who rely on custom code injections.
Users needing version control for critical website configurations.
Anyone looking for reliable, automated disaster recovery for their website code.
n8n power users seeking advanced examples of using the n8n node framework with custom scripting.

Maintaining custom code injections in platforms like Squarespace is critical, but these changes often lack native version control, posing a risk during updates or site migration. This powerful n8n workflow solves this problem by providing a scheduled, automated backup solution straight to GitHub. This specific n8n template uses HTTP requests to pull the relevant code, and custom n8n node scripting (Cheerio) to meticulously clean the HTML data, ensuring only your injected code, not the platform's boilerplate, is saved. By setting up this n8n workflow, you gain peace of mind knowing your custom headers and footers are safely stored and version-controlled every two hours via a reliable n8n trigger.

This automation begins with a scheduled n8n trigger, configured to run every two hours. Alternatively, it can be run manually via the 'On clicking execute' n8n node.

1. Data Retrieval: The Get Squarespace data n8n node (an HTTP Request) queries the specified Squarespace URL using the page-context format to retrieve the current site configuration, including header and footer injection points.


2. Data Separation & Metadata: The data is split into two streams: one for headers and one for footers, using 'Set' n8n nodes (Get Header Injection and Get Footer Injection). These nodes also extract and set important metadata like the domain name and a timestamp.


3. Code Cleanup: The Clean up Footers and Clean up Headers n8n node utilize custom JavaScript with Cheerio to strip away standard Squarespace framework elements, leaving only the truly custom injected code.


4. Preparation for GitHub: The Merge Injections n8n node recombines the two cleaned items (header data and footer data). The Globals n8n node then applies the user-defined GitHub repository settings (owner, name, path).


5. GitHub Storage: The Loop Over Items n8n node processes the header and footer data individually. The first GitHub n8n node (Edit Injection data) attempts to update the existing file. If this action fails (which happens if the file doesn't exist yet, indicated by the If n8n node checking for a 'not found' error), the flow moves to the Create Injection data n8n node, ensuring the file is created for the first time. This conditional logic guarantees either an update or a creation, maintaining a consistent backup history.

To deploy this n8n workflow effectively, follow these steps:

1. Import: Copy the provided n8n workflow JSON and paste it into your n8n instance.


2. Squarespace URL: Locate the Get Squarespace data n8n node and update the URL parameter to the primary domain of your Squarespace site.


3. GitHub Credentials: Configure the GitHub API credential required by the Edit Injection data and Create Injection data n8n nodes. This requires a Personal Access Token with repository write permissions.


4. Define Repository Path: Open the Globals n8n node and update the following settings:

1. Activate: Ensure the Schedule Trigger n8n trigger is active to enable automatic backups.

This advanced n8n workflow relies on several specific n8n node types:

Schedule Trigger: Serves as the primary n8n trigger, initiating the backup process every two hours. Highly reliable n8n node for recurring tasks.
HTTP Request (Get Squarespace data): Fetches the raw Squarespace page context data. Key configuration: Uses the ?format=page-context query parameter.
Set (Get Header/Footer Injection & Globals): Used primarily for data manipulation. The Injection nodes extract the raw content and create supporting metadata (ID, domain). The Globals n8n node centralizes the GitHub configuration details.
Code (Clean up Footers/Headers): Critical for data hygiene. These custom scripting n8n node implementations use the cheerio library to parse the HTML and remove boilerplate code added by Squarespace, isolating only the custom injected code.
Merge: Combines the separate header and footer data streams back into a single input stream for subsequent processing.
Loop Over Items (Split In Batches): Ensures that the header file and footer file are processed sequentially and independently by the GitHub n8n node.

• GitHub (Edit/Create Injection data): Handles the actual storage. The Edit operation attempts to update the file; if it fails, the If n8n node directs execution to the Create operation, facilitating seamless version control within the GitHub repository.