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.

[PostHog] Add custom SMTP provider support for workflow email sends

Workflow email sending is limited to a single built-in provider, preventing users from leveraging their existing SMTP infrastructure or preferred email services. This hinders adoption for teams needing to send emails from their own domain.

Original Source

@@dmarchuk | 1 pts | 3d ago

### Feature request ### Feature request # Custom SMTP Provider Support for Workflow Email Sends Feedback: https://posthog.com/questions/custom-smtp-support ## Problem Currently, workflow email sending only supports a single built-in email provider. Users who have existing email infrastructure (e.g. their own SMTP server or a preferred email service) cannot use it for workflow email sends. This blocks adoption for teams that want to send workflow emails from their own domain/provider for compliance, deliverability, or branding reasons. ## Proposed Solution Allow users to configure a custom SMTP server as an email provider for workflows. This would involve: 1. Adding SMTP as a supported provider in the email integration setup 2. Allowing users to configure SMTP host, port, credentials, and TLS settings 3. Domain verification flow for custom SMTP providers ## Why this matters - Unblocks users who want to migrate their workflows to PostHog but need custom email infrastructure -

Discussion

Loading comments...