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.

[Twenty CRM] Return threadId and messageId from Send Email Action

When sending follow-up emails, users need to thread the follow-up in the same email conversation. The Send Email action currently does not return Gmail/email threading identifiers, making this impossible.

Original Source

@@eliefrancois | 0 pts | 3/15/2026

## Scope & Context We are using Twenty CRM workflows to send automated outreach emails. When sending follow-up emails (either via Twenty workflows or external tools like n8n), we need to thread the follow-up in the same email conversation as the initial outreach. Currently, the Send Email action does not return Gmail/email threading identifiers, making it impossible to programmatically reply in the same thread. --- ## Current Behavior The Send Email workflow action returns only basic metadata: ```json { "subject": "Quick question about your seniors' college apps", "recipients": ["contact@example.com"], "ccRecipients": [], "bccRecipients": [], "attachmentCount": 0, "connectedAccountId": "6085b931-6277-470a-86de-538f22467b5f" } ``` **Missing:** `threadId`, `messageId`, and other email identifiers needed for threading. --- ## Expected Behavior The Send Email action should return the email provider's message identifiers: ```json { "subject": "Quick question about y

Discussion

Loading comments...