EMail Behavior Get Message
Element name: EMailBehaviorCommitMessage
Category: EMail
Description: Basic functionality consisting of an input field for JavaScript code structuring, customizable name, and a group of configurable parameters to obtain email data from the flow configured in Lynn's flow designer.
Functionality: Allows for obtaining email data from the client's mailbox.
Configuration fields for EMail Behavior Get Message action
[Name]: Unique descriptor for the configuration box for identification purposes in the flow.
General configuration subset
Note: 📑 For the following group of configuration tags, it is required to have previously created entities. If the entity is not created, it can be added using the "Add entity" button located within the same tag.
[Specify the contact channel]: Required list field where the name of the previously configured email channel in the channel configuration must be selected.
[Entity where the email ID is stored. Required to send a message as a reply]: Required list field where the entity that will contain the email ID must be stored. This data is obtained from the Google Cloud administrator.
-- Example: The Google Cloud administration interface is shown in the image, and the location where the application name is located is highlighted:
[Entity where email references are stored]: Required list field where they will be stored.
[Entity where the email sender is stored]: Required list field where the entity that will store the email sender's address must be selected.
[Entity where the email cc is stored]: Required list field where the entity that will store the email addresses of the "Copy" or CC recipients must be selected.
[Entity where the email bcc is stored]: Required list field where the entity that will store the email addresses of the recipient(s) "Bcc" or CCO must be selected.
[Entity where the email subject is stored]: Required list field where the entity that will store the email subject must be selected.
[Entity where the email body is stored in plain text]: Required list field where the entity that will store the email body must be selected.
[Entity where the body of the email in HTML will be stored]: Required field of list type where you must select the entity that will store the body of the email in HTML format. This format is the one that the Assistant/Executive can finally visualize in their chat engine.
Example implementation: Email Behavior Get Message
-- Input
[Specify the contact channel]: Email <-- email@gmail.com
[Entity where the email ID will be stored. Required to send a message as a reply]: g-message_id <-- LynnGmail.
[Entity where the email references will be stored. Required to send a message as a reply]: g-message_reference
[Entity where the email sender will be stored]: g_from <-- luis@gmail.com
[Entity where the email cc will be stored]: g_cc <-- jefedeluis@gmail.com
[Entity where the email bcc will be stored]: g_bcc <-- "empty"
[Entity where the email subject will be stored]: g_subject <-- Contract Accepted
[Entity where the email body will be stored in plain text]: g_body_plain <-- By means of this message, I inform you that the client has accepted the contract. Please start the sales process.
[Entity where the email body will be stored in HTML format]: g_body_html <--
cssCopy code
<blockquote class="gmail\_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <div dir="ltr">By means of this message, I inform you that the client has accepted the contract. Please start the sales process.</div>
</blockquote>
-- Output
This is the screen visualization with the entity information:
