InfraNestInfraNest
Linear

Linear integration

Turn incidents into Linear issues that move to Done with them

InfraNest watches your sites, servers, domains, certificates and DNS. Connect Linear and switch on Issues for Incidents: each incident you choose opens an issue for the team you pick, linked back to it. Move it to Done and the incident hears about it; resolve the incident and the issue moves to Done. File any other problem in two clicks, with what InfraNest knows about it.

Start freeSee pricing

On Pro and up · 14-day Pro trial, no credit card · Connect in one click

  • Issues for incidents, moved to Done when they resolve
  • Any warning filed in two clicks, with the whole story
  • A warning when the problem may already have an open issue
  • Reviews published as Linear documents
Follow-up
  • OPS-142Checkout returning 503
    In ProgressPriya RaghunathanOpened 39 minutes ago
  • status.payrail.examplePayment gateway status: degraded API in eu-west
    linked · not kept in steplinked 33 minutes ago

Switch it on, and incidents open Linear issues that stay in step

Switch on Issues for Incidents and pick the team. Each new incident opens an issue there, titled after the incident with a link back: Urgent when it is critical, High when it is major, Medium otherwise. Resolving the incident moves the issue to your team’s own Done state. Moving the issue to Done in Linear adds a note to the incident and, by default, resolves it once the monitor passes again, so a closed issue never hides an outage that is still going on. Notes and comments copy both ways and never reach your public status page.

  • All incidents, only critical ones, or the monitors you choose
  • Priority set from how bad it is: Urgent, High or Medium
  • A repeat while the issue is open adds a comment, not a second issue
  • Send a test issue to see both directions work
One incident, one Linear issue
MonitorCheckout flow goes down — incident opened
LinearIssue opened for Operations, linked to the incident
LinearA comment on the issue lands on the incident
MonitorCheckout flow is back — the issue moves to Done

Moving the issue to Done first adds a note to the incident and, by default, resolves it once the monitor is back.

Hand any problem to Linear in two clicks

An incident, a monitor that is down, a server warning such as a port open to the internet, a domain about to expire, a certificate that failed to renew, DNS records changed outside InfraNest: open its menu and choose Create a Linear issue. The team you used last is already picked, and if you connected more than one tracker, the one you used last comes first. Once the issue exists, it sits at the top of the card with its key and state, and when the problem goes away the issue is told so, and finished if your connection finishes issues when incidents resolve.

  • From Home, monitors, servers, domains, certificates, DNS and incidents
  • The team you used last is already picked
  • The card shows the issue and its state, so the next person sees it
  • Already tracked elsewhere? Link the issue, or any page, instead
Many visitors cannot reach northwyndr.de
A port on api-01 is reachable without needOPS-151In Progress
Cloudflare does not encrypt the connection to the server behind northwyndr-app.devOPS-147Todo
No firewall protects cache-01OPS-153In Review

The whole story in the issue, and a warning before a second one

Before anything is filed, the dialog shows exactly what Linear will receive: for an incident, what failed, what changed just before and what has been tried so far; for a warning, what is wrong, how InfraNest knows and what to do. Both end with a link back and the name of whoever filed it. Command lines and anything that looks like a password are taken out first. If the problem already has an open issue, the dialog says so and adds a comment to it instead. While it is open, it also looks in Linear for an open issue about the same thing and offers to link that one.

  • What failed or what is wrong, and a link back
  • Command lines and anything that looks like a password taken out
  • A matching open issue offered before you file a duplicate
  • The person who acknowledged the incident suggested as the assignee

Follow-ups become Linear issues, and the review a Linear document

After an incident, your team writes the review in InfraNest: what happened, the impact, why it happened and what you will change. Each change becomes a Linear issue with one click, its state shown beside the line. Tick Linear document under Also publish to, pick the project, and the review is written there with what happened, the impact, why, each follow-up with its issue, the timeline and what changed just before. After the review is finished, every change you save updates the document a minute later.

  • Each follow-up filed in Linear, its state shown beside it
  • Published as a Linear document in the project you pick
  • Kept up to date as the review changes
  • A postmortem written in Linear can be linked instead, never copied
