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.

[TDI Website] Automate New Creator Onboarding from Intake Form Submission

Automate the new creator onboarding process, which is currently manual after submission via the website intake form (Web3Forms). The automation should add new creators to the portal and notify the team, eliminating manual steps like running Claude Code prompts and copying Slack messages.

Original Source

@@tdi-ai-create | 0 pts | 3d ago

## Summary When a new creator applies through our website intake form (via Web3Forms), the entire onboarding process is currently manual. We need a strategy to automate this pipeline so new creators are added to the portal and the team is notified without requiring Rae to manually run Claude Code prompts and copy/paste Slack messages every time. ## Current Manual Workflow Every time a new creator application comes in, here's what happens today: 1. **Rae receives an email** from Web3Forms with the intake form submission (name, email, strategy, referral source, content types) 2. **Rae pastes the submission into Claude** to generate a Claude Code Prompt (CCP) 3. **Rae runs the CCP in Claude Code**, which: - Inserts a new record into the `creators` table in Supabase - Auto-generates all `creator_milestones` records (first onboarding milestone unlocked, rest locked) - Adds a `creator_notes` record with a summary of the intake form submission (author: "Rae", associated with onbo

Discussion

Loading comments...