Automatic Squarespace Order Fulfillment Process - n8n Workflow

Squarespace store owners who sell digital products or gift cards.
Businesses using external fulfillment services and need immediate API confirmation.
Developers seeking reliable n8n templates for e-commerce API integration.
Automation specialists looking to manage high volumes of Squarespace orders efficiently using an n8n workflow.

Managing order fulfillment manually can be time-consuming, especially for stores dealing with digital goods or relying on automated drop-shipping services. This robust n8n workflow solves that problem by providing a scheduled, autonomous system for processing pending orders. It utilizes the Squarespace Commerce API to fetch only PENDING orders, applies a crucial time-based filter (only processing orders older than 24 hours to ensure payment settling), and then executes the fulfillment action. This entire process, managed within an n8n instance, ensures that customers receive their fulfillment notification quickly and reliably, saving significant operational time and increasing customer satisfaction. This comprehensive n8n node structure is a perfect example of efficient commerce automation.

This automation can be started either manually via the 'On clicking 'execute'' n8n trigger or automatically on a schedule via the 'Schedule Trigger' n8n node.

1. Configuration (Globals): The flow starts by initializing global variables using the Set n8n node, defining the required Squarespace API version and setting the fulfillmentStatus to PENDING. It also sets maxPage to -1 to enable infinite pagination.


2. Query Orders (HTTP Request): The 'Query pending Orders' n8n node sends a complex HTTP Request to the Squarespace Orders API. It utilizes the parameters set in the Globals node and handles API-based pagination automatically, ensuring all pending orders are retrieved.


3. Data Separation (Split Out Order): The resulting batch of orders is split into individual items using the 'Split Out Order' n8n node, allowing subsequent nodes to process each order independently.


4. Filtering (Filter Orders): A safety check is applied here. The 'Filter Orders' n8n node only allows orders that were created more than 24 hours ago to proceed. This minimizes the risk of fulfilling transactions that might still be pending payment clearance.


5. Batch Processing (Loop Over Items): Filtered items are prepared for sequential processing using the 'Loop Over Items' n8n node.


6. Fulfillment (HTTP Request): For each valid order, the 'Fulfill Order' n8n node sends a POST request to the Squarespace fulfillment endpoint, using OAuth 2.0 credentials. The payload is configured to set the order as fulfilled and trigger a customer notification ("shouldSendNotification": true).

To deploy this n8n workflow successfully, follow these steps:

1. Import: Copy the provided n8n workflow JSON and paste it into your n8n instance (Workflows -> New -> Import From JSON).


2. Squarespace Credentials: This n8n workflow requires two sets of credentials for Squarespace API access:

1. Configuration Node: Open the 'Globals' n8n node and verify the values. Ensure api-version is correct and adjust filters like modifiedAfter or modifiedBefore if you need to narrow down the search scope.


2. Set Trigger: Decide whether to use the 'Schedule Trigger' n8n trigger (and configure its interval) or run it manually. Disable the unused trigger to keep the n8n workflow clean.

This n8n template relies on several key n8n node types for its functionality:

Schedule Trigger / Manual Trigger: These n8n triggers initiate the automation, allowing for timed execution or manual testing.
Set (Globals): Sets flow-specific global variables, including the required API version (1.0) and filtering options like fulfillmentStatus (PENDING) and maxPage (-1) for infinite pagination.
HTTP Request (Query pending Orders): The core fetching n8n node. It dynamically builds the Squarespace API URL using defined variables and utilizes robust built-in pagination settings to handle large result sets automatically.
Split Out Order: Transforms the array of orders received from the API into individual items, enabling the n8n workflow to process them one by one.
Filter (Filter Orders): Implements a time-based condition to check if the order creation time is greater than 24 hours ago. This is a critical flow control measure within this n8n node.
Split In Batches (Loop Over Items): Ensures reliable looping over the filtered orders before the final fulfillment action.

• HTTP Request (Fulfill Order): Sends the POST request to the fulfillment endpoint for the specific order ID, confirming fulfillment status and triggering a notification to the customer via the shouldSendNotification: true parameter.