Ability to send to any additional email through the email action in workflows
M
Matt Ingebrigtsen
Currently, additional emails are only accessible to send to from the contact record. The "Email" action and "Notification" action in workflows will only send to the primary email in additional emails, even if you have specified a secondary email as the recipient in the "Notification" action.
The idea here would be to give users the ability, when setting up an "Email" action in a workflow, to select any of the 10 allowed emails from the additional emails field as the recipient (i.e. Email 1, Email 2, Email 3, etc), defaulting to a "skipped action" if an email does not exist in that spot. OR, allow the user to choose what happens if the email is not found in that spot ("skip or send to Email 1").
Log In
N
Nate Cameron
To do this I have done the following - capture the secondary email through intake (spouse, parent, whatever) custom fields. Use the internal notification feature to send an email to that field in the workflow (contact.spouse or whatever it ends up being). This won't solve the issue in all cases but can in many. Hope that helps Matt Ingebrigtsen
M
Matt Ingebrigtsen
Nate Cameron Oh i'm aware of the workarounds. The reason we don't immediately use the internal notification action is because it will create a duplicate contact record since that email address doesn't already exist in the system as a primary email. This might be manageable for some but we require a work AND personal email on every opt in. It's a necessity for what we do. so managing dups will quickly become an unmanageable nightmare as we tend to get hundreds and sometimes thousands of form fills every week.
This is currently what we have to do to send to the primary email first and then to the "personal" email.
First, we capture both emails off of a form and put both the "Work" email and "Personal" emails text fields while setting the primary email field to the "Work" email. Then, in the workflow, we send the email to the Primary email, do an if/else to see if there is something in the personal email field and that it's NOT the same as the primary email field, we set the primary email field with the contents of the personal email field, do an if/else to make sure that worked (we've seen it not work), and if it worked we will send the email again to the primary email which is now the personal email and end by swapping the work email back into the primary email. If swapping the personal email into the email field didn't work we send the email with an internal email notification action and add them to a smart list so we can review why it didn't work.