Hi All,
We have requirement to create cases based on the mails received in one or more mailboxes in Appian. Kindly guide us on use case or plugin which will help us to achieve this solution. In addition, we have to classify mails based on the subject line of the mails.
Discussion posts and replies are publicly visible
I recommend using the Graph Mail Poller (if your org is on M365) for injestng email.
community.appian.com/.../msgraph-email-poller
As for classifying, you could use the AI Email Classification Smart Service.
docs.appian.com/.../Classify_Emails_Smart_Service.html
Thanks for quick update. Our current project dont have AI option enabled, then whether we can use Graph Mail Poller for classifying mails based on subject line using expression rule?
After going through MSGraph Email poller plugin documentation observed it will not store mail attachment. Whether there is any alternative if mail attachment also required to store?
If you don't have access to the AI features then, yea you would have to use an expression rule.
Appian actually has a doc page dedicated to managing incoming mail.
docs.appian.com/.../email-in-appian.html
Where did you see that?
Shantanu Bhowmick Currently, in one of our projects, we are using the Mail Poller Plugin to read emails in Appian.We are reading incoming emails with attachments in Appian.
The plugin stores email metadata (like subject and body) in a table. Based on business logic (implement this logic in an expression rule), you can classify the email.
Remember: When using this plugin, do not change the name of the table APP_MAIL_POLLER, where the smart service stores email metadata after reading an email.
APP_MAIL_POLLER
Thanks for the quick reply. In that case, Mail Poller will support email attachment as well, then we will check by doing some POC.
Thanks Mathieu Drouin for the link. It is useful to understand our use case further.
Yes right!
Let me know you stuck somewhere.
Second point in the description little mislead us, as it was mentioned in end like attachments removed from it. Later realized after noticed the third points mentioned it will store in separate Appian documents.
Thanks for the clarification, we are clear now, we will do some POC then we will comeback if any questions.