PERSONAL PRODUCTIVITY
Real-Time Email-to-Linear Issue Router
Watches your inbox for newly arriving email and, when a message reads like a real work request, drafts a clean Linear issue with the right team, priority, and a summarized…
How it runs
The automated pipeline, trigger to output.
- TriggerNew email in watched Gmail labelGmail
- ActionDetect request and draft fields with OpenAIOpenAI
- LogicBranch: skip if not a real request
- ActionCreate routed Linear issueLinear
- OutputConfirm capture in SlackSlack
What it does
As each new email lands, this workflow decides whether it contains an actionable engineering or ops request. If it does, it generates a structured Linear issue, routing it to the correct team and setting priority from the email's urgency cues, then replies in Slack so the requester knows it was captured.
When to use it
Use it when stakeholders email work requests instead of filing tickets, and those asks slip through. Good for teams that live in Linear but get inbound from non-technical colleagues over email.
How it works
- 1A new-email trigger fires the moment a message arrives in the watched Gmail label.
- 2An OpenAI step decides request vs. not-a-request and, if a request, drafts a title, description, team guess, and priority.
- 3A logic branch exits early for non-requests.
- 4A Linear issue is created from the structured fields.
- 5A Slack message confirms capture with the issue link so the thread owner can follow up.
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.