Dead Lead Reactivation

Create an n8n workflow with a Schedule trigger set to run once daily. The workflow queries multiple sources in parallel, then consolidates any trigger events found before moving to the drafting layer. For LinkedIn signals: connect to Clay or BirdDog via their APIs or n8n HTTP Request nodes. Pass your cold lead list as the input. These tools return job change events, company update events, and growth signals for the contacts you're monitoring. Configure which signal types to surface based on the two or three triggers you defined in prerequisites. For company news: add an RSS node for each key client's newsroom URL. Also create a Google Alert for each target company name and add the alert's RSS feed URL to n8n. The n8n RSS node can monitor multiple feeds simultaneously - set it to check for items published in the last 24 hours. For renewal windows: query your CRM for contacts where the estimated contract end date or last engagement date falls within your defined reactivation window (90 - 120 days before estimated renewal). This requires that your team log renewal date information consistently - if they don't, add that as a required field and back-fill it for key accounts before building this workflow. After pulling from all sources, add a deduplication step to handle cases where the same contact appears in multiple trigger sources on the same day.

This is the most important safeguard in the workflow. Before passing any trigger event to the drafting layer, check whether the contact is currently in an active pipeline stage in your CRM. Add a CRM lookup node that queries the contact's current deal stage. If the contact has an open opportunity in any non-closed stage (meaning a team member is already in conversation), skip the reactivation path and instead log the trigger event as a note on the CRM record. This note gives the active deal team useful context: "LinkedIn trigger: [Contact] just joined as CFO at [Company] - flagged for active deal team context." Never send an automated reactivation message to someone your team is currently speaking with. That's one of the most damaging things a semi-automated system can do to an active relationship.

For contacts that pass the pipeline check, pull the full CRM record: original inquiry details, past communications summary, why the deal didn't close (close-lost reason), any relationship notes, and the assigned team member. Pass all of this to the AI, along with the trigger event and your example reactivation messages as style guides. The AI prompt is structured to produce a short, targeted message - not a marketing email. Three to five sentences maximum. The message must reference the specific trigger event directly, connect it to why your firm is relevant right now, and make one simple ask. After the AI generates the draft, n8n posts a message to your Slack or Teams reviewer channel with everything the reviewer needs: contact name, company, the trigger that fired, a summary of the CRM history, and the draft. Include two buttons: "Approve and Send" and "Dismiss." Approval sends the email from the assigned team member's email address via n8n's email node and logs the outreach as a CRM activity. Dismissal logs that the trigger was reviewed and skipped.

You are a senior relationship manager at a professional services firm. Your job is to write a short, targeted reactivation message to a cold prospect.

Contact information: {{contact_name}}, {{contact_title}} at {{company_name}}
Trigger event that just fired: {{trigger_event_description}}
CRM history: {{crm_history_summary}}
Original inquiry reason: {{original_inquiry_reason}}
Why the deal didn't close: {{close_lost_reason}}
Time since last contact: {{days_since_last_contact}} days

Example reactivation messages that got replies (use these for tone and length reference only - do not copy them):
{{example_messages}}

Write a reactivation message that:
1. Opens with a direct, specific reference to the trigger event (max 1 sentence)
2. Connects the trigger to why your firm is relevant to their situation right now (1-2 sentences)
3. Makes one simple ask - typically requesting a 20-minute call (1 sentence)
4. Reads like a thoughtful person wrote it, not a marketing campaign

Constraints:
- Maximum 5 sentences total
- No subject line (that's handled separately)
- No attachments mentioned, no pitch decks, no links
- Do not reference that you've been tracking them or monitoring their company
- Sound like you noticed this through normal professional awareness, not surveillance

Return ONLY the email body text, nothing else.

When a reviewer approves a draft in Slack or Teams, n8n receives the approval signal via webhook and triggers the send workflow. The email goes out from the assigned team member's Gmail or Outlook via OAuth - not from a generic firm address. Using the assigned partner's email maintains the personal nature of the outreach. Log the outreach to the CRM immediately after sending: create an activity record on the contact with the send timestamp, the trigger that prompted the outreach, and the message sent. Update the contact's "Last Reactivation Attempt" field if your CRM has one, or create it as a custom property. This prevents the same contact from being surfaced again for the same trigger type within your defined cooldown period (typically 45 - 90 days). If the reviewer dismisses a draft, log the dismissal too: which trigger fired, which draft was generated, and that the reviewer chose not to send. This data helps you tune which trigger types are generating useful drafts versus noise over time.