Tools
Linear
Issues, projects, cycles and comments — read, create and update.
Official site: linear.app
What it does
- List and search issues, filter by team, project, cycle, assignee or status
- Create and update issues, including assignee, priority, labels and status
- Read and post comments on an issue
- List and create projects, teams, cycles and labels
- Create and manage webhook subscriptions
Workspace-scoped, one key per organization — Linear ties an API key to a specific workspace rather than a specific person, so this connects once for the whole team rather than per-seat.
Why through Tulina
Most systems now publish their own way for a model to reach them, and that is a good thing — it is what Tulina connects to. The connection was never the hard part. Deciding who may use it, what it is allowed to return, and what the model knows before it asks: that is.
The keys stay in one place
Connect Linear once. The credential is encrypted in a vault, never held in clear, and never pasted into a chat or a workflow file. A person uses their own key where they have one, their team's where they do not, the organisation's after that — so nobody is blocked and nobody is handed more access than they need. Revoke it once and everything running on it stops.
What leaves is filtered before it leaves
Roles decide who can reach Linear at all. Beyond that, a policy on the connector itself decides what comes back: fields dropped, identifiers masked or hashed, people pseudonymised. The data is minimised at the source rather than after it has already reached a model.
Every call is on the record
Runs are logged for the organisation — what was called, by whom, when. That is what makes an automated action reviewable after the fact, and what a security review asks for first.
The run starts knowing your company
A direct connection gives a model access. It does not tell it how your company names things, which accounts matter, or what was decided last quarter. Tulina carries that across every tool, so the same request against Linear returns something usable instead of something generic.
Processes that run on Linear
Call feedback becomes tickets and docs
Every call recorded during the day is distilled overnight, with bugs and feature requests routed to the right team as tickets and docs, plus a Friday digest.
Merged PRs move tickets and post a digest
Every pull request that lands gets matched to its ticket, moved forward on the board, and rolled into one summary for the team.
Prepare for a customer call
Before the call, the last conversations, the account's state, how the product is actually being used, and where their requested features stand, in one brief.
Revive deals that went cold
Deals lost more than 90 days ago come back with fresh signals, contacts checked for job moves, and the features they asked for that have since shipped.
Triage and route bug reports
An incoming report is read, matched against open issues to catch duplicates, and filed to the right team's board with severity attached.