PERSONAL PRODUCTIVITY
Triage a shared support mailbox into Linear issues with round-robin assignment
Monitors a shared team mailbox, uses an LLM to classify each thread into an engineering area and severity, creates a Linear issue with a deadline.
How it runs
The automated pipeline, trigger to output.
- TriggerNew email in shared team mailboxGmail
- ActionClassify area/severity, draft issue + due dateOpenAI
- LogicDiscard out-of-scope; pick next round-robin assignee
- ActionCreate Linear issue with labels, due date, assigneeLinear
- ActionPost issue link to team Slack channelSlack
- OutputLabel Gmail thread as filedGmail
What it does
A shared mailbox collapses into a clean Linear backlog. Each inbound thread is classified by area (bug, request, question) and severity, turned into a Linear issue with an appropriate due date, and assigned to the next engineer in the rotation so no one owner gets buried.
When to use it
Use it when a team@ or support@ address feeds engineering work and you need every legitimate item tracked, labeled, and fairly distributed. Best for small teams without a dedicated triage manager.
How it works
- 1A new message arrives in the shared Gmail mailbox.
- 2An OpenAI step classifies area and severity, drafts an issue title and description, and proposes a due date from the severity.
- 3A logic branch discards pure thank-you replies and out-of-scope mail, and picks the next assignee in the round-robin order.
- 4A Linear action creates the issue with labels, the computed due date, and the chosen assignee.
- 5The flow posts the new issue link back into the team's Slack channel for visibility and labels the Gmail thread as filed.
Set it up
What you configure once, before turning it on.
- 1Connect GmailRead, draft, send, label.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Personal Productivity workflows
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.
Weekly Low-Attendance Recurring Meeting Auditor
Every Friday, scans the next week of recurring calendar events, flags those where confirmed attendance keeps dropping below a threshold.
Auto-decline focus-block invites unless the organizer is a VIP
Declines meetings that overlap your focus blocks by default, but routes invites from people on your VIP allowlist to a Slack approval prompt so important asks never get…
Auto-create weekly focus blocks around existing meetings and guard them
Every Sunday an agent reads next week's confirmed meetings, carves protected deep-work blocks into the open gaps, sets your Slack status to defend them.
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.
Weekly Subscription Audit: Find Noisy Lists Worth Unsubscribing
Once a week, analyzes which mailing lists flooded your inbox and how rarely you opened them.
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.