Daily Slack alert for unanswered Circle questions

Every weekday at 9am in my timezone, I want an agent that hunts down unanswered question posts in my Circle community and escalates them to my team in Slack so nothing slips through.

Trigger: cron, Monday through Friday at 9am.

Configuration I should be able to set when I install this:

1. Which Circle space to monitor (default to my Q&A or 'Ask the Community' space). Let me pick one or more spaces by name. If helpful, use Circle's List Spaces operation to surface the choices.

2. The 'stuck' threshold in hours (default 24).

3. The Slack channel to post the digest to (my community-ops channel).

What the agent should do on each run:

1. Use Circle's List Posts operation to pull recent posts from the configured space(s). Look back far enough to catch anything created in roughly the last 7 days, since older stuck posts matter too.

2. For each post, use Circle's List Post Comments operation to read the replies. Judge whether the post is actually a member question (questions, help requests, 'how do I…', '?' in title or body) and whether it has received a substantive answer. Ignore short emoji-only reactions, one-word 'thanks' / 'me too' / 'bump' replies, and replies from the original author talking to themselves. A real answer is a reply from another member or team member that actually addresses the question.

3. A post counts as stuck if it is a genuine question, was created at least 24 hours ago (or the configured threshold), and has zero substantive answers.

4. For each stuck post, draft a one-line summary of what the member is asking and include a permalink back to the Circle post. Group them by topic, urgency, or space so the digest is easy to scan: oldest or most urgent first.

5. Use Slack Bot's Send a Message operation to post the digest to the chosen community-ops channel. Format it with a short headline ('3 questions need attention'), each stuck question as its own bullet with the summary and link, and a sign-off pointing the team to claim them in Circle.

6. If there are zero stuck questions, still post a short 'all clear, no Circle questions waiting on answers this morning' note to the same channel so the team knows the check ran and the queue is empty. Do not stay silent.

Tone for the Slack message: warm and concise, written for a community-ops team. Use Slack mrkdwn for formatting (single asterisks for bold, angle-bracket links for the Circle permalinks). Do not @-mention anyone unless I configure that later.

Additional information

What does this prompt do?

Scans a chosen Circle space (like Q&A or Ask the Community) every weekday at 9am for posts asking a real question.
Reads the comments under each post and ignores fluff like emoji-only replies or quick 'thanks' so it can spot questions that still need a real answer.
Flags any question that has been waiting 24 hours or more, drafts a one-line summary, and links straight back to the Circle post.
Posts a grouped digest to the Slack channel your community-ops team lives in, or a quick 'all clear' note when nothing is stuck.

What do I need to use this?

A Circle community on the Business plan or higher, with an API token from your community admin settings.
A Slack workspace where you can add the General Input bot to the channel you want the digest posted in.
The name of the Circle space you want monitored (for example Q&A or Ask the Community) and the Slack channel where your team triages support.

How can I customize it?

Change which Circle space gets monitored, or watch more than one (one space for product questions, another for billing).
Adjust the 'stuck' threshold from 24 hours up or down to match your community's response SLA.
Switch the destination Slack channel, change the post time, or run it Monday to Friday only versus seven days a week.

Frequently asked questions

How does it decide a question is actually unanswered?

It reads the comments under each post and skips short emoji-only reactions, simple 'thanks' or 'me too' replies, and the original poster talking to themselves. If no team member or community veteran has left a substantive reply within 24 hours, the post counts as stuck.

Will it spam our community-ops channel with the same questions every day?

The digest is a snapshot of what is currently stuck, so a question that is still open will appear again the next morning until someone answers it. That's intentional: it keeps real questions from sliding off the radar. You can tune the threshold up if a daily nudge feels like too much.

What if every question has already been answered?

Instead of staying silent, the agent posts a short 'all clear, no stuck questions today' note so your team knows the check actually ran and didn't fail quietly.

Can I run it on more than one Circle space at once?

Yes. The most common setup is one space (your Q&A area), but you can list multiple spaces, like a product questions space and a billing help space, and the digest groups stuck posts by space.

Does it post as me or as a bot in Slack?

It posts as the General Input Slack bot, so the digest is attributed to your community-ops automation rather than a specific teammate. That keeps it working even if the person who set it up takes time off.