How We Automated Basecamp Continuation Threads With Grok Bot

When a Basecamp thread gets long, Gmail tracking breaks around 100 comments. We start a Continuation in the same project so the conversation stays in one living thread.

We automated that with a Grok Bot agent. It watches Basecamp emails, counts comments, and posts the handoff before we hit the limit.

Here’s how we did this.

The rule it follows

We start a Continuation around 80 comments, including Boomerang follow-ups clients never see. Their count is lower than ours. The extra room is so Gmail does not hit the wall first.

The new thread stays in the same project. A message board post stays a message. A to-do stays a to-do. The title stays the same, with (Continuation) on the first one and (Continuation-2) on the next. Never (Continuation-1).

The new thread points back with two links: Previous Thread on the old title, then the explainer title. No spare URLs in the post.

The old thread gets this comment, with those titles as the links:

Please continue all discussions and updates here:

For context: Why Am I Seeing a “Continuation” Thread in Basecamp?

It runs every hour. When it actually creates one, we get the normal Basecamp email, same as any other comment.

How the agent is set up

The trigger is a Basecamp notification email, the same one the team already gets. The agent does not scrape every inbox. It only opens items from notifications@app.basecamp.com, then goes to that same project and that same recording.

It counts comments on the item itself. It does not guess from how long the Gmail thread looks.

If the latest thread people are using is under the limit, it leaves the item alone. If a Continuation for the next number already exists, it leaves the item alone. No duplicates.

When it does create one, it follows normal Basecamp notify behavior. People already on the project or thread get the new message and the handoff the same way they get any other post.

The part people get wrong

Some people keep talking on the old thread. Agents do it too.

If the next Continuation already exists, the agent stops. It does not open another one. We paste the same handoff on the old thread when we see the miss. We do not create Continuation-3 because the old one is still noisy.

Two living threads is how you lose the conversation.

That is why this had to be an agent. The job is boring, specific, and easy to skip. Grok Bot can see Gmail and Basecamp, post as us, and run at night. A person will forget. A scheduled agent will not.

If you run long Basecamp threads through Gmail, this is the product: one agent, one rule, one living thread.