How to Track Shopify Product Views in HubSpot with Power Automate

HubSpot > Settings > Properties > Contact Properties > Create property

Create custom contact properties in HubSpot

Before building the flow, you need somewhere in HubSpot to store browsing data. In HubSpot, go to Settings > Properties, select Contact properties, and click Create property. Create two properties: one called 'Recently Viewed Products' (internal name: recently_viewed_products, type: Multi-line text) and one called 'Product Interest Categories' (internal name: product_interest_categories, type: Multi-line text). These will hold the pipe-delimited list of product titles and category names that Power Automate writes in later steps.

1. 1Log in to HubSpot and click the gear icon (Settings) in the top navigation
2. 2Select 'Properties' from the left sidebar under 'Data Management'
3. 3Click the 'Create property' button in the top right
4. 4Set Group to 'Contact Information', Label to 'Recently Viewed Products', Internal name to 'recently_viewed_products', Field type to 'Multi-line text'
5. 5Repeat for 'Product Interest Categories' with internal name 'product_interest_categories'
6. 6Click 'Create' after each property

Shopify Admin > Online Store > Themes > Edit code > product.liquid

Set up a Shopify webhook for product views

Shopify does not have a native 'product viewed' webhook event in its standard webhook catalog — product views must be captured via a Storefront script or a custom Shopify pixel that fires an HTTP request. In your Shopify admin, go to Online Store > Themes > Edit code, and locate the product.liquid or theme.liquid file. You will add a small JavaScript snippet that fires a POST request to your Power Automate HTTP trigger URL (which you will get in Step 4) whenever a logged-in customer loads a product page. The payload should include the customer email, product title, product ID, and product type.

1. 1In Shopify Admin, click 'Online Store' in the left sidebar
2. 2Click 'Themes', then click 'Edit code' next to your active theme
3. 3Open 'product.liquid' (or 'theme.liquid' if your theme uses sections)
4. 4Paste the JavaScript payload snippet at the bottom of the file, inside a <script> tag (you will insert the Power Automate URL after Step 4)
5. 5Save the file — do not publish yet

make.powerautomate.com > My flows > + New flow > Automated cloud flow

Open Power Automate and create a new Automated cloud flow

Go to make.powerautomate.com and sign in with your Microsoft account. From the left sidebar, click 'My flows', then click '+ New flow' and select 'Automated cloud flow'. Name the flow something like 'Shopify Product View → HubSpot Contact Update'. On the trigger picker screen, search for 'When an HTTP request is received' — this is the built-in Power Automate trigger that gives you a public URL Shopify can POST to. Select it and click 'Create'.

1. 1Go to make.powerautomate.com and sign in
2. 2Click 'My flows' in the left sidebar
3. 3Click '+ New flow' and choose 'Automated cloud flow'
4. 4Name the flow 'Shopify Product View to HubSpot'
5. 5In the trigger search box, type 'HTTP request' and select 'When an HTTP request is received'
6. 6Click 'Create'

Flow canvas > When an HTTP request is received > Use sample payload to generate schema

Configure the HTTP trigger and define the JSON schema

In the trigger card, click 'Use sample payload to generate schema'. Paste in a sample JSON body that matches what your Shopify script will send. This tells Power Automate exactly which fields to expect and makes them available as dynamic content in later steps. Save the flow once to generate the HTTP POST URL, then copy that URL — you will paste it into the Shopify product.liquid script from Step 2.

1. 1Click inside the 'When an HTTP request is received' trigger card
2. 2Click 'Use sample payload to generate schema'
3. 3Paste the sample JSON (see pro tip section for full schema)
4. 4Click 'Done' — Power Automate generates the JSON Schema automatically
5. 5Click 'Save' in the top right to generate the HTTP POST URL
6. 6Click the trigger card again and copy the HTTP POST URL field value
7. 7Paste this URL into the Shopify product.liquid script from Step 2 and re-save that file

Flow canvas > + New step > Data Operation > Parse JSON

Add a Parse JSON action to extract payload fields

Click '+ New step' below the trigger. Search for 'Parse JSON' and select the 'Data Operation: Parse JSON' action. In the Content field, insert the Body dynamic content token from the HTTP trigger. In the Schema field, paste the same schema you generated in Step 4. This step makes individual fields like customer_email and product_title accessible as named tokens throughout the rest of the flow.

