RequestHunt is a community-driven platform that collects and curates feature requests from X (Twitter), Reddit, and GitHub. We help product teams discover what features real users are asking for, making it easier to validate product ideas and prioritize feature development based on actual user demand.

How does RequestHunt collect feature requests?

RequestHunt uses AI-powered extraction to automatically collect feature requests from social media platforms including X, Reddit, and GitHub. The platform monitors discussions, issues, and posts to identify genuine user feature requests, extracting key information like the requested feature, product mentioned, and user sentiment.

Who uses RequestHunt?

RequestHunt is used by product managers, founders, developers, and product teams who want to discover what features real users are requesting. It's particularly valuable for startups looking to validate ideas, established companies prioritizing their roadmap, and developers building products that solve real user problems.

Is RequestHunt free to use?

Yes, browsing and searching feature requests on RequestHunt is completely free. We also offer API access for developers who want to integrate feature request data into their own applications. Check our pricing page for API plan details.

How often is RequestHunt data updated?

RequestHunt continuously collects feature requests from Reddit, X (Twitter), and GitHub. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[Grouparoo] Implement Query Sources v2

The current query sources (v1) are inefficient and limited, as they require a query per property and cannot serve as primary sources. A new version (v2) is requested where a single root query defines properties from its selected columns.

Original Source

@@bleonard | 0 pts | 1/5/2022

### Is there an existing issue for this? - [X] I have searched the existing issues ### Is your feature request related to a problem? Please describe. The original iteration of query sources was a query per property; however, these can not be used as a primary source because they need a `WHERE` clause and they lead to inefficiencies. ### Describe the solution you'd like. A new query source should have a query at the root. The `SELECT`ed columns would be properties. These should produce the data that is written to the Records and then sync'd as they are now. This source would be able to be used as a primary source or incorporate current property values and be a secondary source. It should be optional to do things incrementally as this is not always available. In the ideal case, it would also be able to be used in the Config UI and sample profiles. ### Describe an alternate solution. _No response_ ### Additional context _No response_

Discussion

Loading comments...