Turn Circle feature requests into Linear tickets every evening

By General Input

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.

Integrations

  • Circle
  • Linear

Type

Agentic Task

Categories

  • Product
  • Operations

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.

Related prompts

Explore more prompts
Catch feature flags that never got switched on in productionWeekly alert noise review board for incident.io on-callMorning triage board for your Kernel browser agent runsTrack every half finished LaunchDarkly rollout in one boardFind the customers stuck contacting support again and againTurn shipped Linear work into Intercom product announcementsVoice agent QA review board for your Hume EVI callsClose the loop between Front tickets and Linear bug fixesOpen a Heroku release war room the moment production looks wrongFind the themes Help Scout tags miss and file them in Linear