Pricing

Rating

Developer

Actor stats

Categories

Share

GitHub Issue Lead Monitor

Find GitHub issues that reveal bugs, feature requests, migration pain, API problems, support demand, competitor gaps, and open-source product signals.

This Actor is built for developer lead generation, product research, support monitoring, competitive intelligence, and open-source trend tracking. It uses the public GitHub Search API, so runs are fast, low-cost, and do not need a proxy by default.

What It Returns

• GitHub issue title and URL
• Repository, issue number, state, labels, and author
• Comment count, created time, updated time, and closed time
• Source query or source repository
• Relevance score and matched source terms
• Intent score and matched bug/support/feature keywords
• Optional bot-user exclusion
• Optional issue body
• Monitoring mode for newly discovered issues

Common Uses

• Find people struggling with a product, API, or integration
• Monitor open issues for a competitor or ecosystem
• Track migration problems after SDK/API changes
• Discover feature requests and product gaps
• Build developer prospecting lists from public issue data
• Watch open-source trends around frameworks, APIs, and tools

Input Tips

Use specific query phrases and repositories.

Good query examples:

• stripe webhook error
• shopify api issue
• openai api timeout
• postgres migration error
• firebase alternative
• hubspot api bug

Good repository examples:

• vercel/next.js
• facebook/react
• openai/openai-node

Use state = open for fresh support/lead opportunities. Use sort = created for newest issues and sort = updated for active monitoring.

The default minimumRelevanceScore is 2 and excludeBotUsers is enabled so the output avoids generic matches and common automation accounts.

GitHub Token

The Actor can work without a token for light public searches, but a GitHub token is recommended for reliable production runs.

GitHub's public Search API is rate-limited, and shared cloud IPs may hit that limit quickly. For 500+ result runs, frequent schedules, or many search sources, provide a GitHub token in the hidden githubToken input.

No proxy is needed. The token is for API rate limits, not bypassing blocks.

Result Limits

maxResults is a maximum cap, not a guarantee. The Actor only writes rows that pass your relevance, state, date, and intent filters.

Use maxResultsPerSource when you provide several queries/repositories and want balanced output. For example, with maxResults set to 500 and 5 sources, set maxResultsPerSource to 100.

Without a GitHub token, keep runs small: one or two focused sources and lower pagesPerSource. With a token, larger 500+ result runs are much more reliable.

The minimum maxResults is 50 so runs are commercially practical and users are charged for meaningful output.

Monitoring

Enable monitorChanges to compare the current run against the previous snapshot in the Actor key-value store.

When onlyChanges is enabled, the dataset contains only newly detected issues. When it is disabled, the dataset contains the current full result set while the change snapshot is still stored for automation.

Proxy Use

No proxy is needed by default. This Actor uses a public API and does not run a browser, which keeps speed high and usage cost low.

Output

Each dataset row represents one GitHub issue. The primary output event is one dataset row.

Notes

This Actor is not affiliated with GitHub. It reads public GitHub Search API results and stores structured rows in your Apify dataset.