Hi everyone,
We’ve been facing repeated, blocking issues with both the HubSpot CRM and Notion integrations on Make.
After several hours of testing and scenario rebuilding, it’s clear that the problems are not configuration mistakes but rather structural inconsistencies in how these modules behave.
1. HubSpot CRM Integration Issues
-
The “Search for Contacts” and “Search for Companies” modules frequently return incorrect or outdated results when matching by email.
-
For instance, a query for an existing contact email sometimes retrieves a completely unrelated company record.
-
It seems to use fuzzy matching, not an exact match on email, which causes serious data reliability issues.
-
-
Associated company data (name, domain, etc.) is often wrong or missing — even when the link is correct in HubSpot.
-
The “Create a Note” module fails with the error:
Missing value of required parameter 'toId'even though the correct Object ID is mapped from the previous search.
-
We’ve also noticed the same scenario sometimes succeeds and other times fails without any changes, making it impossible to debug or rely on for production.
2. Notion Integration Issues
-
The “Create a Page” module often fails without a clear explanation (validation or internal server errors).
-
Property mapping in Notion is unstable — fields appear blank, disappear after saving, or fail to update in the final record.
-
Relations and nested properties do not map correctly, even though they’re visible in the database schema.
3. Impact
We’re building a workflow that connects:
Google Calendar → HubSpot (or Notion) → OpenAI → Slack
to automatically generate structured meeting summaries.
Due to these issues, HubSpot and Notion have both proven too unreliable for consistent automation, forcing us to consider alternative systems.
4. Questions for the Make Team
-
Are these integration behaviors known or being addressed in upcoming updates?
-
Is there a way to enforce strict (exact) email matching in HubSpot contact searches?
-
Is the Notion connector being updated to better support relations and consistent field mapping?
We’d be happy to share screenshots, scenario IDs, and test results if that helps the investigation.
Would appreciate confirmation from Make staff or the community if others are facing the same reliability issues.
Thanks in advance,