Linear
Sync Revo with your Linear for issue tracking and project management.
What It Is
Revo connects to your Linear account to read projects, issues, cycles, teams, and comments, then transforms your engineering workflow into searchable, structured intelligence that powers fast, focused delivery.
What It Unlocks
- Search your entire Linear workspace using natural language across all projects, issues, cycles, teams, estimates, and comments
- Auto-sync work data with Revo's intelligence modules, cycle progress, team velocity, blocker trends, and project estimations
- Cross-reference Linear issues with Slack discussions, meetings, user feedback, GitHub pull requests, and product roadmaps
- Trigger workflows based on Linear events like issue state changes, cycle starts/ends, team updates, or assignee shifts
- Auto-generate insights from workflow data, analyze cycle burndown, surface blockers, and forecast delivery timelines
How to Use It for Emails
When drafting email replies, Revo automatically pulls relevant Linear context:
- "What's the status of Issue X?"
- → Revo checks Linear for current state, cycle placement, assignees, and linked discussions
- "How's the current cycle going?"
- → Revo analyzes progress, completed issues, remaining estimates, and velocity
- Includes source links to Linear issues or cycles so recipients can see full details and updates
Result: Emails grounded in current workflow status, no more "let me check the issue" or outdated cycle info.
How to Use It from Chat
Ask questions directly in Revo:
- "What issues are in progress this cycle?"
- "Show me blocked items for the design team"
- "What's our velocity trend over the last 3 cycles?"
Revo searches across Linear projects and issues, delivering answers with issue links and current estimates.
How to Use It in Workflows
Trigger workflows FROM Linear:
- Issue moves to "In Review"
- → Extract details and linked code
- → Cross-reference with GitHub PRs
- → Notify reviewers
- → "Issue LINEAR-456 ready for review, PR linked"
- Cycle starts
- → Pull cycle goals and issues
- → Generate kickoff summary
- → Post to #engineering
- → "Cycle C27 started: 12 issues, focus on core features"
- Issue set as blocked
- → Identify blocker details
- → Create escalation task
- → Notify team lead
- → "3 issues blocked by API changes, prioritize fix"
Update Linear FROM other sources:
- Meeting action item detected
- → Create Linear issue with transcript context
- → Assign owner
- → Set estimate
- → Link to meeting
- User feedback meets threshold
- → Auto-create issue cluster
- → Link source entries
- → Post for triage to #product
Generate insights FROM Linear:
- Cycle summary
- → Query completed issues, velocity, carry-over
- → Post to #engineering
- → "Cycle C26: 15 issues done, velocity 22 points, 1 carried over"
- Blocker patterns
- → Analyze recurring blockers
- → Surface trends
- → Notify leadership
- → "Dependencies blocked 6 issues this cycle, consider refactoring"