From hubspot-admin
Build a workflow to protect sender reputation through automated bounce monitoring. Auto-suppresses contacts above a configurable bounce threshold, alerts on hard bounces, and flags high-bounce contacts for weekly manual review.
npx claudepluginhub tomgranot/hubspot-admin-skillsThis skill uses the workspace's default tool permissions.
Protect your email sender reputation with automated bounce detection and suppression. This workflow catches bounces as they happen rather than waiting for periodic cleanup.
Weekly manual review of contacts with 3+ bounce events. Decide whether to delete or attempt recovery for each flagged contact. Prevents over-suppression while removing truly bad data.
Automates Neverbounce email verification and list management tasks via Composio toolkit and Rube MCP. Requires Rube connection and prior tool discovery with RUBE_SEARCH_TOOLS.
Defines guardrails to pause signal-driven marketing/sales plays for risky, saturated, or in-flight accounts. Provides framework for taxonomy, detection, routing, duration, and audit trails.
Share bugs, ideas, or general feedback.
Protect your email sender reputation with automated bounce detection and suppression. This workflow catches bounces as they happen rather than waiting for periodic cleanup.
| Condition | Action |
|---|---|
| Hard bounce detected | Alert admin immediately, suppress contact |
| Suppression threshold reached (commonly 2-3 bounces) | Auto-suppress from marketing emails |
| Review threshold reached (commonly 3-5 bounces) | Flag for weekly manual review (delete vs. recover) |
email_health_flag or delivery_status) — checkbox or dropdown with value: "flagged for review"Follow the step-by-step instructions in the "Execute" section below. This is the most reliable method and gives you full control over every trigger, branch, and action.
HubSpot's built-in Breeze AI can generate a workflow skeleton from a natural language prompt. Navigate to Automation > Workflows > Create workflow > "Describe what you want" and paste the following prompt:
Create a contact-based workflow that triggers when the "Email Bounce" property
is known (has a value). The workflow should:
1. First, check if the contact has a hard bounce reason (hard_bounce_reason is known):
- If YES: send an internal notification saying "Hard bounce: [email]" and set the
contact as a non-marketing contact
- If NO: continue to the next check
2. Check if the bounce count is greater than or equal to [your suppression threshold, commonly 2-3]:
- If YES: set the contact as a non-marketing contact, then check if bounce count
is >= [your review threshold, commonly 3-5]. If so, set a custom property
"[your bounce review property]" to "flagged" and send an internal notification
saying "Contact [email] has [review threshold]+ bounces - review for deletion"
- If NO: end (below threshold, monitor only)
Enable re-enrollment so the contact re-enters if their bounce count increases.
CRITICAL WARNING: Breeze trigger limitations. Breeze creates event-based triggers (OR logic) instead of filter-based triggers (AND logic). After Breeze creates the workflow, you MUST manually verify and fix the trigger/enrollment conditions in the UI. Breeze is best used for creating the workflow skeleton (actions, branches, delays) -- the trigger conditions almost always need manual correction.
Additional Breeze limitations for this workflow:
The Claude Anthropic Chrome extension lets Claude see and interact with the HubSpot workflow builder UI directly. You can describe the workflow logic in natural language and Claude will click through the UI to build it. This is often more accurate than Breeze for workflows with nested branching logic (this workflow has three levels of branches), because Claude can verify the branch hierarchy visually.
To use this approach:
Note on Fast Mode: If you're using Claude Code's Fast Mode to speed up workflow creation, be aware of the billing model: Haiku usage is included in your subscription, but Opus in Fast Mode consumes extra credits. For workflow building tasks (which are UI-heavy and may require many interactions), consider whether the speed tradeoff is worth the credit cost.
Create your bounce review property (e.g., email_health_flag or delivery_status):
Identify your current bounce baseline — run a quick search for contacts where hs_email_bounce > 0 to understand the starting volume.
Build a single contact-based workflow with branching logic.
Trigger: hs_email_bounce is known (fires when bounce count updates)
Branch 1: Hard bounce check
hs_email_hard_bounce_reason_enum is knownhs_marketable_status to non-marketing (workflow action)Branch 2: Bounce count >= your suppression threshold (commonly 2-3)
hs_email_bounce is greater than or equal to your suppression thresholdhs_marketable_status to non-marketing (workflow action)Branch 3: Bounce count >= your review threshold (commonly 3-5)
hs_email_bounce is greater than or equal to your review thresholdSettings:
Turn on the workflow.
For contacts flagged at your review threshold: