Last Updated: May 10, 2022
While validating the email configuration, I am getting an authentication error even though I have provided the correct credentials. If you are using a Gmail account, change the security settings of the account. Click here to know more about the steps. After you change the settings, refresh the Task design page where you are validating the email configuration and validate the credentials again.
I have an Email Browser node to read emails from a mailbox, but I get an error "No Match Found" when I execute? This error occurs when the condition given under Actions tab of the Email Browser node does not match with the existing emails in the mailbox. Correct the condition.
Values for the condition are not case-sensitive.
I am trying to authenticate my outlook email in the configuration of email browser node but getting "Could not establish imaps connection" error. This error occurs when you provide IMAPS protocol and exchange server uses EWS protocol. Select Incoming/ Outgoing Protocol as Exchange(EWS). Give the Incoming Server/Outgoing Server as https://outlook.office365.com/ews/exchange.asmx. Ensure that the exchange server is running before you validate the configuration.
Facing "Email Browser node fails with … invalid file extensions" error. This error occurs when the attachment extension types you are browsing using Email Browser node does not exist in the configuration files.
While executing Email Sender node I am getting an error “The content of the file attachment at index 0 must be set”. This occurs when the Attachment-fileID is not mapped correctly. In the image above, the file path of the local file is mapped for Attachment-fileID.
Email is browsed using Email Browser Node, the attachment is downloaded and the fileID of the attachment is mapped to pdfFID of Doc Reader node. While executing Doc Reader node, I am getting the error “400 Bad Request: [no body]” for Doc Reader node. This occurs when the attachment-id passed for mapping is empty. Ensure the following:
Gmail has discontinued permissions for Less Secure Apps, except for Google Workspace and Google Cloud Identity. As Google Workspace support is disabled, Email-related features such as, Email, Browser, Send e-mail, etc. are stopped working. The option for allowing less secure apps feature is not applicable for individual email accounts anymore. This applies for regular Google accounts as of May 30, 2022. Therefore, you must either create app passwords for these accounts or move to a GSuite account.