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), GitHub, YouTube, LinkedIn, and Amazon. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[Power Automate] Expand native AI model choices for 'Run a prompt' action

User found native connector model choices limited for AI Actions in Power Automate, requiring complex workarounds to use models like Claude Opus. Request is to expand the range of natively supported AI models.

Original Source

@Suhail Sayed | 35 pts

Defaulting to Microsoft for answers always can cost you your Sanity. Here's what happened. We used the "Run a prompt" action within Power Automate for an AI Action. The customer did not like the output and the model choices on this native connector were limited. After some research, we determined that Claude Opus was the best model to run this prompt on. So what do I do? Start delving into Azure Foundry, read about it for an hour daily, request more time from the client and then go into foundry to set it up with this new found knowledge excitedly. Only to be met with a "REQUEST QUOTA" form. I submit the form which is pretty long and kinda nosey but I do it anyway. I don't get a confirmation on the request, no updates and we lose another week. Yesterday, it struck silly me that we could just directly sign up for Claude Console and get an API key without begging Azure Foundry for Quota. The fact that I lost 2 weeks over this because my brain was knee deep trying to solve it without stepping out of the Microsoft platform is kinda embarrassing. In 30 minutes, we were done setting up Claude, updating the flow and testing the results. I will need to be more conscious of this going forward and be comfortable to explore options outside Microsoft, you can still use Power Automate and just make API calls to external tools and bring the output back into the toolset. If you're thinking, Yes Captain Obvious! I know I know 🫢

Discussion

Loading comments...