Set up email provider

Many authentication use cases require sending emails to your users. Whether they are looking to verify their email address, reset their password, or be alerted of password changes, your users will need to receive these emails. This page shows the options for configuring email providers via the ReachFive Console.

See the Email templates page if you are looking for templates.

ReachFive integrates with the following email SaaS services:

We also provide:

generic integrations with SMTP servers.
an Email API to send the required information to a desired endpoint.

SMTP providers

You should use the SMTP provider to send emails if you have a reliable SMTP server available that will be able to handle all automated email distribution.

SMTP provider setup

In the ReachFive Console, go to Emails Providers.
Enter the SMTP configuration details.
1. Specify the From email address. This is what the recipients see as who sent the email.
2. Enter any Reply to email addresses that you wish to have. (Optional)
  
  When users reply, it will be sent to these emails.
3. Enter the host for your SMTP server.
4. Enter the port for that host SMTP server.
5. Enter your username for the SMTP server.
6. Enter the password associated with the above username for the SMTP server.
7. Check SSL or TLS depending on your requirements.
Select Send test email to validate the configuration.

The email is sent to the address of the user currently logged in.
Don’t forget to Save your input.

Custom providers

You should use the generic Email API to send emails when:

ReachFive Console does not provide a native integration with your SaaS solution. You need to implement the generic email API, and then send your emails from your system as you would.
You use a custom or in-house piece of software to manage emails. You will need to implement our generic API and then map the data sent to your template and email service.

Provider setup

In the ReachFive Console, go to Emails Providers.
Select Custom provider
Select the endpoint where you would like ReachFive Console to send email requests.

When sent, the REQUEST and payload are set and not customisable.
If needed, enter the HTTP Authorization value. For example: Basic dm9yZGVsOnZvcmRlbA==. (Optional)
Select Send test email to validate the configuration.

The email is sent to the address of the user currently logged in.
Don’t forget to Save your input.

Select the endpoint where you would like ReachFive to send email requests

An example request and payload are as follows:

POST https://YOUR_DOMAIN

{
  "email": "clarence@example.com",
  "template_id": "verify_email", (1)
  "personalizations": {
     "id": "id",
     "external_id": "externalId",
     "given_name": "Max",
     "last_name": "Robertson",
     "gender": "M",
     "has_password": "true", (2)
     "lang": "fr",
     "verification_code": "verificationCode",
     "redirect_url": "https://www.example.com/redirect"
   }
}

1	The `template_id` is the email template. This is the ID for the template found at Settings Emails Templates or alternatively for MFA at Settings MFA email templates.
2	The `has_password` boolean is only included in the payload for the `password_reset` template.

The has_password boolean gives custom email providers the option to let users create a password.

true: The user already has a password; the user should be asked to reset the existing password.
false: The user does not have a password associated with their account; the user should be asked to create a password.

Custom personalization fields

The following are all of the possible personalizations you can use as part of the payload sent for custom email providers.

Email

id
external_id
given_name
last_name
gender
has_password
lang
verification_code
redirect_url