GitHub Issue Monitor – public GitHub issues export and API

Give it a list of public GitHub repositories and get back one row per issue. Each row has the repository, issue number, title, state, labels, comment count, author and timestamps. You can filter by state, labels and last-updated date, and choose how results are sorted.

Pull requests can be included too. They are flagged with isPullRequest, so you can keep them or filter them out later. Schedule it to run daily and use the Updated since filter to get only what changed.

Why this one

• No login or token. It reads public issue data only, so there is nothing to set up.
• Clean, consistent records. Every row uses the same field names, so spreadsheets and dashboards don't break.
• Filters that match how you work. Pick open, closed or all issues, require labels like bug,good first issue, and set a date with Updated since.
• Many repositories in one run. Add up to 20 repositories as owner/repo or a full GitHub link.
• Bounded cost. Max items per repository (1 to 500) caps how much each repository can return.
• Simple pricing. $1.90 per 1,000 results, with no start fee. Runs that return nothing cost nothing.

Quick start

{
  "repositories": ["nodejs/node", "apify/crawlee"],
  "state": "all",
  "sort": "updated",
  "direction": "desc",
  "maxItemsPerRepo": 5,
  "includePullRequests": true,
  "includeBodyExcerpt": false
}

This returns the 5 most recently updated issues and pull requests from each repository. In a test run on 26 Oct 2026 it returned 10 records.

What you can use it for

Who	What for
Developer relations and open-source teams	Watch new and updated issues across the repositories you maintain
Engineering managers	Check the bug backlog of a key dependency before you upgrade
Product researchers	Gauge demand by label, comment count and reactions
Contributors and consultants	Find good first issue or help wanted work
Support teams	Send a daily digest of recently updated issues using Updated since

How to use it

1. Click Try for free.
2. In Repositories, add the public repositories to watch, for example nodejs/node or https://github.com/apify/crawlee. The limit is 20.
3. Set Issue state to open, closed or all.
4. Optionally add a Labels filter, such as bug,good first issue. An issue must carry all the labels listed.
5. Optionally set Updated since to a date like 2026-10-01.
6. Choose Sort by (updated, created or comments) and Sort direction (desc or asc).
7. Set Max items per repository, and turn on Include pull requests or Include body excerpt if you want them.
8. Click Start.

To track changes, schedule the Actor and set Updated since to the date of your last run.

What data you get

Each row is one issue or pull request. If you turn on Include body excerpt, a bodyExcerpt field with the first 500 characters of the description is added.

Field	What it is	Example
id	Repository and issue number	nodejs/node#66872
url	Link to the issue or pull request on github.com	https://github.com/nodejs/node/pull/66872
apiUrl	GitHub API link for the item	https://api.github.com/repos/nodejs/node/issues/66872
githubNodeId	GitHub's internal node ID	PR_kwDOAZ7xs88AAAABJhS0Iw
repository	Repository the item belongs to	nodejs/node
number	Issue or pull request number	66872
title	Title	url: use indexed appends in search params getAll
state	Open or closed	open
stateReason	Reason an issue was closed, if any	null
isPullRequest	True if the item is a pull request	true
isLocked	True if the conversation is locked	false
labels	Label names	["whatwg-url","author ready","needs-ci"]
assignees	Assigned users	[]
milestone	Milestone, if any	null
comments	Number of comments	4
reactionsTotal	Total reactions	0
author	Username of the author	rozzilla
authorAssociation	Author's relationship to the repository	CONTRIBUTOR
createdAt	When it was created	2026-10-20T09:35:05Z
updatedAt	When it was last updated	2026-10-26T16:14:55Z
closedAt	When it was closed, if it was	null
ageDays	Days since it was created	6
scrapedAt	When the record was collected	2026-10-26T16:15:11.817Z

Pricing

Event	Price
Result (one record saved to the dataset)	$0.0019

There is no start fee. Runs with no results cost nothing.

Run	Cost
100 results	$0.19
1,000 results	$1.90
10,000 results	$19.00

Good to know

• Data source. It uses the public GitHub REST API. Only repositories that are public can be read, and private repositories are never requested.
• Limits. Up to 20 repositories per run and up to 500 records per repository.
• Rate limits. No token is used, so GitHub's limit for unauthenticated access applies (roughly 60 requests per hour per IP address). If it is reached, the run stops and keeps what it has already saved.
• Missing repositories. Repositories that don't exist or aren't public are skipped with a warning.
• Empty results. Narrow filters, such as a rare label or a recent date, can return zero records.
• Pull requests. They are left out by default. Turn on Include pull requests to keep them.
• Freshness. Records show the state at collection time. Check scrapedAt, because issues can change afterwards.
• Run summary. A RUN_SUMMARY record in the key-value store has per-repository counts and any failures.
• Not affiliated. This tool isn't affiliated with or endorsed by GitHub.

FAQ

Do I need a GitHub token? No. It only reads public data.

Does the labels filter match any label or all of them? All of them. An issue must carry every label you list.

Why did I get pull requests in my results? GitHub lists pull requests alongside issues. Turn off Include pull requests to leave them out, or filter on isPullRequest.

Can I paste full GitHub links? Yes. Use owner/repo or https://github.com/owner/repo.

Getting the data out

Download the results as Excel, CSV or JSON from the Output tab. Send them to Google Sheets, Slack, Zapier, Make or webhooks from the Integrations tab. Every run is also available through the Apify API, and you can schedule runs from Schedules.

Questions or problems

Open an issue on the Issues tab and include the run link. I reply within one business day.

Related tools

• GitHub Public Release Monitor: track new releases from public repositories
• NPM Package Version Monitor: watch npm packages for new versions
• PyPI Package Release Monitor: watch PyPI packages for new releases