9 Commits

Include renames

Author	SHA1	Message	Date
5 people	e81152608d	fix: Issue with processing variables in outgoing email content (#12799) ... Co-authored-by: Shivam Mishra <scm.mymail@gmail.com> Co-authored-by: Vinay Keerthi <11478411+stonecharioteer@users.noreply.github.com> Co-authored-by: Sojan Jose <sojan@pepalo.com>	2025-11-10 20:50:02 +05:30
3 people	ce400a36d7	feat: Always process email content (#12734) ... Co-authored-by: Muhsin Keloth <muhsinkeramam@gmail.com>	2025-10-30 13:36:39 +05:30
3 people	368d7c4608	feat: Add support for HTML emails in outgoing messages (#12662) ... This PR adds sending custom HTML content in outgoing email messages through Chatwoot's Email channels, while maintaining backward compatibility with existing markdown rendering. ### API Usage **Endpoint:** `POST /api/v1/accounts/{account_id}/conversations/{conversation_id}/messages` ```json { "content": "Fallback text content", "email_html_content": "<div><h1>Welcome!</h1><p>This is <strong>custom HTML</strong></p></div>" } ``` --------- Co-authored-by: Muhsin <muhsinkeramam@gmail.com>	2025-10-15 13:22:23 +05:30
3 people	b9694a0818	feat: support reply to for Telegram (#8105) ... Co-authored-by: Muhsin Keloth <muhsinkeramam@gmail.com>	2023-10-20 13:14:20 +05:30
Sojan JoseandGitHub	7ab7bac6bf	chore: Enable the new Rubocop rules (#7122) ... fixes: https://linear.app/chatwoot/issue/CW-1574/renable-the-disabled-rubocop-rules	2023-05-19 14:37:10 +05:30
3 people	026e03c307	fix: Handle spaces in CC/BCC email lists (#6788) ... When the CC field is generated in the UI, the email values are joined together with ", " but when they are parsed, we currently split by just ",". This causes an error on the backend and on the frontend. It seems reasonable to update the code to allow whitespace in the input and to split by `\s*,\s` and also to trim leading and trailing whitespace from the CC list. --------- Co-authored-by: Sojan <sojan@pepalo.com>	2023-04-18 19:18:23 +05:30
Tejaswini ChileandGitHub	5cce04da78	Chore: specs for process_emails in message builder (#6379)	2023-02-02 18:36:52 +05:30
3 people	af020f446e	fix: check the content type for the file when uploading from cloud storage (#5378) ... When sending the message with audio, only the signed id of the file is sent. In the back end check only the UploadedFile type. The attachment has the default file type image, now it gets the content type from the signed id Fixes: #5375 Co-authored-by: Sojan Jose <sojan@pepalo.com>	2022-10-21 18:05:36 -07:00
Sojan JoseandGitHub	8079bf50a0	Feature: API Channel (#1052)	2020-07-21 12:15:24 +05:30