1. 1Click '+ New step'
2. 2In the action search bar, type 'Parse JSON'
3. 3Select 'Parse JSON' under 'Data Operation'
4. 4Click in the 'Content' field and select 'Body' from the dynamic content panel (from the HTTP trigger)
5. 5Paste your JSON schema into the 'Schema' field

Flow canvas > + New step > HubSpot > Search for contacts

Look up the HubSpot contact by email

Click '+ New step'. Search for 'HubSpot' and select the HubSpot connector. Choose the action 'Search for contacts'. If this is your first HubSpot action, Power Automate will prompt you to create a Connection — click 'Sign in' and authenticate with your HubSpot account. In the filter field, set the search to match contacts where the 'Email' property equals the customer_email token from the Parse JSON step. This returns the HubSpot contact record including their current property values.

1. 1Click '+ New step'
2. 2Search for 'HubSpot' in the connector search bar
3. 3Select 'HubSpot' and choose 'Search for contacts'
4. 4If prompted, click 'Sign in' and complete OAuth with your HubSpot account
5. 5Set the filter property to 'Email', operator to 'equals', and value to the 'customer_email' dynamic content token
6. 6Set the properties to retrieve to include 'recently_viewed_products' and 'product_interest_categories'

Flow canvas > + New step > Control > Condition

Add a Condition to handle contact-not-found cases

The search in Step 6 returns zero results if the browsing customer has no HubSpot contact record. You need to handle this before trying to update a contact that does not exist. Click '+ New step' and add a 'Condition' control action. Set the condition to check if the 'Total' output from the HubSpot search action is greater than 0. In the 'If yes' branch, continue with the update steps. In the 'If no' branch, add a 'Terminate' action set to 'Succeeded' — this cleanly exits the flow without logging an error for unmatched visitors.

1. 1Click '+ New step'
2. 2Select 'Control' and then 'Condition'
3. 3In the left value field, select the 'Total' dynamic content token from the HubSpot Search for contacts step
4. 4Set the operator to 'is greater than' and the right value to '0'
5. 5In the 'If no' branch, click 'Add an action', search for 'Terminate', select it, and set Status to 'Succeeded'

Flow canvas > If yes branch > + Add an action > Data Operation > Compose

Build the updated product interest string

Inside the 'If yes' branch, add a 'Compose' action to construct the updated 'Recently Viewed Products' value. You want to append the new product_title to whatever is already stored in the contact's recently_viewed_products property — without overwriting previous views. In the Inputs field of the Compose action, write an expression that concatenates the existing property value with a pipe separator and the new product title. Use the expression: concat(body('Search_for_contacts')?['results']?[0]?['properties']?['recently_viewed_products']?['value'], ' | ', triggerBody()?['product_title']). Do the same in a second Compose action for product_interest_categories using product_type as the appended value.

1. 1Inside the 'Yes' branch, click 'Add an action'
2. 2Search for 'Compose' and select the 'Data Operation: Compose' action
3. 3Click in the 'Inputs' field and switch to the 'Expression' tab in the dynamic content panel
4. 4Enter: concat(body('Search_for_contacts')?['results']?[0]?['properties']?['recently_viewed_products']?['value'], ' | ', body('Parse_JSON')?['product_title'])
5. 5Click 'OK' and name this action 'Compose_Updated_Products'
6. 6Repeat for a second Compose action named 'Compose_Updated_Categories' using product_type instead of product_title

Flow canvas > If yes branch > + Add an action > HubSpot > Update a contact

Update the HubSpot contact properties

Still inside the 'Yes' branch, add another HubSpot action. Search for 'Update a contact' and select it. In the Contact ID field, use the ID from the first result of the search: body('Search_for_contacts')?['results']?[0]?['id']. Map the 'recently_viewed_products' property to the Output of the Compose_Updated_Products action. Map 'product_interest_categories' to the Output of the Compose_Updated_Categories action. You can also write additional static or dynamic fields here such as last_product_viewed_date using the utcNow() expression.

