Adding custom vars to email templates?

Adding custom vars to email templates? User email confirmation FRONTEND_URL use case

Hello,

I would like to be able to add custom vars to the e-mail templates of the user-permission confirmation and reset password templates.

I’m using Strapi v5 through an Astro front-end, so the Strapi confirm link will not be immediately visible to end users who need to click on the e-mail link.

A solution would be being able to define custom vars such as the provided <%= CODE %>, for example <%= FRONTEND_URL %> that would be available globally.

Without this, I think I need to hard code these values between dev and staging.

You can add your own vars by extending the email plugin’s send call in a lifecycle or controller and passing FRONTEND_URL into the template context so it works like CODE.

I’ve been growing my outreach lists faster lately by using scrape emails from linkedin to pull verified contacts without needing to log in or run extensions. The built‑in verification saved me a ton of bounces, and the background processing kept things moving while I worked on other tasks. The free credits made it easy to test without committing anything upfront.