How to Track Shopify Product Interest in HubSpot with Pipedream

pipedream.com > Workflows > New Workflow

Create a new Pipedream workflow

Go to pipedream.com and log in. Click 'New Workflow' in the top-right corner of the Workflows dashboard. Give it a name like 'Shopify Product Views → HubSpot Interest' so it's easy to find later. You'll land on the workflow canvas with a trigger slot waiting to be filled.

1. 1Click 'New Workflow' in the top-right
2. 2Enter workflow name: 'Shopify Product Views → HubSpot Interest'
3. 3Click 'Create' to open the canvas

Workflow Canvas > Add a trigger > Shopify > New Event (Instant)

Set up the Shopify webhook trigger

Click the 'Add a trigger' block and search for 'Shopify'. Select the Shopify app, then choose 'New Event (Instant)' — this gives you a raw HTTP webhook endpoint that Shopify will POST to on every topic you configure. Pipedream will display a unique webhook URL immediately after you save. Copy this URL — you'll paste it into Shopify in the next step. Connect your Shopify store by clicking 'Connect Account' and authenticating with your Shopify admin credentials.

1. 1Click 'Add a trigger'
2. 2Search for and select 'Shopify'
3. 3Choose 'New Event (Instant)' as the trigger type
4. 4Click 'Connect Account' and authenticate your Shopify store
5. 5Copy the generated webhook URL shown in the trigger configuration panel

Shopify Admin > Settings > Notifications > Webhooks

Register the webhook in Shopify

In your Shopify admin, go to Settings > Notifications > Webhooks and click 'Create webhook'. For standard order or customer events, you'd pick a topic from the dropdown — but for product view tracking, you'll fire the webhook from your storefront theme instead. Add the Pipedream URL to your theme's product page template so it POSTs a payload whenever a logged-in customer loads a product page. The payload should include the customer's email, the product ID, product title, and product type.

1. 1Open Shopify Admin and navigate to Settings > Notifications
2. 2Scroll to the Webhooks section and click 'Create webhook' for reference
3. 3In your theme code (Online Store > Themes > Edit Code), open product.liquid or the relevant product template
4. 4Add a fetch() call in the theme JavaScript that POSTs customer and product data to your Pipedream URL on page load
5. 5Save the theme changes and test by visiting a product page while logged in as a customer

Workflow Canvas > + Add Step > Run Node.js code

Parse and validate the incoming payload

Add a new Node.js code step after the trigger. This step extracts the fields you need from the raw webhook body and throws a descriptive error if any required field is missing. This prevents bad data from reaching HubSpot. Pull out customer_email, product_id, product_title, product_type, and a timestamp. Log the parsed values using console.log so they appear in Pipedream's event inspector during testing.

1. 1Click '+ Add Step' below the trigger block
2. 2Select 'Run Node.js code'
3. 3Paste the validation code into the code editor
4. 4Click 'Test' to run against the last captured event

Workflow Canvas > + Add Step > Run Node.js code

Look up the contact in HubSpot by email

Add another Node.js code step to find the matching HubSpot contact. Use the HubSpot v3 Contacts API: GET /crm/v3/objects/contacts/search with a filter on the email property. Pass the customer_email from the previous step as the filter value. If no contact is found, export a flag (contactFound: false) so a later step can skip the update gracefully instead of throwing an error.

1. 1Click '+ Add Step' and select 'Run Node.js code'
2. 2Use the HubSpot Connected Account to supply the Bearer token via process.env or the $ helper
3. 3Write the search API call targeting /crm/v3/objects/contacts/search
4. 4Parse the response and export contactId and contactFound
5. 5Click 'Test' and confirm a real contact ID appears in the exports

Workflow Canvas > + Add Step > Filter

Add a filter step to skip unmatched contacts

Add a Pipedream Filter step after the HubSpot lookup. Configure it to continue only when contactFound is true. This prevents the update step from running against a null contact ID, which would throw a 404 from HubSpot's API and mark the event as failed. For contacts that don't exist yet, you may want to add a parallel branch later that creates the contact — but start with a clean skip for now.

1. 1Click '+ Add Step'
2. 2Select 'Filter' from the step type list
3. 3Set the condition to: steps.hubspot_lookup.contactFound === true
4. 4Click 'Continue if true'
5. 5Test with both a matched and unmatched email to confirm the filter behaves correctly

Workflow Canvas > + Add Step > Run Node.js code

Read the contact's existing product interests

Before writing new interest data, fetch the contact's current values for the product interest properties. Use a GET request to /crm/v3/objects/contacts/{contactId}?properties=product_interests,last_viewed_product,last_viewed_category. This prevents overwriting historical interest data with only the latest view. You'll merge the existing array with the new product type in the next step.

1. 1Add a new Node.js code step
2. 2Call GET /crm/v3/objects/contacts/{contactId} with the properties query param
3. 3Parse the properties object from the response
4. 4Export existing_interests as an array (split on semicolon if stored as a string)
5. 5Test and confirm the exported array reflects whatever is already on the contact

Workflow Canvas > + Add Step > Run Node.js code

