Bye bye the Monday CSV. Grok Bot runs these 7 Circle jobs now.

Community work is mostly fetching data.

Open Insights, filter, export, open Sheets, sort by last active, open Circle again, write the DM, hope you tagged the right person.

I plugged Circle into Grok Bot with one prompt. Circle already had the members, the posts, and the inbox. Grok Bot reads all three, picks the move, and drafts it.

Circle’s own MCP is the connector. Sign in once. Start on Read only. Flip to Full access when you want it to comment or send.

Here are the seven jobs that used to eat my Monday.

1. I stopped exporting members into Sheets

Request the CSV. Wait. Open it. Filter last active, post count, comment count. That was the warm-up before a single check-in got written.

The export only existed because Insights and the inbox could not talk. Now the question and the list happen in Grok Bot.

2. I let it find the posted-once members

These people already tried. They joined, they posted, they went quiet. One reply away from becoming a regular, or from never coming back.

Finding them by hand meant a member export and a sort, every week. Now it is one sentence, and the list comes back with last active sitting next to the post they wrote.

3. I went after comments instead of post count

“Which posts got 50+ unique member views and zero comments this week?”

Those posts already showed up. People opened them and left. Circle has counted post views since July 2025, so this is not a vibe. It is a miss.

Rewriting the first line, or dropping a follow-up question in the thread, is a ten-minute fix on a post that took an hour to write.

4. I put last-seen in the same window as the post

Checking whether someone is actually around used to mean the directory, then their profile, then the space they lurk in.

Grok Bot holds last active, spaces, post count, and comment count while it is still looking at the thread. Nothing gets copied into a sheet. Nothing gets DMed to the member who already left in June.

5. I read the home feed before I wrote anything

A post does not have to be good in the abstract. It has to beat the three posts already sitting on the community home.

It pulls what members will see above it right now and writes the first line against those, not against a content calendar from last month.

6. I cut pasting DMs one name at a time

The last step used to be opening each profile, pasting a “hey, we missed you” note, hoping I did not send it to the person who posted yesterday.

Now the check-in is drafted in the same request that found the silent list. I still approve the send. I do not hunt.

7. I killed the delay between quiet and the check-in

The old loop was slow enough that last active was stale by the time I wrote. Friday’s export, Monday’s DMs, and half of them had already gone cold.

Live member data means the nudge matches this week. I am not retaining a snapshot from last Tuesday.

Lesson

Every one of these was already possible. Circle had last active, post views, and comments. The inbox had the DM. Insights had the download button.

The job was carrying lists between them. That is the part no one should still be doing by hand.

Now I type: “Which members posted once, then went quiet for 14 days? Draft the check-in DMs.” It reads Circle, lines up last active next to their post, and writes the notes. I say send on the ones I want.

Ship it

Circle MCP needs a Business plan or higher. It runs on Admin API v2, so each ask counts as an API request. Start Read only. Switch to Full access only when you are ready for comments and DMs.

1. Create a new Grok Bot.

2. Paste the prompt below as its instructions.

3. Tell it to connect Circle. The URL is https://app.circle.so/api/mcp.

4. Sign in with your Circle admin. Pick Read only.

5. Type the sentence above.

Nothing to code. No API key to dig for. You can also add that same URL in Claude, Cursor, or Claude Code. Same sign-in.

The prompt to paste