A Clay and HubSpot reactivation workflow starts with a real relationship, a current reason to reconnect, and a clear owner. HubSpot identifies the account’s lifecycle, deal history, contacts, and permissions. Clay can check whether the company or buying team has changed and prepare a sourced brief. The resulting action belongs back in HubSpot, where sales or customer success can decide whether contact is appropriate.
This approach serves two different goals: reconnecting with a previously known prospect and finding relevant expansion opportunities within an existing customer account. They should not share one undifferentiated campaign. Their owners, context, consent, and success measures differ.
Which CRM records should enter a reactivation play?
Define cohorts by relationship state, not by a blanket “no activity” rule. HubSpot’s lifecycle stages describe where contacts and companies sit in the marketing and sales process; they should not be reset merely to make a workflow run again. Use deal status, owner, last meaningful interaction, suppression status, and recorded reason for the earlier stop to decide what deserves review.
| Cohort | Required review | Likely owner |
|---|---|---|
| Previously engaged prospect | Confirm prior conversation, current fit, and a new reason to reconnect. | Sales owner |
| Closed-lost opportunity | Read the loss reason and verify that the blocking condition may have changed. | Original owner or assigned account lead |
| Existing customer | Check health, contract scope, open service issues, and account plan before an expansion conversation. | Customer success or account owner |
Exclude active opportunities, disputed or inactive relationships, recently contacted accounts, records without a responsible owner, and contacts whose communication status disallows the intended channel. A dormant record alone does not establish a useful sales moment.
How do Clay and HubSpot divide the work?
- Build a clean cohort in HubSpot. Use company, contact, and deal criteria that reflect the actual relationship. HubSpot active segments can update as records enter or leave the criteria; a static segment can preserve a fixed test cohort. Check association filters so a contact is not selected because of the wrong company.
- Import only the selected records into Clay. Clay’s HubSpot integration supports importing objects, including a selected list when configured. Retain the HubSpot object ID, owner, cohort, and relevant relationship fields.
- Refresh only decision-critical data. Verify the company and contact are still current. Check public changes that relate to the offer, such as a relevant leadership, hiring, or product change. Clay custom signals can monitor defined sources, but the event must still be judged against the relationship and offer.
- Hold uncertain findings. Do not turn a weak match, stale source, or changed contact role into an automatic message. Route the account to the owner with the reason for uncertainty.
- Create the next action in HubSpot. For a valid prospect reactivation, give sales a task with the prior context, verified change, and suggested conversation objective. For an existing customer, route the brief to the account or success owner to decide whether it belongs in an account review.
- Stop on a new state. Remove accounts when an opportunity opens, a customer issue takes precedence, a contact opts out, or the owner declines the play. Configure workflow re-enrollment deliberately; HubSpot’s workflow documentation makes clear that re-enrollment depends on settings and fresh trigger conditions.
Clay should enrich and explain an opportunity to act; HubSpot should preserve the relationship and outcome. Matching by existing object ID reduces the risk of creating a second company or contact. HubSpot warns that API-created companies are not automatically deduplicated by domain, so ambiguous matches need manual resolution.
What makes a customer expansion play different?
Expansion begins with value already delivered and the customer’s current situation, not a cold-prospecting message. The owner should review open tickets, adoption or account notes where available, contract boundaries, and any recent conversations before interpreting an external signal. Clay can help identify a public change or missing buying role, but it cannot determine customer health or promise that an upsell is appropriate.
Build a separate route for customer accounts. The output can be a research brief for an account review, a task to confirm the new stakeholder, or a recommendation to defer contact. Keep customer data and external enrichment in distinct fields so the account team can see what is known internally and what Clay inferred from outside sources.
How do you measure reactivation and expansion?
Report each cohort separately. For prospect reactivation, track eligible accounts, owner acceptance, accounts contacted after review, useful replies or meetings, opportunities created, and reasons for rejection. For customer expansion, track reviewed accounts, accepted account plans, expansion conversations, qualified opportunities, and actual deal outcomes. Preserve a fixed test cohort or date window so the team can compare the process over time without counting the same account repeatedly.
HubSpot’s custom report builder can join selected CRM data sources on eligible subscriptions. Simpler saved views and exports can support a first pilot. The point is to measure whether the new trigger produced a useful owner action and a real commercial outcome, not how many records were re-enriched.
Frequently asked questions
Should every old lead receive a reactivation email?
No. Old records need current fit, a relevant reason to reconnect, an owner, and permission for the intended channel. HubSpot requires verifiable opt-in for marketing email; enrichment does not create that permission.
Can Clay automatically change lifecycle stages?
Clay can update HubSpot records through the integration, but a lifecycle change should follow the team’s agreed stage definition and approval rules. A research signal alone is not a new stage or an opportunity.
What is the smallest useful pilot?
Choose one relationship cohort, one reason for review, and one owner action. Audit the records and their communication status, then measure owner acceptance and downstream outcomes before adding more signals or automated messaging.
Want to turn existing CRM relationships into a thoughtful growth program? Explore our HubSpot development and RevOps service and Clay and HubSpot consulting, then tell us how your team currently handles dormant prospects and customer expansion.
Product documentation
HubSpot: Lifecycle stages · HubSpot: Segments · HubSpot: Workflows · Clay: HubSpot integration · Clay: Custom signals