An Azure service for ingesting, preparing, and transforming data at scale.
Hi @Tariq Riahi
You're correct that the HubSpot connector v2.0 (Preview) no longer supports the query property, which was commonly used in v1.0 to implement incremental loads.
As a result, the v1.0 query-based incremental pattern doesn't carry over to v2.0.
The current v2.0 documentation focuses on accessing supported HubSpot objects via tableName, and it does not describe an equivalent built-in incremental load capability that replaces query.
If incremental ingestion is required, you'll likely need to implement it at the ADF pipeline level, for example:
- Maintain a watermark value (such as a last modified timestamp or ID).
- Store the latest processed value in an external control table or metadata store.
- Use pipeline logic to process only new or changed records where possible.
If you're migrating from v1.0 and depend heavily on query-based delta extraction, you may want to validate whether your specific HubSpot objects expose fields that can support a custom watermark strategy before moving to v2.0.
Documentation:
If you can share which HubSpot objects/tables you're loading and whether you're using Copy activity or Mapping Data Flows, we can suggest a more specific incremental loading pattern.