Google Sheet to Shopify Customer Bulk Creation - n8n Workflow

E-commerce Managers needing to migrate customer lists.
Developers implementing bulk data synchronization.
Businesses using Google Sheets as a primary CRM staging area.
Users looking for reliable, high-volume n8n templates for data migration.

This essential n8n workflow provides a robust solution for syncing large volumes of customer data from a Google Sheet directly into Shopify. Manual data entry is time-consuming and error-prone, especially during store migrations or large marketing campaigns. This n8n workflow bypasses these issues by leveraging the Google Sheets n8n node and the high-performance Shopify GraphQL API.

By utilizing this specific n8n templates design, users can ensure data consistency, rapid execution, and accurate customer record creation, including essential details like SMS marketing consent. Setting up the Shopify connection requires generating an API access token with the necessary write_customers scope, a critical setup detail detailed in the installation guide.

This automated process begins with the manual n8n trigger, initiating the data synchronization on demand. The flow is straightforward and powerful:

1. Data Retrieval: The first n8n node in the sequence is the Google Sheets node, which connects to the specified document and sheet ('Customers' in this case). It retrieves all customer records, ensuring the column names (e.g., firstname, email, mobilephone) match the expected format.


2. Iterative Creation: The data output from the Google Sheet is passed directly to the Shopify CustomerCreate n8n node. This GraphQL n8n node processes each record individually.


3. Shopify Integration: The n8n node executes a customerCreate mutation using the Shopify Admin API (GraphQL). It meticulously maps the fields from the Google Sheet row (email, mobilephone, firstname, last_name) into the required GraphQL input structure.


4. Consent Handling: As part of the mutation, the n8n workflow explicitly sets the smsMarketingConsent to 'SUBSCRIBED', ensuring compliance and proper tagging within the Shopify customer profile.

This reliable n8n workflow template ensures that every row in your Google Sheet results in a new, fully populated customer entry in your Shopify store.

To deploy and utilize this n8n workflow, follow these steps:

1. Import the n8n template: Copy the provided JSON and import it directly into your n8n instance.


2. Google Sheets Credentials: Configure the 'Google Sheet, Fetch Customers' n8n node. You will need to set up a Google Sheets OAuth2 API credential allowing n8n access to your target spreadsheet.


3. Shopify GraphQL Credentials: This is the most crucial step. Configure the 'Shopify, CustomerCreate' n8n node with a 'Header Auth' credential.

1. Sheet Structure Check: Ensure your Google Sheet contains the required column headers: firstname, lastname, email, and mobilephone. Note that the mobile_phone must be in international format without spaces (e.g., +61414708406), as enforced by Shopify.


2. Execution: Activate the n8n workflow and click the 'Execute Workflow' button on the manual n8n trigger to run the synchronization.

This efficient n8n workflow leverages three key components:

Start Workflow (Manual Trigger): This n8n trigger initiates the entire process manually. It allows you to run the bulk synchronization whenever you have new data ready in your Google Sheet.

Google Sheet, Fetch Customers (Google Sheets n8n node):
Function: Reads all data rows from the specified 'Customers' sheet within the designated Google spreadsheet.
Key Configuration: Configured to output data row by row, providing JSON objects for the next step.

Shopify, CustomerCreate (GraphQL n8n node):
Function: Executes the customerCreate GraphQL mutation against the Shopify Admin API for every input item received from the Google Sheet n8n node.
* Key Configuration: Requires 'Header Auth' for authentication. The variables field utilizes n8n expressions to map incoming data fields like {{ $json.email }} and {{ $json.mobile_phone }} directly into the CustomerInput object required by the mutation.