PERSONAL PRODUCTIVITY
Discord Feature Requests to Linear Backlog
Watches a Discord feature-request channel, detects genuine product requests, deduplicates against existing issues, and files or upvotes them as Linear tickets.
How it runs
The automated pipeline, trigger to output.
- TriggerNew message in Discord feature-request channelDiscord
- ActionClassify message as feature request or notOpenAI
- LogicDrop non-requests; search Linear for a duplicateLinear
- LogicBranch: existing issue vs new
- OutputComment + upvote existing issue, or create new Linear issueLinear
What it does
Keeps your product backlog in sync with what users actually ask for in Discord. When a new message lands in your feature-request channel, the agent decides whether it is a real product ask (versus a question or off-topic chatter). If it is, it checks whether a matching Linear issue already exists; if so it adds a comment and bumps the vote count, otherwise it creates a new issue with a clean title, the original quote, and the requester's handle.
When to use it
When feature requests pile up in Discord and never make it into the tracker, or the same idea gets filed five times. Built for PMs and small product teams who triage from one channel.
How it works
- 1A new message in the watched Discord channel triggers the flow.
- 2An LLM classifies the message as a feature request or not.
- 3Non-requests are dropped immediately.
- 4The agent searches Linear for a semantically similar open issue.
- 5If a match exists, it comments with the new context and increments support; if not, it creates a new Linear issue with the rewritten title and source quote.
Set it up
What you configure once, before turning it on.
- 1Connect DiscordCommunity channels + voice + bots.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Personal Productivity workflows
Monthly Meeting Cost Report by Email
On the first of each month, tallies every recurring meeting's total person-hours across the team, converts to an estimated dollar cost.
Turn Outlook email promises into assigned Asana tasks with due dates
When you send an email containing a commitment, an LLM extracts the promise and its deadline and creates a corresponding Asana task assigned to you with the due date set.
Auto-decline low-priority invites that collide with deep-work blocks
When a new calendar invite lands on top of a protected deep-work block, an AI scores its priority and auto-declines low-value meetings with a polite note proposing alternative…
Decline focus-block meetings and auto-propose a free slot via Notion log
When a low-priority invite hits a focus block, it declines the meeting, finds your next genuinely free slot, replies with a counter-proposal.
Log Outlook promises to Airtable with per-recipient commitment rollups
Captures promises from sent Outlook mail into an Airtable base, linking each commitment to a recipient record so you get a running per-contact view of everything you've promised…
Email-to-Task: Turn Action-Required Mail Into Linear Issues
Detects mail that contains a concrete task or request, extracts the deliverable and due date, and creates a Linear issue automatically so commitments from email never get lost.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.