Hi everyone,
I’m experiencing an issue with the new Gmail module.
Previously, I used the legacy Gmail module without any problems. Now, using the new Gmail module, whenever I send an email with accented characters in the subject line, it shows up incorrectly. For example:
"Olá Matrículas" → "Olá MatrÃculas"
The same happens with my name in the sender address (where accented characters appear garbled).
Interestingly, the email body displays perfectly, with all accented characters showing as they should.
Has anyone else faced this encoding issue? Is there a way to explicitly enforce UTF-8 encoding for the subject and sender fields in the new Gmail module?
Thanks in advance for any tips or solutions!
2 Likes
I also have the same problem.
Hi !
Same for me !
I also have a problem with my HTML signature with a lot of space.
I dont have this problem with old Gmail modules that i will not update until those 2 problems are solved.
Thanks
Hello 
Thank you so much for bringing this to our attention. 
Our development team is already working on resolving the issue, and we expect to have a fix released shortly. We’ll be sure to keep you updated on the progress.
In the meantime, you can continue using the legacy version of the app via this link.
We truly appreciate your patience and understanding. Please don’t hesitate to reach out if you have any further questions or concerns. 
3 Likes
It seems the new gmail module was pulled from the list. Please inform us, as we rely on Make.com to create reliably automations. I get the feeling the new Gmail module was a hasty job and not ready for prime time.
Dear Users,
We’re sorry to hear you’ve had a suboptimal experience with the new Gmail version. We genuinely appreciate your feedback and are taking it very seriously.
Our goal is to provide the best possible app experience, so we’ve paused the rollout of the new Gmail version to new users. We’re actively analyzing your feedback and exploring solutions to bring you an improved app as soon as possible.
Important Information for Existing Users
The new Gmail version (V4) is now marked as Beta. If you’ve already added it to your scenarios, it will remain available to you. We’d be grateful for any further feedback you can share here on our Community forum or the Make Idea Exchange.
We strongly advise against using the Beta Gmail version (V4) for production use cases. Since your feedback may lead to significant changes, we recommend sticking with the previous stable version (V2) for your critical automations. The V2 version remains fully functional and reliable.
You can easily select which version you want to use when adding a module to your scenario, as shown in the screenshot below:
Once we’re confident we’ve addressed your feedback and the new version is stable, we’ll remove the Beta label.
As the Group Product Manager responsible for apps on Make, I want to assure you that we are fully committed to resolving these issues and delivering a superior experience. If you have any questions, please don’t hesitate to contact us.
Sincerely,
Jan Knettig
2 Likes
I do not have and option to change version!
Hi @Seleslav ,
based on your screenshot, what you are seeing is the old V2 version. If you don’t see the version selector, you are running the V2 version at this moment. Only users who have already the new V4 Beta version in their scenario would see the version selector and could choose between the 2.
If you had it but then you removed it from a scenario or deleted a scenario which included it, you are likely not to see the new V4 Beta version in your Make account.
To clear out any doubts, if you are seeing exactly this when adding a Gmail module to a new scenario, you are seeing the old V2 version:
If you are among the ones already using the V4 Beta version, you would see this:
Hope this helps. Let us know if you have further questions.
1 Like
Dear users,
I am very sorry for misleading information in the previous message but the behavior is slightly different than what I described above. If you already use any module of the new Gmail V4 app in any scenario, you can keep using that module in that scenario (migrating to V2 is still recommended for production use cases). Yet, when adding a new module you would only be able to add modules from the stable V2 version and you won’t see any version selector. This selector is only visible to you if more than one version is published which is not the case now. Only the stable V2 version is published at this moment.
As you can see on the below screenshot, if you are already using a Gmail V4 module in your scenario, you should be seeing the green arrows prompting you to change version to the latest published version. In this case this would be actually the older, stable version of Gmail V2. When adding a new Gmail module in the same or new scenario, the module selection you see is modules of Gmail V2 version.
To clear out any doubts - if you see the green arrows, you are likely using the new Gmail V4 version (you could also be using a legacy V1 version but there are not many users on that version anymore, so chances are low). If you don’t see the green arrows, you are on version 2 = the stable version.
If you wanted to be absolutely sure, you could use the Make DevTools and the tool of “Get app metadata”. Running this tool would produce JSON output in which you could clearly see the version. See screenshot.
Hope this helps. Once again, really sorry for any inconvenience this misleading information caused. If you have any questions, don’t hesitate to reach out.
1 Like
