-
Notifications
You must be signed in to change notification settings - Fork 5.5k
Description
Is your feature request related to a problem? Please describe.
The HubSpot "New Contact Property Change" trigger currently processes all existing contacts on first activation and triggers on newly created
contacts even when no actual property changes occurred. This results in workflows receiving events for thousands of existing contacts as "property
changes" when they represent historical data, and new contacts without property modifications trigger the workflow despite no actual changes.
Describe the solution you'd like
Two new configuration options for the HubSpot "New Contact Property Change" trigger:
- "Skip existing contacts when first activated" - When enabled, the trigger ignores all existing contacts and only watches for property
changes that happen after activation - "Only trigger on actual property changes" - When enabled, only fires when a contact property is actually modified (requires
propertiesWithHistory
), filtering out newly created contacts that haven't had property changes
Do you have a workaround?
Current options include:
- Processing all existing contacts and filtering in workflow logic
- Implementing custom timestamp-based filtering
- Manual event filtering within the workflow
These approaches require additional complexity and don't address the core issue of receiving irrelevant events.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status