n8n E-commerce Automation Suite manual

What it does

• Receives POST requests in the Webhook Nuovo Ordine node, at the new-order path.
• Accepts customer_email, customer_name, and order_id either in the request body or at the top level of the received data.
• Responds to the webhook as soon as it is received because the node uses onReceived mode.
• Sends an HTML confirmation email through the Email Conferma node, including the order number.
• Appends the received data to the Ordini sheet in the configured Google Sheets document through the Log Ordine node.
• After Email Conferma, waits exactly 7 days in the Attendi 7 Giorni node and then sends an HTML email from the Richiedi Recensione node.
• The review request uses the customer from the original webhook and the link set in place of YOUR_REVIEW_LINK.

What it does not do

• It does not verify product delivery, receipt, or use: the seven-day count starts when the order webhook arrives.
• It does not create discounts, check inventory, issue refunds, or publish reviews.
• It does not configure your e-commerce platform for you or automatically create SMTP or Google accounts.
• It does not include order de-duplication logic: repeated webhook requests can create repeated executions.
• It does not include credentials, API keys, real email addresses, or a ready-made review link.

Requirements

• Package ZIP archive: Download and keep n8n-ecommerce-automation-suite.zip; it contains the two workflow JSON files and the guides.
• n8n instance: Use a cloud or self-hosted n8n instance compatible with the Webhook, Email Send, Google Sheets, and Wait nodes included in the workflow.
• E-commerce system with webhooks: Your e-commerce system must be able to send a POST request to the n8n webhook with customer_email, customer_name, and order_id.
• SMTP service: Configure an SMTP account in the two email nodes in n8n. The service may be paid; check the provider’s price list.
• Google account and Google Sheets spreadsheet: You need a Google Sheets document accessible to the account connected to n8n and containing a tab named Ordini. The service may depend on your Google plan.
• Data and email consent: Use personal data and email addresses under the applicable rules. For marketing messages or review requests, obtain consent where required and include an appropriate unsubscribe mechanism.

Step-by-step setup

1. Download and extract the archive. Download the purchased archive to a local folder and extract it. Do not rename the JSON files before import, so you can reliably identify the chosen variant.
2. Choose the customer-message language. For Italian messages, use n8n-ecommerce-automation.json. For English messages, use n8n-ecommerce-automation.en.json. The English variant keeps Italian node labels and the Ordini sheet name.
3. Import the workflow into n8n. In n8n, open Workflows, choose Import from File, and select the JSON for the desired variant. The import adds five nodes: Webhook Nuovo Ordine, Email Conferma, Log Ordine, Attendi 7 Giorni, and Richiedi Recensione.
4. Prepare the Google spreadsheet. Create or select the Google Sheets document to use and make sure it contains a tab named Ordini. The Log Ordine node appends data to that tab with automatic input-data mapping.
5. Connect Google Sheets. In the Log Ordine node, connect your Google account in n8n and replace YOUR_SHEET_ID in the documentId field with your spreadsheet identifier. Keep Ordini as the tab name, or change both the configured name and the actual tab in the same node.
6. Configure both emails. In the Email Conferma node, configure SMTP and replace YOUR_CONFIRMATION_FROM_EMAIL with an authorized sender. In the Richiedi Recensione node, configure SMTP and replace YOUR_REVIEW_FROM_EMAIL. Review the HTML subjects and text against your store’s actual terms.
7. Add the review link. In the Richiedi Recensione node message, replace YOUR_REVIEW_LINK with the URL of the page where you want to collect honest reviews. Before use, confirm that the link is correct and that sending complies with applicable rules.
8. Configure sending from your e-commerce platform. Copy the webhook address shown by the Webhook Nuovo Ordine node into your e-commerce order configuration. Send a POST request containing customer_email, customer_name, and order_id; the workflow reads these fields from the request body or the received data’s top level.
9. Run a controlled test. Send a test order to the test webhook using non-production data. Check that the confirmation email arrives and that Log Ordine appends data to the Ordini tab. The review request is not immediate: the Wait node is set to 7 days.
10. Enable the production webhook. Only after testing, use the production webhook URL in your e-commerce system and activate the workflow following the standard n8n process. If you use self-hosted n8n, make sure suspended Wait-node executions remain available for the full wait period.

Daily use

Check new executions

After activation, verify in n8n that the webhook receives the three expected fields and that the flow proceeds toward Email Conferma and Log Ordine.

Verify email and logging

Periodically check confirmation delivery and new rows in the Ordini tab. If you change the e-commerce payload, run another test first.

Manage the wait

Each confirmation creates an execution that proceeds to Richiedi Recensione after 7 days. In a self-hosted installation, keep the components required for suspended executions operating.

Keep content and consent current

Update the sender, text, link, and conditions mentioned in the emails whenever they change in your store. Do not send review requests to contacts without the required legal basis or consent.

Test after every change

If you change nodes, credentials, spreadsheet, SMTP, or webhook configuration, use test data and recheck email and logging before leaving the production flow active.

Practical cases

Confirmation for a small online shop

A small e-commerce shop can send the essential data to the webhook when an order is received.

1. Configure the e-commerce system to send a POST request to the webhook.
2. Send customer_email, customer_name, and order_id.
3. Configure the SMTP sender in Email Conferma.
4. Verify the confirmation email with a test order.

The customer receives the confirmation message defined by the workflow, and the shop can inspect its execution in n8n.

Order log in a shared spreadsheet

A team that consults a Google document can use the Ordini tab as a record of data received from the webhook.

1. Create or select the team’s Google Sheets document.
2. Add a tab named Ordini.
3. Enter the document ID in the Log Ordine node.
4. Connect the Google account and test a webhook.

