The block (Fig.1(1)) is used in space to build the Flow. The settings panel for this component opens (Fig.1(2)) when you click on the block.
Fig.1. Send email component
1.1. Send email block
The block consists of the following elements:
The name of the component;
in branch - receiving (connecting with the previous block) branch;
out branch - outgoing (connecting with the following block) branch.
1.2. Send email settings panel
It consists of the following elements:
;
;
Subject;
;
Message;
SMTP Settings;
Port;
Server;
TLS;
Break;
Add limit.
1.2.1.
Here you enter the email recipient.
Here you can enter additional recipients.
1.2.3. Subject
The subject of the message is entered here.
1.2.4.
Here you enter the email sender.
1.2.5. Message
The body of the message is entered in this field.
1.2.6. In Reply To
It is used to be able to maintain a conversation, that is, to quote previous messages in response to them.
The response will be sent as a separate new message if the field is blank.
To keep the conversation in the In Reply To field you have to enter a variable - ${message_id}
This variable contains the identifier of the message to be answered.
1.2.7. SMTP Settings
It is designed for authorization.
In the on position, two additional fields are opened for entering data for authorization:
User;
Password.
1.2.8. Port
Mail server settings.
Here you can enter the port in this field.
1.2.9. Server
Mail server settings.
Here you can enter the server in this field.
1.2.10. TLS
TLS (Transport Layer Security) is a protocol for encrypting email to protect privacy. TLS prevents unauthorized access to emails during transmission over the Internet.
- the protocol is enabled;
- the protocol is disabled.
1.2.11. Response code
Enter the name of the variable that will be used to store responses from SMTP in case of receiving errors in this field.
1.2.12. Break
Responsible for the completion of the flow execution.
- initiates the end of the flow execution after the given component.
- the switch is in the off position.
1.2.13. Add limit
Unable to render {include} The included page could not be found.
Add Comment