Shopify + Google Sheets + Klaviyo integration — technical questions on 4 Make scenarios

Questions
, , , , ,
1

:bullseye: What is your goal?

Build 4 Make scenarios for a wine delivery service: daily inventory reset on Shopify, order processing to Sheets + Klaviyo + Shopify metafields, and Google Forms → Sheets tracking

:thinking: What is the problem & what have you tried?

Hi everyone,

I’m building a Make.com automation architecture for WineHoliday, a wine delivery service built on Shopify Basic.

The stack is:

  • Shopify Basic
  • Make.com
  • Google Sheets
  • Klaviyo
  • CallMeBot WhatsApp for internal test notifications

The goal is to build 4 main scenarios:

  1. Daily Shopify inventory reset
    Reset two Shopify delivery slot variants every morning at 08:00 Europe/Rome:
  • AM1 = 3
  • AM2 = 3
  • Tuesday = 0 for both

This should be done through Shopify GraphQL Admin API, ideally using inventorySetQuantities.

  1. Shopify order processing
    Trigger on orders/create, read order note_attributes, determine order_type, then:
  • add row to Google Sheets Orders_Log
  • send custom event to Klaviyo Events API
  • update Shopify order metafields
  • send internal WhatsApp briefing through CallMeBot

  1. Delivery stop completed
    Google Form response → Google Sheets
    Then update Stop_Log and the corresponding order row in Orders_Log.

  2. End of route / KPI tracking
    Google Form response → Route_Run
    Then calculate or update KPI fields such as minutes_per_order, km_per_order, margin_per_hour and Zone_Stats.

Main questions:

  • What is the best Make module to call Shopify GraphQL Admin API for inventorySetQuantities?
  • Should KPI calculations be done in Make or directly in Google Sheets?
  • For Google Forms, is it more robust to use the Google Forms module or Google Sheets “Watch New Rows”?
  • For deduplication, should I use Make Data Store, Shopify order metafields, or both?
  • For Klaviyo Events API, is it better to use a native Klaviyo module or an HTTP request?
  • Is it better to keep these as separate scenarios or consolidate them?

I attached the full technical document with all details.

Any advice on the cleanest and most robust Make architecture would be appreciated.

:camera_with_flash: Screenshots (scenario flow, module settings, errors)

WineHoliday_Documento_per_Make_Support.docx (42.8 KB)

4

To answer a few of your questions here:

Google Sheets Rows: It is probably best to go with the “Watch New Rows” as it is more reliable than the native Forms polling trigger.

KPI Calculations: This probably best done in Google Sheets rather than Make. It is much easier there to adjust the formulas and math in Sheets rather than having to modify a Make scenario in order to do so and end up burning operations, etc.

Klaviyo vs HTTP in general: Better to use the HTTP module with the Events API rather than Klaviyo. This will give you fuller control over event payloads and profile properties.

Overall I would keep your scenarios separate as it is a much easier way to handle things like errors and debugging as well as additions etc. This will keep changes isolated and prevent larger errors from forming.

5

Thanks Anthony, this is helpful and confirms the direction I was leaning toward.

I’ll use Google Sheets “Watch New Rows” for the Google Form responses, keep KPI calculations in Google Sheets, and use HTTP for Klaviyo Events API.

I also agree on keeping the scenarios separate for debugging and maintenance.

For now my planned architecture is:

  • Scenario A: scheduled Shopify slot inventory reset

  • Scenario B: Shopify order processing → Sheets + Klaviyo + Shopify metafields + WhatsApp

  • Scenario C: Google Form Stop Completed → Sheets

  • Scenario D: Google Form End of Route → Sheets/KPI

Thanks again!