The flow appends received data to the configured tab, where the team can consult it according to its Google permissions.

Review request after an order

A store with the necessary legal basis can send an invitation to leave an honest review.

1. Set a review URL in place of YOUR_REVIEW_LINK.
2. Configure the sender in the Richiedi Recensione node.
3. Check consent rules and any unsubscribe requirement.
4. Test the flow and account for the 7-day wait from the webhook.

After the configured wait, the workflow sends the message with the chosen link to the recipient provided by the webhook.

Messages for English-speaking customers

An e-commerce business that communicates in English can use the delivered variant with English email content.

1. Import n8n-ecommerce-automation.en.json.
2. Configure Google Sheets, SMTP, senders, and the link as for the Italian variant.
3. Send a test webhook with the three required fields.
4. Check the confirmation email content before activation.

The workflow retains the same node graph and sends English customer-facing messages, while node labels remain Italian.

Tips

• Keep an unmodified copy of both JSON files before customising the workflow in n8n.
• Replace all four delivered placeholders before activation: two senders, the spreadsheet ID, and the review link.
• Keep the tab named Ordini or update the sheetName field in the Log Ordine node consistently.
• Send customer_email, customer_name, and order_id with the exact names expected by the workflow; always test after an e-commerce change.
• Use an authorised SMTP sender and only email addresses for which you have the appropriate legal basis.
• Add an appropriate unsubscribe mechanism where required by law or the message type; the delivered template does not contain one.
• Do not present the review request as based on verified delivery: the workflow starts it seven days after the order webhook.
• For English customer messages, import the .en JSON; Webhook Nuovo Ordine, Log Ordine, and Attendi 7 Giorni remain labeled in Italian.
• Before enabling production, verify the review link and review the generated wording to ensure it genuinely reflects your store’s conditions.
• Protect the SMTP and Google credentials configured in n8n and do not place them in messages, public documents, or shared workflow copies.

Troubleshooting

The workflow does not import into n8n

The selected file may not be the workflow JSON or the n8n instance may not support the node types or versions present. Reimport one of the two delivered JSON files through Import from File and verify that the instance supports Webhook version 2, Email Send version 2, Google Sheets version 4, and Wait version 1.

The confirmation email has no recipient

The payload does not contain customer_email in the request body or at the top level of the data. Inspect the test order sent by the e-commerce system and make sure the field is named exactly customer_email.

Emails are not sent

SMTP is not configured in the relevant node or the sender placeholder has not been replaced with an authorised address. Configure the SMTP account in Email Conferma and Richiedi Recensione, then replace the respective fromEmail values and repeat a test.

The spreadsheet receives no data

The document ID, Google access, or tab name does not match the Log Ordine node configuration. Check documentId, the connected Google account’s permissions, and the existence of the Ordini tab, then send a new test webhook.

The review request does not arrive immediately

The Attendi 7 Giorni node is configured with amount 7 and unit days, so the flow waits seven days after Email Conferma. Check the suspended execution in n8n and wait for the expected due time. Do not interpret the wait as delivery verification.

A review request does not run after seven days in self-hosted n8n

Suspended Wait-node executions may not be retained correctly by the installation. Check the configuration and persistence of your self-hosted instance against the n8n documentation, then repeat a controlled test.

Multiple confirmations are created for the same order

The delivered workflow has no node that detects and blocks duplicate webhooks. Check whether the e-commerce system is retrying the same event and consider an n8n customisation suited to your process, testing it before production.

Messages remain Italian when English is needed

The original Italian file was imported instead of the .en variant. Import n8n-ecommerce-automation.en.json and reconfigure credentials, spreadsheet, senders, and link before activating it.

Limits to know

• The seven-day period is calculated from the moment the order webhook arrives, not from confirmed package delivery.
• The workflow does not check stock, shipments, payments, refunds, discounts, or review publication.
• The webhook and credentials must be configured by the e-commerce owner; the package contains no integrations already connected to a store.
• The workflow processes personal data such as email and name: comply with GDPR, privacy notices, data minimisation, security, and your e-commerce and provider terms.
• For commercial email or review requests, verify consent, legal basis, content, and unsubscribe requirements. The package is not legal or marketing-compliance certification.
• The English-variant documentation states offline JSON and structural checks, not execution while connected to providers; test it with non-production data before use.
• n8n, SMTP, Google, and other services used may have their own costs; the package does not state prices.

Frequently asked questions

Which file should I import?

Import n8n-ecommerce-automation.json for Italian emails or n8n-ecommerce-automation.en.json for English emails. The node graph, wait, and endpoints remain the same.

What data must my e-commerce system send?

It must send a POST request to the webhook with customer_email, customer_name, and order_id. The workflow looks for those fields in the request body and, alternatively, at the top level of the received data.

When is the review request sent?

It is sent seven days after the order webhook arrives, along the Email Conferma, Attendi 7 Giorni, Richiedi Recensione path. It does not wait for delivery confirmation.

Can I use a Google tab with a different name?

Yes, by changing the sheetName field in the Log Ordine node and ensuring that it matches an existing tab in the configured document. The delivered configuration uses Ordini.

Do I need to configure two email senders?

The workflow contains two separate placeholders, one in Email Conferma and one in Richiedi Recensione. Configure SMTP in both nodes and replace both with authorised senders.

Does the English variant also change node names?

No. The English variant changes customer-facing content; node labels and the Ordini tab name remain Italian.

Does the package prevent duplicate sends?

No. The five delivered nodes contain no de-duplication logic. If your e-commerce system can repeat webhook events, consider a customisation and test it before use.