Send email

general settings this task will send emails to the desired destination this task has the following settings from name it's the name that is displayed in an inbox above or to the left of the subject line it tells the recipient who sent the message or who it’s 'from' from email here you can the address of the email sender keep in mind that to use a custom "from email" you first need to contact your hypercoach to validate your domain otherwise, this feature won't work and emails won't be sent reply to email this will be the email of the person who will receive replies to the sent email destination emails (to) here you can set the receivers of the emails you can enter up to 15 addresses here, they can be separated by a comma, semicolon, or whitespace you can also use variables like the email of the cms contact or cms organization(it works with other entities too) to link such an email you should have the needed entity set as a property of the process, then you can enter the entity id of the email field in {{}} brackets example {{company email}} destination emails (cc) here you can set the receivers of the email copies has the same possibilities and limitations as 'destination emails (to)' destination emails (bcc) here you can set the receivers of the hidden email copies has the same possibilities and limitations as 'destination emails (to)' you can enable the computed mode for all previously mentioned fields default template here you can select the https //app archbee io/docs/ffeactz47 cw3ctxvllbm/fmbeuqcq41voj8ftphign and edit the mapping of the template you can also select the language of the default template the field also supports computed expressions, but keep in mind that in the end, the computed expression has to return an entity id of the template you can find the entity id of email templates in the 'email templates' cms object template mapping will allow you to choose templates based on the process property to set up mapping click on the 'show template option' there you should choose a process property that will be used for mapping and the mapping rules example (see screenshot above) the node sends email in the dutch language by default, because the dutch template is selected as default we added the 'language' property as a mapping property and selected the right template for the english language now the email node will send an email in english if the language is selected in the process property field attachment property this setting allows you to send file attachments with your emails here you can select a file type property of the process the email node will attach the files that are saved in the chosen property to the sent email email logs you can enable email logging for every 'send transactional email node' if this option is enabled (this switch also supports https //hyperportal help/#/content/computed expressions , but keep in mind that the expression should return true or false at the end), every email that was sent by this node will be recorded in the 'email logs' cms entity this cms entity has prebuilt metrics that can show you the email status analytics each log shows the status of the message and the id of the workflow process and the task that sent the email continue on fail the email node can fail if there are no email destinations (example the contact has empty email fields) you can turn on the setting that allows the process to continue even if the email node fails you can also decide whether the output of the node is skipped on the fail both switches support https //hyperportal help/#/content/computed expressions (expression should return true or false) forms you can add multiple forms to your email the settings of the form are the same as in the ' https //app archbee io/docs/2cknjfhyirys11yu azfj/u45vrr4kw17gwulcama8e ' node template variable name in this field, you can set the variable that will be used in the email template example you can create an unsubscribe button with the link to the unsubscribe form in the link field of the button settings, you should enter the form variable name in curly brackets (see screenshot) send mail history after the process ends to send mail, you can check it in the history on the side drawer, where send email destination shows delivery mail status deliveryт deliveryт / warning warning / bounce bounce ( 1 1 ) email sending details button ( 2 2 ) after clicking on the button ( 2 2 ) the window "email sending details" will appear, where click the "preview" button to see how the email looks in a browser and on a mobile device ( 1 1 ) click the "details" button ( 2 2 ) recipient(s) to ( 3 3 ) delivery status( 4 4 ) date and time ( 5 5 ) displays the count of email openings ( 6 6 ) displays the count of clicks on a button in an email ( 7 7 ) after clicking on the "details" button the side drawer will open "global status" section ( 1 1 ) (we have no information from aws who clicked and opened the email, only the ip address, because of this, we show this information at the global message level) send and delivery status shows only once ( 2 2 ) open status means that mail was opened ( 3 3 ) click status displayed how many times the user clicked on the link and which link in the mail( 4 4 ) "user history" section which shows only send and delivery status ( 5 5 ) email feedback statuses send – the send request was successful and hyperportal will attempt to deliver the message to the recipient’s mail server renderingfailure – the email wasn't sent because of a template rendering issue this event type can occur when template data is missing, or when there is a mismatch between template parameters and data reject – our security scan determined that it contained a virus or something suspicious, and didn’t attempt to deliver it to the recipient’s mail server delivery – we delivered the email to the recipient's mail server bounce – a hard bounce that the recipient's mail server permanently rejected the email complaint – the email was successfully delivered to the recipient’s mail server, but the recipient marked it as spam this recipient's email will be added to our blacklist, because he indicated that he doesn't want to receive any emails like this if this was done by mistake by the recipient, a manual message needs to be sent to support\@hypercharge io, so that we can remove the email from the list deliverydelay – the email couldn't be delivered to the recipient’s mail server because a temporary issue occurred delivery delays can occur, for example, when the recipient's inbox is full, or when the receiving email server experiences a transient issue open – the recipient received the message and opened it in their email client click – the recipient clicked one or more links in the email