Implemented
1
Make emails readable: store & render the HTML (or at least render markdown)
Source: twentyhq/twenty#27224 · opened by @jjpshorg
Hi, The issue. Emails in Twenty are often unreadable. The reader shows the raw stored text, with no rendering — you see markdown syntax and sender artifacts, for example: • [Privacy policy]( — marketing tools; • Sent with [Mail App]( — a signature added by the sender's mail app; • tracking URLs wrapped in < > — bulk emails. Why. Twenty only stores the text version of the message (text): the email's text part when present, otherwise an HTML-to-text conversion. And the reader renders that text as-is (pre-line + auto-linkify), interpreting neither markdown nor HTML. What we'd need. 1. Store the message HTML (in addition to the text) and render it (sanitized) in the reader — that's what an email client does; 2. failing that: render the markdown of the stored text; 3. ideally: an "Open in Gmail" action per message. Use case. Our exchanges (sponsors, partners, customers) are tracked in Twenty; if emails are unreadable there, we hav…
No pledges yet. Be the first to back this.
Comments
Similar requests
Synced messages only store a plain-text extract; HTML-only emails end up empty or truncated
2 votes · 0 comments
Feature Request: Surface emails from Opportunity-linked People in the Opportunity Emails tab
3 votes · 0 comments
Attach emails and meetings to tasks / custom objects (1-to-N exchanges)
1 vote · 0 comments
Enable the Emails / Calendar reader on custom objects (the read path already looks generic)
1 vote · 0 comments
Add conditional field formatting for numeric table and record fields
3 votes · 0 comments
No comments yet.