---
title: New Linear issue
description: Start the workflow when an issue is created in Linear
---

Start the workflow when an issue is created in Linear, in every team or in one.

:::note\[A polling trigger]
It checks for new items on a timer while the workflow is **On**, in the browser extension. Read [Polling triggers](/concepts/flow/polling-triggers/) for the first check, test events and what happens when a check fails.
:::

Pick a saved connection in the **Connection** field, or create one from there. It signs in with a Bearer Token.

## What it does

Every **Check every** minutes, the trigger reads the latest issues and starts one run with the new ones. Fill **Team key** (for example `ENG`) to watch one team; leave it empty for every team.

A check that finds nothing new starts no run. Press **Run** to fetch a test event: the latest items, without moving the trigger's position.

## When to use it

* Announce new issues in a chat channel.
* Copy new issues to another tool.
* Ask AI to suggest a priority for each new issue.

## Inputs and settings

The **Team key** is the short prefix of the team's issue ids (`ENG-123` → `ENG`).

## Outputs

Each run returns a list of items with these fields:

```json title="Shape of an output item"
[
  {
    "id": "…"
  }
]
```

One item per new issue, as Linear returns it.

## Dependencies and credentials

* **Connection** (connection, Bearer Token): required. See [Create a connection](/app/connections/).

## Example workflow

1. New Linear issue, **Team key** `SUP`.
2. [Discord](/nodes/builtin/integration/discord/) posts the issue title and link.

## Common issues

* **Nothing runs for one team**: check the **Team key** matches the prefix of its issues.

## Related nodes

* [Polling triggers](/concepts/flow/polling-triggers/): how every "New …" trigger checks.
* [Linear](/nodes/builtin/integration/linear/): create and update issues.
* [Schedule Trigger](/nodes/builtin/trigger/schedule/): run at fixed times instead.