Resend and MySQL: Work Anniversary Email Template

A scheduled query finds employees celebrating a work anniversary today and sends each one a personalized recognition email through Resend.

What It Builds

A Schedule trigger fires every morning and a MySQL connector node queries your HR table for employees whose hire date matches today's month and day. A Loop node walks each match, and inside it a Resend connector node sends a warm, personalized anniversary email with the employee's name and years of service. Spojit handles the daily timing so nobody on your team has to remember the dates.

The Prompt

Paste this into Miraxa and it builds the workflow, connecting the tools for you:

Build a workflow that runs every weekday at 8am, queries my MySQL employees table for anyone whose hire date is today's month and day, and for each match sends a personalized work anniversary email through Resend that greets them by first name and mentions how many years they have been with us.

Connectors Used

  • Schedule trigger - runs the workflow on a daily cron in your time zone.
  • MySQL - reads the employee records that match today's anniversary date.
  • Resend - sends each recognition email from your own verified domain.

Customize It

Change the time and days in the prompt (for example, run only on weekdays or at a different hour), adjust the employees table or column names to match your schema, and reword the email so the subject line and message fit your culture. You can also add milestone logic by mentioning that 1, 5, and 10 year anniversaries should get a different message.

Tips

  • Verify your sending domain in Resend first so anniversary emails land reliably.
  • Use the Resend node in Direct mode to send a fixed template with no AI cost; switch to Agent mode only if you want the message wording generated per employee.
  • If your hire dates are stored as full timestamps, ask Miraxa to compare on month and day only so the query matches every year.

Related

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.