suppress-hard-bounced

To suppress hard-bounced contacts in HubSpot, this skill identifies them via API, exports a CSV audit trail, creates a dynamic active list for monitoring, and provides step-by-step UI guidance for manual suppression since the marketing flag is API read-only.

No, the hs_marketable_status cannot be set via API. This skill reads hard bounce reasons through the API and generates step-by-step UI instructions to manually suppress those contacts to non-marketing status.

You can audit hard-bounced contacts by running the skill's before-state script, which queries the HubSpot API for bounce reasons and exports a CSV audit log containing all identified hard-bounced contacts across the portal.

Yes, the skill requires HubSpot API access to read specific contact properties including hs_email_hard_bounce_reason_enum and hs_marketable_status, as well as the ability to create dynamic active lists for ongoing monitoring.

The skill creates a dynamic HubSpot active list to automatically monitor hard-bounce contacts over time, ensuring ongoing sender reputation protection by continuously tracking new bounces as they occur in the portal.

For high-bounce cases, the skill supports optional review lists alongside the dynamic monitoring list and UI suppression guidance, allowing you to carefully review and manage contacts with severe bounce issues before final removal.