Turn Circle feature requests into Linear tickets every evening
Every day at 6pm, sweep your Circle community for fresh feature requests and file them as Linear tickets for your product team, with member quotes attached.
Build me an agent workflow that runs every day at 6pm and routes fresh feature requests from my Circle community into Linear tickets for my product team, with no manual babysitting.
Trigger: cron, daily at 6pm in my local timezone.
Inputs I want to configure once: the Circle space to watch (default to my 'Feature Requests' or 'Ideas' space, but make it swappable), and the Linear team or project where new product ideas should land.
Each run, the agent should:
1. Call Circle 'List Posts' scoped to my configured space and grab every post created in the past 24 hours. If the space isn't passed by ID, fall back to Circle 'List Spaces' to find the right space by name.
2. For each post, call Circle 'List Post Comments' to capture the discussion and any signal about how much the community cares (replies, agreement, upvotes mentioned in the thread).
3. Read each post and decide if it's a real feature idea. Skip spam, off-topic chatter, support questions, and venting that isn't actionable. Don't file those.
4. For every legitimate idea, draft a clean Linear-ready ticket: a clear, scannable title; the user's underlying problem in their own words; a proposed solution; a verbatim quote from the post; and a link back to the original Circle post so the product team can see the full context.
5. Before filing, call Linear 'Search Issues' to dedupe against existing tickets. If there's a strong match, call Linear 'Add Comment to Issue' to append the new member quote and any new context. Otherwise, call Linear 'Create Issue' in my configured product team or project.
6. After the Linear ticket exists, call Circle 'Create Comment' on the original post to acknowledge that the idea was logged and include a link to the Linear issue, so the member feels heard.
If a run finds zero new posts, exit quietly without filing or commenting anywhere. If a Linear call fails for one post, keep going with the rest and log what was skipped.
Additional information
What does this prompt do?
- Pulls the last 24 hours of posts from your Circle 'Feature Requests' or 'Ideas' space, including comments and engagement.
- Writes a clean, product-ready ticket for each idea: the problem in the member's own words, a proposed solution, and a link back to the original post.
- Checks Linear first to see if the request already exists, then either appends the new context to the matching ticket or files a fresh one in your product team's intake.
- Replies on the Circle post so the member knows their idea was logged, with a link to the Linear issue you created.
What do I need to use this?
- A Circle community on the Business plan or above, with a dedicated space for feature requests or ideas.
- A Linear workspace and the team or project where new product ideas should land.
- Permission to post comments in your Circle community as the connected account.
How can I customize it?
- Point it at a different Circle space (Bugs, General, a private VIP space) instead of Feature Requests.
- Change the schedule. Run it twice a day, only on weekdays, or only on Mondays for a weekly digest pass.
- Adjust the Linear destination, swap the team, route to a specific project, or tag every filed ticket with a label like 'community'.
- Tighten the spam filter or have it skip posts under a minimum upvote or comment threshold.
Frequently asked questions
Will members know their idea was logged?
What stops it from creating duplicate Linear tickets for the same idea?
Will it file spam or off-topic posts?
Can I run this on a different schedule?
Do I need the paid Circle plan?
Stop hand-copying community ideas into your roadmap tool.
Connect Circle and Linear once, and Geni files every fresh feature request, dedupes against your backlog, and closes the loop with the member.