Turn X complaints about your product into Linear tickets

By General Input

Every 15 minutes, scan X for fresh complaints about your product, classify each one, and file a clean Linear ticket so nothing slips by.

Integrations

  • TwitterAPI.io
  • Linear
  • Slack

Type

Agentic Task

Categories

  • Product
  • Customer Support

Build an agent that turns customer complaints about my product on X (Twitter) into actionable Linear tickets. Trigger it on a cron schedule every 15 minutes.

On every run, the agent should do the following:

1. Use TwitterAPI.io's Advanced Search to find new tweets that mention my product handle alongside complaint signals. The query should combine my product handle and aliases (e.g. @myproduct, my product name) with keywords like "broken", "doesn't work", "bug", "crash", "feature request", and "wish [product] could". Restrict the search to the last 15 minutes using sinceTime so the agent only sees fresh posts each run and doesn't refile old ones.

2. For every matching tweet, call TwitterAPI.io's Get Tweet Thread Context so the agent has the full conversation, not just the surface tweet. A vague-looking complaint often becomes clear once you can see the reply chain.

3. Classify each thread as one of: bug, feature-request, how-to, or non-actionable. Drop the how-to and non-actionable items immediately. Do not file anything for those.

4. For each remaining bug or feature request, use Linear's Create Issue to file a ticket. Route bugs to a configurable Bugs team and feature requests to a configurable Product team. Write a clean, descriptive title that captures what the user is actually hitting, not marketing language. In the description, include the original tweet quote, the relevant context from the thread, the author's @ handle, a direct link to the tweet, and a short paragraph with the agent's interpretation of what is actually being asked for or broken. Tag every issue with a "from-twitter" label (configurable). Set priority based on engagement: mark it high priority if the tweet has more than N likes (configurable, default 10) or if the author is verified. Otherwise leave priority at normal.

5. After all tickets for the run are filed, use Slack's Send a Message to post one summary to a configurable support channel. The summary should list how many tickets were filed, a link to each new Linear issue, and the original X author handle and tweet link for each, so the support team can reply on X with an acknowledgement. If nothing was filed in the run, do not post anything.

Configurable inputs the user should be able to set when installing the workflow: the product handle and any aliases, the complaint keyword list, the Linear Bugs team and Product team, the label to apply (default "from-twitter"), the likes threshold for high priority, and the Slack channel for the run summary.

Related prompts

Explore more prompts
Call overdue Xero customers with an AI collections agentWin back LiveChat visitors whose chats went unansweredChat quality review board for LiveChat support leadsWin back no-show and cancelled appointments every morningLive Loop returns analytics with product-level drill-downNewsletter pre-flight and approval board for Mailjet sendsTurn a prospect spreadsheet into personalized sequence enrollmentsMailjet email delivery lookup console for support teamsCatch feature flags that never got switched on in productionKajabi customer support console for member access fixes