Sync Shopify Gift Card Balances to Klaviyo Profiles

The schedule trigger runs daily at midnight (00:00 UTC). Each time it runs, it kicks off the entire workflow to retrieve all gift cards, calculate balances, and update Klaviyo profiles. You can adjust the frequency by modifying the schedule—for example, you could change it to weekly if daily seems excessive, or twice daily during high gift card redemption periods. The trigger automatically initiates at the configured time with no manual action required.

The step fetches up to 8,000 gift cards from Shopify using the gift cards API endpoint. This includes the gift card ID, initial value, current balance, customer ID, and important dates like creation, expiration, and any disable dates. The limit is set to 8,000 to handle stores with large gift card programs—if you have more than 8,000 active gift cards, you may need to implement pagination or contact support to handle your volume.

The step pulls your shop information, specifically your store domain (like "yourstore.myshopify.com"). This domain gets used in Step 5 to build URLs that link directly to each gift card's admin page in the format "https://admin.shopify.com/store/yourstore/gift_cards/{id}". This is auto-configured and runs in the background with no setup needed.

The loop iterates through all gift cards retrieved in Step 2, processing one gift card at a time through the remaining workflow steps. For example, if you have 500 active gift cards, the loop will run 500 times—once for each card—retrieving customer details, updating the data table, and syncing to Klaviyo for each unique customer. This loop structure allows the workflow to handle gift card programs of any size.

The step retrieves the full customer record using the customer ID from the gift card being processed in the loop. It pulls the customer's email (required to find them in Klaviyo), their first and last name (stored in the data table for reference), and any other customer properties. The API call automatically uses the customer ID from the current gift card to fetch the correct customer's details.

The step creates or updates a record in the "Shopify Gift Cards" table using the gift card ID as the unique identifier. If the gift card already exists in the table (from a previous sync), it updates the record; if it's new, it creates a new record. Each record stores: Gift Card ID, Initial Value, Current Balance, Customer ID, Customer Email, Customer Name, Created/Updated/Expires/Disabled dates, and a direct admin URL to the gift card. This table acts as both a historical record and the data source for the balance calculation query in the next step.

The step runs a SQL query against the "Shopify Gift Cards" table to calculate the sum of all gift card balances for the customer being processed. It filters by the customer's email and includes the condition WHERE "Disabled At" IS NOT NULL—though you should verify this logic matches your needs, as you may want to only count active cards (where Disabled At IS NULL). The query returns a single "Total Balance" value that represents all gift card value this customer holds.

The step queries Klaviyo's profiles API filtering by email address (using the customer email from Step 5) and limits results to 1 profile since emails should be unique. If a matching profile exists, it returns the profile ID needed to update their properties in Step 10. If no profile exists (customer hasn't been synced to Klaviyo yet), the query returns empty and the next filter step will stop the workflow for this customer.

The filter checks if the Klaviyo profile ID from Step 8 "is not empty." If a profile was found, the workflow continues to update it with the gift card balance; if no profile exists, the workflow stops here for this customer and moves to the next gift card in the loop. This is a hard-coded filter with no configuration needed—it automatically handles the workflow flow based on whether profiles exist.

The step updates the Klaviyo profile identified in Step 8, specifically adding or updating the custom property "Gift Card Balance" with the total balance calculated in Step 7. For example, if a customer has $85 across multiple gift cards, their Klaviyo profile gets a property Gift Card Balance: 85 that you can use in segments like "Gift Card Balance is greater than 20" or in email content with {{ person|lookup:'Gift Card Balance' }}. The update uses Klaviyo's v4 API and automatically handles creating the property if it doesn't exist.