1. 1Click 'Add an action' inside the 'Yes' branch
2. 2Search for 'HubSpot' and select 'Update a contact'
3. 3In 'Contact ID', click the Expression tab and enter: body('Search_for_contacts')?['results']?[0]?['id']
4. 4Click '+ Add new property', select 'recently_viewed_products', and set the value to the Output of 'Compose_Updated_Products'
5. 5Click '+ Add new property' again, select 'product_interest_categories', and set the value to the Output of 'Compose_Updated_Categories'
6. 6Optionally add 'last_product_viewed_date' mapped to the expression: utcNow()

Flow canvas > + New step > Control > Scope

Add error handling with a Scope and Send an HTTP request fallback

Wrap Steps 6 through 9 in a 'Scope' control action so you can catch failures. Click the three-dot menu on each action inside the Yes branch and use 'Move inside Scope' (or add a Scope first and rebuild actions inside it). After the Scope, add a 'Run after' configured action — a second action set to run only if the Scope fails. Inside that fallback, add a 'Send an email (V2)' or a Teams notification to alert your team that a contact update failed, including the customer_email value so the failure is actionable.

1. 1Click '+ New step' before the HubSpot search action in the Yes branch
2. 2Select 'Control' then 'Scope'
3. 3Move or rebuild the HubSpot Search, Condition, Compose, and Update actions inside the Scope
4. 4Click '+ New step' after the Scope
5. 5Click the three-dot menu on the new step and select 'Configure run after'
6. 6Check 'has failed' and uncheck all other options
7. 7Add a 'Send an email (V2)' or 'Post message in a chat or channel' action with the failure details

make.powerautomate.com > My flows > [Flow name] > Run history

Test end-to-end and turn on the flow

Use a tool like Postman or curl to POST a test payload to your HTTP trigger URL with a real customer email that exists in HubSpot. Check the flow run history at make.powerautomate.com > My flows > [your flow] > Run history. Each step should show a green checkmark. Then open the matching HubSpot contact and confirm the recently_viewed_products and product_interest_categories fields show the test product data. Once confirmed, enable the Shopify theme script by updating any remaining placeholder values and verifying it fires on your staging store before going live.

1. 1Open Postman and create a POST request to your HTTP trigger URL
2. 2Set the body to raw JSON with customer_email, product_title, product_id, and product_type
3. 3Click Send and check for a 202 response
4. 4In Power Automate, click your flow name then 'Run history' to see the run appear
5. 5Click the run to expand each step and confirm all show green
6. 6Open HubSpot, find the test contact, and verify the property values updated correctly
7. 7Toggle the flow to 'On' using the button at the top of the flow detail page

This Power Automate expression block goes into the 'Inputs' field of the Compose action in Step 8. It handles the null-safe concatenation for both product titles and categories, deduplicates repeated category entries, and caps the stored product list at the 10 most recent views to keep the HubSpot property value from growing unbounded. Paste each expression into its own Compose action using the Expression tab in the dynamic content panel.

// Compose action 1: Compose_Updated_Products
// Safely appends new product title; caps list at 10 items
// Paste into the Inputs field > Expression tab

// Compose action 1: Compose_Updated_Products
// Safely appends new product title; caps list at 10 items
// Paste into the Inputs field > Expression tab
if(
  equals(coalesce(body('Search_for_contacts')?['results']?[0]?['properties']?['recently_viewed_products']?['value'], ''), ''),
  body('Parse_JSON')?['product_title'],
  join(
    take(
      split(
        concat(body('Search_for_contacts')?['results']?[0]?['properties']?['recently_viewed_products']?['value'], ' | ', body('Parse_JSON')?['product_title']),
        ' | '
      ),
      10
    ),
    ' | '
  )
)

// Compose action 2: Compose_Updated_Categories
// Appends new category and deduplicates using union()
// Paste into second Compose action Inputs field > Expression tab
join(
  union(
    split(
      coalesce(body('Search_for_contacts')?['results']?[0]?['properties']?['product_interest_categories']?['value'], ''),
      ' | '
    ),
    array(body('Parse_JSON')?['product_type'])
  ),
  ' | '
)

// Compose action 3: Compose_View_Count
// Increments product view count safely from null baseline
add(
  int(coalesce(body('Search_for_contacts')?['results']?[0]?['properties']?['product_view_count']?['value'], '0')),
  1
)