Integrations · Linear
A label or an assignment starts a change, scoped by team and project.
Write-back lands as the application, never under the name of the person who authorised it.
What starts work
Three events, and the only assignment that starts work.
A Linear issue scoped by team and project starts a change. Team and project are independent scopes and both must match — a project groups issues across teams, so it is a second axis rather than a synonym. An empty team means every team; an empty project means any, including none.
- 01
linear.issue.labeleda label is added to a Linear issue
scoped by team_key · project_id · label - 02
linear.issue.assigneda Linear issue is assigned to someone
scoped by team_key · project_id · assignee_id - 03
linear.issue.mentionsomeone mentions @devbyte on a Linear issue
scoped by team_key · project_id
What lands back
It writes back as the application actor: a Markdown comment on the issue per milestone, and a state change where you map one, resolved by name against the issue’s team. Issue bodies and comments arrive as data, never as instruction.
What you grant and why
Three scopes, and one we do not ask for.
Deliveries are verified against the deployment’s webhook secret and recorded once. The webhook is configured once per deployment and routes by workspace, so connecting is the whole of your setup.
- read
- To read the issue that started the change, and the teams, projects and users an automation can be scoped to.
- write
- To move an issue’s workflow state where an automation maps states.
- comments:create
- To post the write-back comment. Narrower than write on purpose: this is the permission that does the visible work.
- issues:create · optional
- Not requested by default. DevByte does not need to create Linear issues to run a change.
It acts as the application, never as the person who connected it.Until you set the assignee explicitly, the default is whoever authorised the app, so their own assignments start changes; tokens do not expire, so to rotate one you reconnect.
Label an issue this week.
Connect the workspace, scope an automation to a team, and put one label on the work nobody has time for.