Mail component for other providers?
So currently you have Resend but there are lots of other providers out there that could have a same implementation as the current component apart from the actual API. Why not make it pluggable? That way we could easily implement the api interface and the “email” component can handle the internals like scheduling, rate limiting etc. Would be happy to help.
2 Replies
Thanks for posting in <#1088161997662724167>.
Reminder: If you have a Convex Pro account, use the Convex Dashboard to file support tickets.
- Provide context: What are you trying to achieve, what is the end-user interaction, what are you seeing? (full error message, command output, etc.)
- Use search.convex.dev to search Docs, Stack, and Discord all at once.
- Additionally, you can post your questions in the Convex Community's <#1228095053885476985> channel to receive a response from AI.
- Avoid tagging staff unless specifically instructed.
Thank you!
Provider specific is probably the path for now, but you could fork the resend repo and augment it to use a different provider (or to be generic/pluggable if your own needs are that broad).