See llms.txt for all machine-readable content.

Back to Templates

Track champion job changes with Google Sheets, Apollo, Claude, Gmail and Slack

Quick overview

This workflow monitors a Google Sheets champion list for email bounce/“left company” signals in Gmail, verifies job changes via Apollo with an AI agent, and posts prioritized alerts plus a biweekly digest to Slack, with optional Hunter email finding and a webhook for “call now” engagement alerts.

How it works

  1. Runs every morning on a schedule (or manually for one contact), loads configuration, and ensures the required n8n Data Tables exist for state, cases, lookup cache, and credit usage.
  2. Reads champions and customer accounts from Google Sheets, loads prior state and lookup/usage history from Data Tables, and searches Gmail for recent bounces or “no longer with the company” auto-replies.
  3. Selects candidates to investigate based on inbox signals, due rechecks, retries, and a monthly sweep, and marks signal-based candidates as suspects in the state table.
  4. Looks up each candidate in Apollo (respecting per-run caps, lookup caching, and the monthly credit budget), updates the lookup cache and usage tables, and posts a Slack warning when the budget threshold is reached.
  5. Uses an Anthropic chat model agent to assess the Apollo evidence, classify the result as confirmed/verify/no change, and draft an outreach opener for confirmed moves.
  6. Scores and routes confirmed moves using your ICP/persona rules, optionally finds missing new work emails via Hunter, then writes case and state updates to Data Tables and posts formatted move or [VERIFY] alerts to Slack.
  7. Every other Monday, builds a digest from recent cases in the Data Table and posts the summary to Slack.
  8. Accepts POST requests on a webhook endpoint, matches engagement events to recently moved champions, posts a “call now” Slack alert, and records the last alert time to enforce a cooldown.

Setup

  1. Create a Google Sheet with Champions and Customers tabs (and columns matching the workflow mappings) and add Google Sheets OAuth credentials, then paste the sheet ID and tab names into the Config values.
  2. Add Gmail OAuth credentials and confirm or adjust the Gmail search query in Config to match how your bounce and “left company” signals appear.
  3. Add Slack credentials and set the target Slack channel name in Config.
  4. Add an Apollo API key as an HTTP Header Auth credential named x-api-key, then set your monthly Apollo budget and lookup timing settings in Config.
  5. Configure an Anthropic (or compatible) chat model credential for the AI agent and update the product/ICP/personas and team directory (Slack member IDs for mentions) in Config.
  6. (Optional) Add a Hunter HTTP Header Auth credential named X-API-KEY and set find_new_emails to true, and for “call now” alerts copy the webhook URL and configure your sequencing/website-intent tools to POST events to it with an email or company domain.