[FEATURE REQUEST] Convex Resend Email Scheduling
Convex resend connection seems great so far, would love to see it expand to support resend scheduling, or handle the cron-schedules inside of convex rather than creating the delayed actions ourselves.
4 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!
One for @Jamie to think about for a future upgrade to the component maybe?
I marked as completed because we did talk about it a bit during the YT live stream 🙂
I think jamie's take on this was that in his opinion it's likely better to just rely on the scheduler of convex rather than push more work out to resend - this way you don't rely on the process of other systems.
I think this is fair as a general statement with separate email providers to consider. Resend is pretty legitimate to handle schedules too, but I totally see the win of using convex schedulers when considering mutations, etc.
now what I would legitimately like to see on the road map is the ability to send in react components using their tailwind / email-components instead of an html string.. but that's super low hanging fruit 😛
Awesome, yes I saw your face on the YT stream, I jkoined it kinda late so missed your question. Glad Jamie was able to help you out there