Trigger Cotonity workflows when contacts are added to or removed from HubSpot static or active lists, enabling real-time list-based automation.
Static vs. active lists as triggers
HubSpot lists come in two flavors: static lists, which are manually curated and only change when you explicitly add or remove members, and active lists, which automatically include contacts that meet defined criteria. Both can serve as Cotonity triggers. Static list additions are typically triggered by a manual import or another HubSpot workflow, making them useful for ad-hoc campaigns. Active list membership changes fire whenever a contact's properties shift to meet or stop meeting the list criteria, making them powerful real-time triggers for lifecycle-based automation.
Configuring a list trigger
In Cotonity, go to Triggers → HubSpot List Membership and select Added to List or Removed from List. Choose the target list from the dropdown (lists are grouped by type). Cotonity polls for list membership changes every 5 minutes on the Standard plan or uses a near-real-time webhook on the Business plan. The trigger payload includes the contact ID, the list ID, the timestamp of the membership change, and all contact properties you have included in the sync configuration.
Practical use cases
List-based triggers unlock a wide range of automations. Add a contact to an Event Attendees list when they register, triggering a Cotonity workflow that sends pre-event logistics emails via HubSpot. Remove a contact from a Trial Users list when their trial expires, triggering a conversion outreach sequence. Add a contact to a Re-engagement Candidates list (defined by 90+ days of inactivity) to trigger a personalized win-back campaign managed by a Cotonity conversational agent. The possibilities are limited only by your list criteria design.
Avoiding over-triggering
Active lists can fluctuate frequently if the criteria are based on volatile properties. A contact might enter and exit the same active list multiple times per day, which could trigger the same Cotonity workflow repeatedly. Use Cotonity's trigger frequency controls to limit how often a workflow can be triggered for the same contact — for example, at most once per 24 hours or once per list membership cycle. This prevents contacts from receiving duplicate messages and reduces unnecessary API calls against both Cotonity and HubSpot.