Every agent knows the money’s in the follow-up. So why doesn’t it get done? It takes time you don’t have, you’re never sure what to say, and the leads worth writing to are buried in a database of thousands. This handles all three — it reads your CRM, finds the leads worth an email today, and writes the reply in your voice.
This is a Claude Plugin, which is a newer way to get an AI agent onto your machine. The old way was assembly: a folder to download, skills to install one by one, an instructions file to drop in, then pointing Cowork at all of it and hoping nothing was missed. A plugin skips the assembly. It’s one file, and it carries the skills, the instructions, and the setup questions that make it yours — installed together, in one step. Never built a Cowork agent? You’re not behind. You just skipped the hard part.
It works two kinds of leads, and only two:
It won’t touch your old dormant pile, past clients, or sphere — every one of those is a chance to send a generic email that damages a relationship. And it won’t write to a lead who already replied and is waiting on you. Those get flagged as a reply-owed list with no draft, because a conversation in progress deserves your actual reply.
Your first runs happen in demo mode: every email gets sent to you instead of the lead. Real email, your inbox, exactly what they would have received. Read a few batches. Switch to live only when you see work you’d put your name on.
One decision, and everything else follows from it: do you want a short talking-head video inside your follow-up emails? Remember those old BombBomb emails with the little looping clip of a face? That.
Why n8n for video? Claude’s built-in Gmail connection strips images out of emails before they send — every one, silently. We can’t work around that from inside Claude. n8n sends the email itself, so the image survives. We tested it: the animated preview renders in Apple Mail on desktop, Apple Mail on iPhone, and Gmail in a browser.
Start on the easy path and add video later if you want. Nothing gets thrown away — you point Claude at n8n instead of Gmail and carry on.
Six steps, in order. The first one is the longest because it’s the only one with anything to configure — after that you’re just talking to it.
STEP 1: CONNECT YOUR TOOLS
Claude reaches outside itself through connectors — the same place you’d add Gmail or Google Drive. Which ones you need depends on the path you picked above. Do these first; each one is a wall you’d otherwise hit halfway through setup.
1a. AiM Bridge — everyone needs this.
Bridge is what puts your CRM inside Claude. It’s read-only — it reads your leads and can never change anything. Bridge is one of the apps in the AiM Automations marketplace, so it requires the Automations add-on. Works with Follow Up Boss, Lofty, Sierra Interactive, BoldTrail (kvCORE), and CINC.
Setup takes about two minutes, and the instructions are here: apps.aimarketingacademy.com/bridge/redeem
1b. HeyGen — only if you want video.
This is what lets Claude write the script and produce the video for you. Have your avatar recorded in HeyGen before you start — this is built for their Avatar V model, so re-record if yours is on an older one. You won’t need any ID numbers; Claude reads the avatars in your account and asks which one you want, by name.
https://mcp.heygen.com/mcp/v11c. n8n — if you want video, or you’re on Outlook.
This is what sends the email so the video preview survives. You’ll need an n8n Cloud account — the hosted version at n8n.io, not a self-installed one. On Cloud, connecting your mailbox is one click; self-hosted means registering your own app in Google Cloud Console or Azure. Start by downloading the workflows:
Unzip it — inside are two files, one for Gmail and one for Outlook. n8n needs the .json, not the zip. Build it out in n8n first, then connect it to Claude last:
.json to match your mailbox./mcp-server/http.The order matters. Connect Claude to an empty n8n and it’ll link up fine while seeing no workflows — which looks like a broken connector and isn’t one. Build the workflow first and Claude finds it waiting.
Enabling MCP access and adding the connector are one-time-ever. Everything else repeats only if you add another workflow later. n8n’s own documentation for them: connect to the n8n MCP server
The one everyone misses: connect that same email account inside your CRM, too — every CRM on the list has an email-sync setting for it. That’s what logs these emails on the lead’s record. Without it, the emails send fine and your CRM never shows them.
WHAT ELSE BRIDGE UNLOCKS
Once Bridge is connected, it’s a permanent part of your Claude — every conversation, not just this one. CRM access is what this AI agent needs, and it’s the smallest part of what Bridge actually gives you.
Bridge also reads your Brand System — the profile you build inside AiM Automations that records your tone, your voice, and what you know about your own brand. It’s what makes anything the AI writes sound like you rather than like software, and it carries into every tool you connect. In practice that means the next step asks you a handful of questions instead of a dozen.
And Bridge reads the entire Academy library. Which means you can open Claude, ask “what did Jason say about handling pricing objections about twelve minutes into last month’s lecture?” — and get the actual answer, pulled from the lecture itself, not a paraphrase of something that sounds close. The Academy stops being a place you go and becomes something Claude just knows.
See what else comes with AiM Automations →
STEP 2: INSTALL THE PLUGIN
With your connectors in place, this is the last piece of configuration — and the point where you stop setting things up and start talking to it.
That’s the whole install — nothing to unzip, nothing to configure, no commands to memorize. From here on you just talk to it.
STEP 3: SET UP YOUR AGENT PROFILE
Your agent profile is what makes the writing yours instead of generic — your name and brokerage, your market, how you sign off, how often one person may be emailed. You build it once. Start a new Cowork task in Claude and paste this in:
There are about twenty things it needs to know, and you should only have to answer five. Before asking you anything, it goes looking: your Brand System, the signature already stored in your CRM (which usually carries your phone, license number, and office address), anything Claude already knows about you from past sessions, and — if you paste the link — your own website. Then it shows you everything it found in one block and asks you to correct whatever’s wrong.
What it can’t guess, it asks: the address you send from, your timezone, how often one person may be emailed, whether you want video, and your compliance confirmation. Plus one that’s worth your time — real writing samples, meaning a couple of emails you’ve actually sent to leads, pasted exactly as you sent them. That’s what separates follow-up that sounds like you from follow-up that sounds like software.
STEP 4: TEST IT IN DEMO MODE
Demo mode sends every email to you instead of the lead — real email, your inbox, exactly what they would have received. Nothing reaches a lead. Two commands, in this order. The first checks the wiring:
It verifies your CRM connection, your sending setup, whether your mail syncs back into your CRM, and your video setup if you’re using one — then sends a test email to you. Run it again any time something fails in a way that smells like a connection problem. The second command works your first batch:
“Who haven’t I followed up with?” works too. Every draft goes through a built-in critic that grades it and rewrites anything below the bar before it reaches you. Read a few batches in your own inbox and see whether this sounds like you.
STEP 5: SET IT LIVE
Live means it sends to your leads instead of you, on its own, with nobody reading them first. There are two states and no middle one — demo and live. It starts in demo and stays there until you say otherwise, and it won’t take a hint.
When you ask, it walks you through it one question at a time: whose database this is, whether you’re comfortable with emails going out that you haven’t read, and who owns it if one lands wrong. Then it makes you type send for real. A “yes” won’t do it, on purpose.
Be clear about what you’re agreeing to. Emails go to your actual leads, from your mailbox, under your name — and no human reads them before they send. Not you, not Claude. How many go out depends entirely on how many new leads come in: some weeks that’s two, some weeks it’s twenty, and nobody can tell you which in advance. You’re the sender. The leads are yours, the compliance is yours, and so is anything that lands wrong. That’s a reasonable trade once you’ve read a week of batches in demo. It’s a bad one if you haven’t.
You still see everything — just afterward. Every run emails you a summary: who it wrote to, the angle it used, the subject line, and every lead it held back with the reason why. If anything looks wrong mid-run, it stops and sends you the summary instead of sending the emails.
It also asks about a limit, right after you go live. By default it sends at most 10 emails per run — anything over that isn’t dropped, it waits and goes out first next time. Keep 10, pick your own number, or switch the limit off entirely. Your call, and you can change it later.
STEP 6: PUT IT ON A SCHEDULE
Everything up to here still needs you to start it, and a new inquiry that sits until Thursday isn’t speed to lead. You don’t have to do anything for this one — once you’re live, it offers:
Want me to run this on its own, or would you rather kick it off yourself each time?
If speed to lead is the point, run it hourly through your working day — a new inquiry gets a reply inside the hour instead of tomorrow morning. Lighter lead flow? Every weekday morning, every other day, or once a week all work. Tell it which, give it your hours, and it sets up the schedule for you.
A run that finds nothing does nothing. No new leads means it stops on the spot — no drafts, no video, no email to you. You only hear from it when something actually went out. So running it hourly doesn’t mean twelve notifications a day; it means the one inquiry that came in at 10:40 gets a reply at 11.
Say “change my follow-up schedule” or “stop the schedule” any time — you’re not stuck with a decision you made on a Tuesday.
WHAT IT WON’T DO
It also holds certain leads back: anyone with no record of where they came from, bounced addresses, Canadian leads past the six-month window (under Canada’s anti-spam law, an inquiry only gives you permission to email for six months), anyone under contract, anyone already emailed inside your cadence window, and records too thin to write anything honest about. It never skips quietly. You see the name and the reason — and when a held-back lead is one of your best, it says so and tells you to pick up the phone.