ReviewDraftPriya Raghunathan
  1. What happened
  2. Impact
  3. Why it happened
  4. What we change
What happened

API response times climbed from about 120 ms to over 4 seconds eight minutes after release 2.31 reached production. Sam rolled the release back, and latency was normal again 22 minutes after it started.

Impact

For 22 minutes most API requests took several seconds and about 6% timed out. Checkout and the dashboard were slow but stayed up; no data was lost.

Why it happened

The release included a migration that added an index without a lock timeout. On the primary database it waited behind long-running reads and held its connections open, so the pool ran out and requests queued behind it.

What we change · 2 follow-ups
  • Run schema migrations with a lock timeout, so a slow one fails instead of holding the primary database.ENG-87Done
  • Add a pre-deploy check that flags migrations expected to run longer than a minute.Create issue
Also publish to☑Linear document· Reliability☐Status page· Northwind Cloud Status
Save draftFinish review

Connect Linear to your own incidents

On Pro and up, with a 14-day trial and no credit card. Connect in one click and send a test issue to see the round trip.

Start freeRead the setup guide

Connect Linear in about a minute

Sign in with Linear and approve the workspace. Updates from Linear work from that moment, with nothing to set up there. Pick the team for incident issues and send a test issue.

  1. 1

    Connect your workspace

    Links InfraNest to Linear so issues can be opened in it — click Connect in Integrations, find Linear, and approve the workspace.

  2. 2

    Turn on issues for incidents

    Opens a Linear issue for every incident automatically — in Linear's Connections & settings, switch on Issues for Incidents and pick the Team.

  3. 3

    Send a test issue

    Confirms both directions work — opens and closes a real issue, then checks Linear reports the close back.

That’s it — Linear is connected.

Full setup guide

Set up with AI

I use Linear, and I want to connect it to InfraNest (infranest.io) — it manages domains, DNS, servers and certificates across providers. InfraNest asks for: Sign in with Linear, or a personal API key. Walk me through creating that in Linear: where each setting is in the current interface, whether a read-only option exists, and how to check it works before I paste it in.

Open in Claude Open in ChatGPT

MCP server

Linear in Claude and ChatGPT

Handling an incident from Claude or ChatGPT? Your assistant can file it in Linear with the details filled in and give you the link. It asks you first.

  • Acknowledge the Checkout incident and file it in Linear.
  • What caused this incident? Then file it in Linear for the team.
How it works Connect Claude or ChatGPT With Linear connected: Pro and up

Often connected together

CloudflareCloudflareDNS · SSL · Domains · AutomationGitHubGitHubAutomationWebhookWebhookNotifications · Automation

Questions about the Linear integration

#Does every incident open an issue, or only some?

You choose: every incident, only critical ones, or only on monitors you pick. The setting lives in Linear's Connections & settings and can be changed any time.

#What happens if the same incident happens again?

If the incident recurs while its issue is still open, InfraNest adds a comment to that issue instead of opening a second one, so a flapping monitor doesn't flood your Linear team with duplicates.

#Can InfraNest change anything on Linear's side?

InfraNest only creates and updates issues, comments and (if you publish a review) a document in a project you choose — it never changes your teams, workflows or other settings in Linear.

#What happens if the API key expires or is revoked?

The connection shows a red card and stops creating or updating issues until you replace the key; nothing already linked is lost, and reconnecting picks up exactly where it left off.

#What do I need before connecting Linear?

A Linear workspace, and either one-click sign-in or a Personal API key with Read and Write access that covers the team your issues go to — see the setup guide.

#Does InfraNest’s MCP server work with Linear?

Yes. With “Also let it act” switched on, your assistant can file an InfraNest incident in your connected Linear and give you the issue’s link. It asks you first, and an incident that already has an issue keeps it. The Linear integration is on Pro and up. Linear’s own MCP server works with your Linear issues. InfraNest’s brings the incident, its monitor and what changed before it into the same conversation.

Let the issue know what the incident knows

Create your account (it starts with 14 days of Pro), connect Linear in one click, and switch on Issues for Incidents. Your teams and workflows stay exactly as they are.

Start free

Free plan · No credit card required · Set up in minutes