You sent the invitations. Maybe after a sales call, maybe after someone asked about the community in your DMs, maybe after a launch.
Some people clicked right away. The rest are still sitting in your Circle audience with an invitation and no accepted date. They were warm. They were one click from being inside. And this week, like last week, nobody followed up, because you were busy doing everything else.
That’s not a lost member yet. It’s a missed nudge.
This post sets up a Circle invite follow up you build once in Claude Cowork. It runs every Monday on its own, finds the people who haven’t accepted, resends their invitation, and tells you who got one.
What Does an Automated Circle Invite Follow Up Do?
Every Monday, Claude checks your Circle community for anyone invited in the last seven days who hasn’t accepted, resends their invitation, skips test accounts and duplicates, and reports back.
That’s the whole job. It isn’t a new onboarding flow or a drip sequence. It’s the follow up you already meant to send, handed to something that doesn’t forget on a busy Monday.
It runs inside Claude Cowork, the app where Claude can actually go and do the work using the tools you’ve connected. In this case, that’s your Circle account. You write the task once, set it on a schedule, and it shows up every week without a reminder from you.
This is video four in my MCP 101 series, and it’s the quickest payoff in the set. If you already have Circle connected to Claude from the earlier videos, you’re most of the way there.
The people it reaches matter more than they look. Someone who was invited and never came in is the earliest version of why new members leave your community: they drifted off before they ever started.
What Do You Need Before You Set It Up?
Two things: Circle connected to Claude, and a standard invitation email you’d be happy to send twice. The prompt resends whatever invite is saved in your Circle settings right now.
Circle connected to Claude
Claude needs access to your community to see who’s been invited and to resend anything.
What that looks like:
- Connect your Circle account to Claude, if you haven’t yet
- Open Claude Cowork, where the scheduled task will live
- Go back to the earlier videos in the series if either step is new to you
Nothing below works until this piece is in place, so start here.
An invitation email that sounds like you
This is the step people skip, and it’s the one that decides whether the follow up lands. The automation doesn’t write a new message. It resends your standard Circle invitation, exactly as it’s saved in your settings today.
What that looks like:
- Open your invitation email in Circle and read it as the person receiving it
- Make it warm, and make it sound like you
- Give it one clear next step
- Replace it entirely if it’s still the bare default
It takes two minutes, tops. That invitation is also the first step in your community onboarding process, so it deserves better than placeholder text, especially when it’s about to go out twice.
What Prompt Resends Circle Invitations Automatically?
This one. Put your community name in the brackets, paste it into Claude Cowork, and schedule it for Monday mornings.
Every Monday at 9 AM, look at [your community name] in Circle and find everyone who was invited in the last seven days but hasn’t accepted yet. Still inactive, no accepted date. Resend each of them their invitation. Skip anything that’s clearly a test account or a duplicate. Then give me a quick summary of who you re-invited and how many.
Each line is doing a specific job:
- The seven-day window keeps the list to recent invites only, so nobody from months ago gets a surprise
- “Still inactive, no accepted date” tells Claude exactly what “hasn’t accepted” means, so it doesn’t have to guess
- Skipping test accounts and duplicates means you’re not reinviting yourself or the dummy account you made to check a space
- The summary is your receipt: who got the nudge, and how many
That last line is the one I’d never cut. You want to see what ran, even when it runs without you.
How Do You Schedule It to Run Every Monday?
Set the task to repeat every Monday, then run it once by hand right away. That first manual run lets you accept any permissions it needs and watch it work before the schedule takes over.
Here’s the order:
- Paste the prompt into Claude Cowork with your community name filled in
- Set it to run every Monday
- Hit run on it now, the first time, instead of waiting for Monday
- Accept any permissions it asks for while you’re watching
- Read the summary it gives you back
The manual run is the part people forget, so don’t skip it. Do it while you’re at your desk, clear whatever it asks you to approve, and Monday is ready to go.
Then you’re done. The schedule takes it from here.
Will Automated Invite Reminders Spam People?
No. The task looks back seven days and runs once a week, so each person gets exactly one follow up and then ages out of the window. One nudge, and done.
That’s the design choice that makes it safe to leave running. You aren’t building a sequence that chases someone until they tune you out. Someone invited on a Wednesday gets the resend the following Monday. By the Monday after that, they’re outside the seven-day window, and Claude leaves them alone.
The test-account and duplicate rule matters here too. Without it, the person most likely to get spammed is you.
If you like handing your community a recurring job like this, a Circle AI weekly digest works on the same principle: set it up once, then check in on it instead of doing it.
When Should You Go Beyond the Simple Version?
When you want to see the list before anything sends, write something warmer than your standard invite, or reach people who went quiet months ago. Each of those builds on this same task.
This version is simple on purpose. There’s a whole other level to it:
- Approving people yourself before any invitation goes out
- Sending a warmer custom email instead of the standard invite
- Reaching back out to people who went cold months ago, not just last week
That’s more than a 101 build needs. The extended version lives inside coCreator Society, where I walk through each of those.
Start with the simple one anyway. You’ll see what your pending invites actually look like before you decide how much more control you want.
Try This Prompt
Since the automation resends your standard invitation as it is, get that email right before the first Monday run.
“I run a [type of community] on Circle for [who it’s for]. Here’s my current Circle invitation email: [paste it]. People get this when I invite them, and anyone who hasn’t accepted within a week gets it once more as a follow up. Rewrite it so it sounds warm and personal, reminds them why they were invited, and ends with one clear next step. Keep it under 120 words and give me two versions to choose from.”
Read both against how you actually talk. You pick the one that goes out twice.
One Nudge Is the Whole Job
Most people who don’t accept an invitation aren’t saying no. They’re saying later, and then later never comes, because nobody reminded them.
You don’t need a campaign for that. You need one follow up, sent on time, in an email that sounds like you. That’s exactly the kind of work that slips when you’re running everything else, and exactly the kind Claude can carry for you.
Set it once. Run it by hand. Let Monday handle the rest.
Watch the Video
New videos go up every Thursday on Your Community Strategist.
Watch This One
More like it on Your Community Strategist, new every Thursday.
More Like This
Watch: Circle MCP Tutorial: The New Member Welcome Prompt I Run Every Week. What to send the people who do accept.
Watch: Circle MCP Tutorial: The Weekly Recap Prompt I Run Every Monday. Another Monday job worth taking off your plate.
Listen: Engage Mode: Activated! Crafting a Welcome Series That Captivate. The welcome series that picks up once they’re inside.
Watch: Your Quiet Members Are About to Cancel. Circle AI Finds Them First. The same idea for members who joined and then went quiet.
Keep Going
coCreator Society is where community builders and membership founders work through this together, with the templates, the walkthroughs, and people who are one step ahead of you. Join coCreator Society
If you would rather not do this part alone, Rachel and the team build, migrate, and run communities for founders who need it done properly the first time. Talk to the team
Comments +
Comments