Linear Integration & Workflow Automation
Run Linear on autopilot. Keep the veto.
33 actions3 triggers
Issues get reassigned, comments post, and projects update before you've read the context; Rills proposes every Linear change and waits for your call.
Interactive. No signup. 14 days free · approvals always free.
Most automation fires first, asks later. Rills shows you the change before it ships.
Every consequential project management action from Linear arrives on your phone first. Approve in seconds. Decline without explaining yourself. Workflows wait, paused at zero cost, until you decide.
Queue 3
Move 14 stalled issues from In Progress to Blocked?
14 issues · no status change in 9+ days
Same pattern flagged in last sprint review
3 issues assigned to teammates currently on leave
Free to wait. Free to think.
Approvals and logic don't cost a credit. Pause a workflow for three hours or three weeks. The price is the same: zero. You only pay when something real happens: an AI call, an outbound action.
Approve from your phone in five seconds.
Swipe right when you're sure. Decline when you're not. Between meetings, mid-coffee, on the train. No dashboard to babysit, no inbox triage, no 3am stomach-drop wondering what shipped while you slept.
Routine cases graduate themselves.
Every approval feeds a confidence score for that exact workflow shape. The obvious cases (the ones you've green-lit fifty times) start running on their own. The judgment calls still come to you.
About Linear automation
Issue status changes, bulk reassignments, and auto-generated project updates fire through your Linear board faster than any small team can review them, and the wrong one going out is the one that confuses a client or closes a ticket that wasn't ready.
When Linear runs unsupervised
Project management automation moves fast, and the mistakes it makes are public to your whole team the moment they ship.
- LINEAR_ISSUE_UPDATED_TRIGGER fires a reassignment across 20 open issues before you realize the rule was too broad.
- Create a comment posts a client-facing status note that references the wrong milestone, and it goes out before anyone reads it.
- Update issue marks a batch of tickets Done while two of them are still actively blocked.
- Delete issue removes a card a teammate was mid-work on, with no undo prompt and no warning.
- Create Project Update publishes a progress summary that reflects stale data from earlier in the week.
What Rills does inside Linear
Rills watches your Linear triggers and queues every proposed action for your review before anything posts or changes. Whether the AI wants to run a Search Linear issues pass and bulk-update states, or fire a Create Project Milestone based on a closed issue cluster, it puts the proposal in front of you first.
The issue updates still happen; you just see exactly what's changing before it goes out.
When Linear events should and shouldn't act on their own
Not every Linear automation trigger carries the same risk. Some are routine enough to approve once and graduate; others touch things that need a human every time. Linear automation works best when you draw that line deliberately.
- LINEAR_ISSUE_CREATED_TRIGGER: safe to graduate for internal triage labels on predictable issue types, where the cost of a wrong label is low.
- LINEAR_COMMENT_EVENT_TRIGGER: routine enough to auto-approve for internal bot summaries, but should always wait for your call before posting anything client-visible.
- LINEAR_ISSUE_UPDATED_TRIGGER: almost always needs a human; a bulk state change or reassignment hitting the wrong issues is hard to walk back and visible to the whole team immediately.
What wakes Rills up in Linear
When these events fire, Rills proposes the next move and waits for your call.
LINEAR ISSUE CREATED
Fires when someone creates a new issue in Linear. Use this to automatically notify teams, log the issue in other systems, or start a workflow.
LINEAR ISSUE UPDATED
Fires when any aspect of an issue changes, such as its status, assignee, labels, or priority. Use this to keep other tools in sync or trigger actions based on issue progress.
What Rills can do in Linear
6 of 33 actions across reads, writes, and updates.
- 01
Create a comment
Add a comment to a specific Linear issue to provide updates, ask questions, or collaborate with your team on issue discussions.
- 02
Create linear issue
Creates a new issue in your Linear project with customizable properties like title, description, assignee, priority, and due date. Use this to capture work items, bugs, or feature requests directly into your project management system.
- 03
List Linear issues
Retrieves a list of all non-archived issues across your Linear workspace or within specific projects, allowing you to view active work items and filter by assignee. This gives you a quick overview of what needs to be done and who's responsible for each task.
- 04
Search Linear issues
Quickly find specific issues across your Linear workspace by searching for keywords, issue IDs, or text within issue titles and descriptions. This helps you locate relevant work items without manually browsing through lists.
- 05
Update issue
Modify an existing issue's details such as title, description, status, assignee, priority, or labels to keep your project information current and reflect the latest progress or changes.
- 06
List linear projects
Retrieves all projects from your Linear workspace so you can view and manage your project portfolio. This gives you a complete snapshot of all active and inactive projects in one call.