Make.com and HubSpot: Accessing All Your Contact Properties
Integrating HubSpot with other platforms like Make.com can unlock powerful automation workflows. However, sometimes things don't work quite as expected. Imagine setting up a Make.com scenario to watch for new contacts in HubSpot, only to find that most of your contact properties are missing! That's exactly the issue one HubSpot user ran into, and the community had some helpful insights to share.
The Problem: Missing HubSpot Properties in Make.com
The original poster described creating a Make.com integration that started with a "Watch CRM Object" trigger in HubSpot. The goal was to retrieve contact information. While basic properties like First Name, Last Name, and Email were available, dozens of other default and custom properties showed up as blank. This severely limited the usefulness of the integration.
The Solution: Using the GET Module
A community member identified the core issue: the "Watch CRM Object" trigger is designed to be lightweight. It efficiently detects changes and returns the Record ID, but it doesn't automatically fetch the entire data payload for all custom properties. Think of it like getting a notification that a package arrived – you know *something* is there, but you don't know exactly what's inside.
The solution is to use the Record ID obtained from the trigger and then use Make.com's GET module to retrieve the full contact data. Here’s how you can implement this:
- Set up your "Watch CRM Object" trigger in Make.com, connected to your HubSpot account and configured to watch for changes to the Contact object.
- Add a "GET" module after the trigger. This module will be responsible for fetching the complete contact data.
- Configure the "GET" module. You'll need to specify the HubSpot API endpoint for retrieving a contact by ID. This usually looks something like
/crm/v3/objects/contacts/{contactId}. Replace{contactId}with the Record ID obtained from the "Watch CRM Object" trigger. - Map the Record ID. In the "GET" module configuration, map the Record ID from the trigger's output to the
{contactId}parameter in the API endpoint. This tells Make.com which contact to retrieve. - Access your properties. Once the "GET" module is configured, it will retrieve the full contact data, including all your default and custom properties. You can then use these properties in subsequent modules in your Make.com scenario.
Why This Works
By using the "GET" module, you're explicitly telling Make.com to retrieve the complete contact record from HubSpot. This ensures that all properties, including custom ones, are available for use in your automation workflows. It's a two-step process, but it unlocks the full potential of your HubSpot data within Make.com.
Exploring the Make.com HubSpot Integration
The HubSpot Community manager also shared links to the Make.com integration in the HubSpot Marketplace and Make.com's documentation. While the documentation didn't explicitly mention mapping custom properties, understanding the limitations of the "Watch CRM Object" trigger and using the "GET" module provides a workaround.
ESHOPMAN Team Comment
This is a common issue when integrating platforms – not all triggers are created equal! The suggested solution of using a GET request to pull the full record is spot on. It's a good reminder to always check the documentation for specific triggers and understand their limitations. For e-commerce businesses using HubSpot, ensuring all customer data is accessible in integrations is crucial for personalized marketing and efficient automation.
By understanding the nuances of the "Watch CRM Object" trigger and leveraging the "GET" module, you can overcome this limitation and build powerful, data-rich integrations between HubSpot and Make.com. This ensures you can access all your valuable contact properties and use them to drive your marketing and sales efforts.