Engineering integration guide
Linear + UbiGrowth workflows
Linear is an issue tracking platform built for product and engineering delivery cycles. This guide covers the records that matter, how the connection should be scoped, and what the first bounded workflow should be.
Introduction
Make Linear part of the workflow, not another silo.
Validate connector availability for your workspace
This guide covers how a team designs a engineering workflow around Linear with UbiGrowth: which records stay authoritative, how the connection should be scoped, what the first bounded workflow should be, and how to tell whether it worked.
The records that matter are Issue, Project, Cycle, Team, Label, Workflow State, and Roadmap. Linear scopes Workflow States to a Team, so "In Progress" on one team is a different state object from "In Progress" on another. Cross-team reporting has to map states rather than compare names.
Linear is not currently on UbiVibe's verified connector list. This page is an implementation design reference: use it to specify the workflow, then validate whether the connection is available and correctly scoped for your workspace before you make it a dependency. The verified UbiVibe connections today are Salesforce, HubSpot, Gmail, Google Drive, Slack, and GitHub.
Launch is the usual destination for this connection, because the value shows up as a tool, dashboard, or internal surface built on the connected data.
Why teams evaluate this connection
Integrations create value when they remove operating friction.
The first design decision is not which API endpoint to call; it is which system owns the record, what event should trigger work, who owns the exception path, and what successful completion means.
Engineering systems produce more signal than any other part of the business and the least usable summary. Linear knows exactly what happened; turning that into something the rest of the company can act on is manual work that nobody owns.
The second problem is direction of risk. An integration that reads engineering activity is low-risk and useful. An integration that can act on infrastructure or production systems is a different category entirely, and the two are often discussed as if they were the same project.
You're likely here because
- Engineering activity is invisible outside the engineering team
- Incident context has to be reassembled manually every time
- Internal tool requests sit behind product work indefinitely
Record model
What a Linear integration actually reads and writes.
Integration design starts from the objects the system really exposes, not from a generic connector diagram. These are Linear's.
Identity and matching
Linear scopes Workflow States to a Team, so "In Progress" on one team is a different state object from "In Progress" on another. Cross-team reporting has to map states rather than compare names.
Start here
Read Issues in the current Cycle that have not changed state past the team's own expectation and surface them at standup with context.
What this will not do
It will not carry a service desk. Linear models product work; customer requests need a system that models the requester.
The constraint to plan around
The GraphQL API meters by complexity and requires explicit pagination on every connection, so an under-specified query returns a page and looks like the whole answer.
Build notes
What you actually have to reason about in Linear.
The fields that carry meaning, how the connection authenticates, and whether the event surface can be trusted. This is the part that decides whether the integration works in month three.
| Field | Why it matters |
|---|---|
| state id | workflow states are per team, so identical names across teams are different objects |
| state type | backlog, unstarted, started, completed, canceled — the portable abstraction for cross-team reporting |
| cycle | the time-boxed unit; issues move between cycles and the history matters |
| estimate | optional and per-team, so velocity comparisons across teams are not meaningful |
| identifier (ENG-123) | the human handle, stable and distinct from the internal UUID |
Authentication
Personal API key or OAuth for apps, with access scoped by workspace membership. Linear's permission model is comparatively simple, which means a key grants broad workspace read by default.
Events and delivery
Webhooks deliver issue, comment, and project events with signature verification. Linear's events are timely and complete enough that polling is rarely justified.
Workflow
How the Linear workflow runs.
The operating sequence, from reading the source system through to the result landing back where it belongs.
Step 01
Connect read-only first
Linear is connected with scoped, read-only credentials so context and reporting value can be proven without any action risk.
Step 02
Assemble the engineering picture
Delivery, incident, or operational activity is summarized in a form the rest of the business can act on rather than a raw feed.
Step 03
Build the internal surface
Launch produces the dashboard or internal tool that was never going to clear the product backlog, reviewed like any other internal service.
Step 04
Bound any action path
If the workflow needs to act, that path is specified separately with explicit scope, approval, and a record of what ran.
Design decisions
The engineering decisions this connection forces.
Each of these has to be settled before the Linear workflow is allowed to write anything.
Step 01
Separate read from act
Reading Linear for context and reporting is a different risk decision from letting a workflow act on it. Do not bundle them into one project.
Step 02
Make execution paths explicit
Any action that reaches a real environment should run through a reviewable execution path with a record of what ran, not an implicit side effect.
Implementation path
How to implement the Linear workflow.
- 01
Start read-only against Linear and produce something the team already wants: delivery visibility, incident context, or an operational summary.
- 02
Use scoped credentials rather than a shared token, and confirm what the scope can actually reach.
- 03
Build the internal surface in Launch, and review the result as you would any other contribution.
- 04
After cycle-stall surfacing works, add estimate-versus-actual per team so the planning conversation has evidence rather than opinion.
Governance
Controls that matter.
Control 01
Credentials are scoped and workspace-approved; no shared secret belongs in a prompt or in generated code.
Control 02
Actions that reach production systems run through explicit, reviewable execution paths.
Control 03
Generated code and configuration are reviewed on the same terms as any other change.
Failure modes
How a Linear integration breaks in production.
Not generic integration advice. These follow from how this system actually behaves, which is why they look nothing like the list on the next guide over.
Symptom 01
Cross-team reporting shows impossible state transitions.
Cause
Workflow states are per team and were compared by name.
Fix
Map to state type — backlog, started, completed — which is the portable abstraction.
Symptom 02
A query returns fewer results than expected and looks complete.
Cause
GraphQL connections paginate and the cursor was not followed.
Fix
Always follow pageInfo; a first page is never the answer.
Symptom 03
The backlog fills with automated issues nobody reads.
Cause
An integration files an issue per alert.
Fix
Aggregate into one issue per condition and update it, rather than creating per occurrence.
What changes at scale
The GraphQL API meters by complexity, so deeply nested queries fail where several shallow ones succeed. Design queries for the metering model rather than for elegance.
Examples
What a working Linear workflow looks like.
Bounded scenarios rather than a feature list. Each one can be verified against work the team already does.
Product delivery
With Linear connected read-only, delivery and operational activity can appear alongside commercial context instead of living in a separate report.
Internal tool that was stuck in the backlog
A small tool reading Linear gets built in Launch and reviewed like any other internal service, without consuming sprint capacity.
Limitations and considerations
What to validate before you depend on this.
- The GraphQL API meters by complexity and requires explicit pagination on every connection, so an under-specified query returns a page and looks like the whole answer.
- Automated issue creation is the standard way to make a backlog meaningless. An integration that files an issue per alert produces a queue nobody reads within two weeks.
- When the work is customer requests. Linear models product work and has no requester concept worth the name; a service desk needs a system that does.
- Write or action access to Linear is a materially different risk decision from read access and should be scoped, reviewed, and approved separately.
- Generated code and configuration still require review. Speed of production does not change ownership of what ships.
FAQ
Linear integration questions.
What records does a Linear integration actually work with?
The primary records are Issue, Project, Cycle, Team, Label, Workflow State, and Roadmap. Linear scopes Workflow States to a Team, so "In Progress" on one team is a different state object from "In Progress" on another. Cross-team reporting has to map states rather than compare names.
What should the first Linear workflow be?
Read Issues in the current Cycle that have not changed state past the team's own expectation and surface them at standup with context.
What will a Linear integration not do?
It will not carry a service desk. Linear models product work; customer requests need a system that models the requester.
What is the main constraint to plan around?
The GraphQL API meters by complexity and requires explicit pagination on every connection, so an under-specified query returns a page and looks like the whole answer.
What changes about a Linear integration at scale?
The GraphQL API meters by complexity, so deeply nested queries fail where several shallow ones succeed. Design queries for the metering model rather than for elegance.
How does authentication work for Linear?
Personal API key or OAuth for apps, with access scoped by workspace membership. Linear's permission model is comparatively simple, which means a key grants broad workspace read by default.
Does Linear support webhooks, and can they be trusted?
Webhooks deliver issue, comment, and project events with signature verification. Linear's events are timely and complete enough that polling is rarely justified.
What is the risk of writing to Linear?
Automated issue creation is the standard way to make a backlog meaningless. An integration that files an issue per alert produces a queue nobody reads within two weeks.
When is connecting Linear the wrong call?
When the work is customer requests. Linear models product work and has no requester concept worth the name; a service desk needs a system that does.
What should a Linear integration automate first?
Start with one bounded workflow that removes a measurable handoff, duplicate-entry step, reporting delay, or follow-up gap. Expand only after the first workflow is reliable.
Does UbiGrowth require Linear to be replaced?
No. The operating model is designed around connecting to systems that should remain authoritative and building workflows around them rather than forcing a wholesale replacement.
Is connector availability identical for every workspace?
No. Availability can depend on provider configuration, authentication, scopes, workspace setup, and deployment state. Validate the required connection before treating it as an operational dependency.
Can the workflow act on Linear, not just read it?
Action paths are possible but should be treated as a separate, bounded project with scoped credentials, explicit approval, and a record of what ran.
How are credentials handled?
Through workspace-approved, scoped grants. A shared secret pasted into a prompt or embedded in generated code is not an acceptable pattern.
What is a safe first integration?
A read-only workflow that produces something the team already wants from Linear — delivery visibility or incident context — before any action path is considered.
How this access is governed
What ARIA is allowed to do in Linear, and who decides.
Connecting Linear is a permission decision, not just a setup step. These are the controls that decide what ARIA can reach, what it can change, what gets recorded, and how you take the access back.
Required permissions
ARIA works through the scopes the connection was granted, and no others. Authorization happens at the provider, so the permissions being requested are shown by the system itself before anything is connected.
What it can reach
Reachable systems are the intersection of what your organization approved in the connector registry and what the requesting identity is permitted to use. Identity resolves before execution, not after.
What it can do
Actions run through explicit execution paths with state, spend, and failure boundaries — a bounded worker path rather than an open-ended agent loop with a credential.
Credential handling
Credentials live in the governed connection layer and are resolved through canonical connection identity. They are not pasted into individual workflows, prompts, or generated artifacts.
Action logging
Execution carries state and traces: what triggered the work, which connection it used, and what came back — including an explicit failure when something did not run.
Approval and revocation
Consequential actions can be made to require a person to approve them. Access can be changed or revoked at the connection, and ARIA loses that reach without unpicking the work already completed.
Start with ARIA
Ask ARIA to run this integration.
Describe the outcome you need across this system. ARIA works out the scopes, data, and actions the job requires, and operates inside the access you grant — which you can change or revoke.
- ARIA acts only through the systems and permissions you connect.
- Connections use scoped credentials you can change or revoke.
- Actions are recorded, and consequential ones can require approval.
Start here
Turn the integration into a working business outcome.
Start with ARIA to describe the outcome, then continue into the product path that fits the workflow. Connector availability and required scopes should be validated for the specific workspace before production use.