New issue or pull request

Start the workflow when an issue or a pull request is opened, or updated, in a GitHub repository.

A polling trigger

It checks for new items on a timer while the workflow is On, in the browser extension. Read Polling triggers for the first check, test events and what happens when a check fails.

Needs a New issue or pull request connection — 

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

Create a connection →

What it does

Every Check every minutes, the trigger reads the repository’s latest issues or pull requests (Watch) and starts one run with the new ones. With Start a run when one is set to Updated, every new change to an issue counts again. The issue trigger never starts a run for a pull request.

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

• Post new issues to a team channel.
• Label or triage new pull requests with AI.
• Copy new issues to Linear or Todoist.

Inputs and settings

Setting	Type	What it does
Connection REQ(required)	Credential
Repository REQ(required)	One of several shapes	owner/repo, or paste its link.
Watch	Choice	Options: Issues, Pull requests. Default: Issues
Start a run when one is	Choice	Options: Opened, Updated. Default: Opened
Check every	Number	At least 1 minute, only while the workflow is On. Default: 5
On the first check	Choice	Options: Skip what’s already there, Start with the latest. Default: Skip what’s already there
How many to start with	Number	For “Start with the latest” and Fetch test event (1–20). Default: 3

Repository takes owner/repo, or paste the repository’s link.

Outputs

• Output

Each run returns a list of items with these fields:

Field	Type	What it holds
id	Number
number	Number
title	Text

Shape of an output item

[
  {
    "id": 0,
    "number": 0,
    "title": "…"
  }
]

One item per issue or pull request, as GitHub returns it (number, title, html_url, user, labels…).

Dependencies and credentials

• Connection (connection, Bearer Token): required. See Create a connection.

Example workflow

1. New issue or pull request, Watch Issues, Opened.
2. Text Classifier sorts it into bug / question / idea.
3. Slack posts it to the matching channel.

Common issues

• “Repository: use owner/repo.”: type it as owner/repo, or paste the full link.
• GitHub answered 404: the connection’s token can’t see that repository.

Related nodes

• Polling triggers: how every “New …” trigger checks.
• GitHub: work with issues, pull requests and repositories.
• Schedule Trigger: run at fixed times instead.