Merge and deduplicate interests

Add a Node.js code step to combine the existing interests with the new product type from the current browse event. Use a Set to deduplicate so the same category isn't appended multiple times. Then join the Set back into a semicolon-delimited string for HubSpot. Also prepare the last_viewed_product and last_viewed_at values. Export the merged string and the individual field values as separate exports for the next step.

1. 1Add a new Node.js code step
2. 2Import existing_interests from the previous step
3. 3Spread into a Set with the new product_type and convert back to array
4. 4Join with semicolons to form the merged interests string
5. 5Export merged_interests, last_viewed_product, and last_viewed_at

Workflow Canvas > + Add Step > Run Node.js code

Update the HubSpot contact properties

Add a final Node.js code step to PATCH the HubSpot contact with the merged interest data. Hit /crm/v3/objects/contacts/{contactId} with a PATCH request. The body should include the product_interests, last_viewed_product, last_viewed_category, and last_viewed_at properties. Use the Connected Account OAuth token from the HubSpot app in Pipedream — reference it via auths.hubspot.oauth_access_token so you don't hard-code credentials.

1. 1Add a new Node.js code step
2. 2Reference the HubSpot token via auths.hubspot.oauth_access_token
3. 3Build the PATCH request body with all four property fields
4. 4Send the PATCH to /crm/v3/objects/contacts/{contactId}
5. 5Log the response status and export the updated contact ID for confirmation

Workflow Canvas > Deploy (top-right button)

Add error handling and activate the workflow

Wrap your API calls in try/catch blocks and use $.flow.exit() to stop execution cleanly on non-retryable errors (like a 404 on a deleted contact). For 429 rate limit responses, throw an error so Pipedream's automatic retry kicks in. Once testing passes with real events, click 'Deploy' in the top-right corner to make the workflow live. Pipedream will start processing all new incoming webhook events immediately.

1. 1Review each code step and add try/catch around fetch() calls
2. 2For 429 responses, throw new Error('Rate limited') to trigger Pipedream retry
3. 3For 404 responses, call $.flow.exit('Contact not found — skipping')
4. 4Click 'Deploy' in the top-right corner
5. 5Trigger a real product view on your Shopify store and confirm the HubSpot contact updates

Paste this into a single Node.js code step that handles the HubSpot lookup, interest merge, and contact update in one shot. This replaces steps 5, 7, 8, and 9 with a single step — fewer round-trips, cleaner event logs. Reference it from the step immediately after your parse/validate step.

import axios from 'axios';
export default defineComponent({
  props: {

import axios from 'axios';

export default defineComponent({
  props: {
    hubspot: {
      type: 'app',
      app: 'hubspot',
    },
  },
  async run({ steps, $ }) {
    const email = steps.parse_payload.$return_value.customer_email;
    const productType = steps.parse_payload.$return_value.product_type;
    const productTitle = steps.parse_payload.$return_value.product_title;
    const shopifyCustomerId = steps.parse_payload.$return_value.customer_id;
    const viewedAt = new Date(steps.parse_payload.$return_value.viewed_at).getTime();

    const baseURL = 'https://api.hubapi.com';
    const headers = {
      Authorization: `Bearer ${this.hubspot.$auth.oauth_access_token}`,
      'Content-Type': 'application/json',
    };

    // Step 1: Find contact by email
    const searchRes = await axios({
      method: 'POST',
      url: `${baseURL}/crm/v3/objects/contacts/search`,
      headers,
      data: {
        filterGroups: [{
          filters: [{
            propertyName: 'email',
            operator: 'EQ',
            value: email.trim().toLowerCase(),
          }],
        }],
        properties: ['email', 'product_interests', 'shopify_product_view_count'],
        limit: 1,
      },
    });

    if (searchRes.data.total === 0) {
      $.flow.exit(`No HubSpot contact found for email: ${email}`);
    }

    const contact = searchRes.data.results[0];
    const contactId = contact.id;
    const rawInterests = contact.properties.product_interests || '';
    const currentViewCount = parseInt(contact.properties.shopify_product_view_count || '0', 10);

    // Step 2: Merge and deduplicate interests
    const existingInterests = rawInterests.split(';').filter(Boolean);
    const mergedInterests = [...new Set([...existingInterests, productType])].join(';');
    const newViewCount = currentViewCount + 1;

    // Step 3: PATCH the contact
    const patchRes = await axios({
      method: 'PATCH',
      url: `${baseURL}/crm/v3/objects/contacts/${contactId}`,
      headers,
      data: {
        properties: {
          product_interests: mergedInterests,
          last_viewed_product: productTitle,
          last_viewed_category: productType,
          last_viewed_at: viewedAt,
          shopify_customer_id: shopifyCustomerId,
          shopify_product_view_count: newViewCount.toString(),
        },
      },
    });

    if (patchRes.status !== 200) {
      throw new Error(`HubSpot PATCH failed with status ${patchRes.status}`);
    }

    return {
      contactId,
      updatedInterests: mergedInterests,
      viewCount: newViewCount,
      status: 'updated',
    };
  },
});