Newsletter/TemplateId
I moved my thread from Feature-suggestions to questions
https://github.com/wasp-lang/wasp/issues/1553
Hey has this been solved or will this just be closed as not possible? I was trying to use templateId, I guess I could just make a html but would be cooler if I could use templateId from SendGrid.
I solved this by using
export const registerTemplate = "my html file" and made my html template through sendgrid.
import { registerTemplate } from './templates/register-template';
export const getVerificationEmailContent: GetVerificationEmailContentFn = ({ verificationLink }) => {
const html = registerTemplate.replace('{{verificationLink}}', verificationLink);
return {
subject: 'Welcome to myappname!',
html,
text: Please verify your email by clicking this link: ${verificationLink}
};
Also about creating a newsletter, I still think this would be cleaner if I did this via sendgrid or hubspot or?
Is there any guidelines/best practices about how you all do newsletters?GitHub
[Email sender] Allow specifying provider specific options, like tem...
Right now, when defining an email sender, and when sending an email via it, we don't allow any provider-specific options. It would be useful to provide some, because for example, users using Se...
2 Replies
Hi @VS. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Thank you for your question about email templates and newsletters in Wasp. Let me address your points based on the available information:
1. Regarding the use of templateId from SendGrid:
Currently, Wasp does not directly support provider-specific options like templateId for SendGrid. This feature is still an open issue, as mentioned in GitHub Issue #1553 (https://github.com/wasp-lang/wasp/issues/1553). The ability to specify provider-specific options is planned for future implementation, but it's not available yet.
2. Your workaround:
The solution you've implemented, using a custom HTML template and replacing placeholders, is a good approach given the current limitations. This method allows you to use your SendGrid template while working within Wasp's current capabilities.
3. Newsletter functionality:
Wasp doesn't have built-in newsletter functionality. For newsletters, it's generally recommended to use specialized services like SendGrid, Mailchimp, or similar platforms. This approach is supported by community suggestions in a Discord thread where members recommended using Mailchimp or Sender.net for newsletter services (https://discord.com/channels/686873244791210014/1214904014865571890).
4. Best practices for newsletters:
Wasp doesn't provide specific guidelines for newsletters. The general recommendation is to use dedicated newsletter services. These platforms offer features like list management, analytics, and compliance with email regulations, which are crucial for running effective newsletter campaigns.
5. Future improvements:
The Wasp team is aware of the need for more flexible email templating options. There's an open issue discussing the introduction of a templating system for writing emails in Wasp (https://github.com/wasp-lang/wasp/issues/1132), which might address some of these concerns in the future.
For now, your approach of using a custom HTML template is a good workaround. For newsletters, considering a dedicated service would be the most straightforward option until Wasp potentially introduces more comprehensive email features.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @VS, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
Hey has this been solved or will this just be closed as not possible? I was trying to use templateId, I guess I could just make a html but would be cooler if I could use templateId from SendGrid.Using
templateId with SendGrid is an open issue for us
https://github.com/wasp-lang/wasp/issues/1553
Also about creating a newsletter, I still think this would be cleaner if I did this via sendgrid or hubspot or?We don't really have any official recommendation, I'd say using a dedicated service for the newsletter sounds cleaner to me - you'll get nicer tooling and you won't build many things yourself. @matijash might have some suggestions for which newsletter service to use
GitHub
[Email sender] Allow specifying provider specific options, like tem...
Right now, when defining an email sender, and when sending an email via it, we don't allow any provider-specific options. It would be useful to provide some, because for example, users using Se...