hubspot-nango-integration

Incremental sync for HubSpot contacts uses the Search API with the `lastmodifieddate` property filter to fetch only changed records. The Search API allows 4 requests per second per token, making it efficient for large datasets. Include the `lastmodifieddate` property in your filter criteria and track the last sync timestamp to avoid redundant API calls.

HubSpot uses inconsistent property naming: contacts use `lastmodifieddate`, while other objects like companies and deals use `hs_lastmodifieddate`. This variation must be handled in schema-driven integrations to ensure accurate incremental filtering across all object types without data loss or missed updates.

Schema introspection enables dynamic discovery of custom and standard object properties in HubSpot. Query the schema once before fetching records to adapt your integration to customer-specific setups, then use discovered properties in subsequent data sync requests for complete field coverage.

Yes, HubSpot's Search API enforces 4 requests per second per OAuth token, while the Standard API has different rate limits. Plan request patterns to stay within Search API limits when syncing large datasets incrementally, and implement backoff strategies to handle rate-limit errors gracefully.

Two-phase sync first discovers the schema to identify available properties, then fetches records using that schema. This pattern ensures data completeness, handles custom fields correctly, and adapts automatically when HubSpot object structures change in customer environments.

OAuth token introspection verifies that your authentication token is valid and active before executing API requests. This prevents unnecessary API calls with expired credentials and allows you to detect authentication issues early in HubSpot integration workflows.