MSGraph Email Poller

Overview

Need to poll emails from your Exchange server? This smart service can be used in a poller process and extract the data from the Microsoft Exchange server. Messages are stored in the Appian Document System, as well as the attachments. Meta data is stored in a database table for further processing.

This plug-in provides an alternative to sending emails to an Appian process model when inbound email integration is requested. Instead of the email being forwarded to Appian, this plug-in reads the emails directly from the Exchange mailbox using the MS Graph API as described below:

  • Reads the mailbox using the MS Graph API
  • Convert the email to an EML file stored as an Appian document; Item attachments (calendar invites, messages) are kept in the eml file, File attachments removed from it and stored separately in the document management system.
  • Store all email file attachments as separate Appian documents
  • Store all email metadata (subject, author, recipients, etc...) into a set of tables in the database

Key Features & Functionality

All information how to deploy, configure and use the smart service is in the 'MS Graph Mail Poller.pdf' document in the downloaded zip. Extract the files in the ZIP and follow the instructions in the document.

Anonymous
  • v4.2.0 Release Notes
    • Updates to license file and to deprecated APIs. Updates to netty and jackson libraries. Fixed issue with smart service icon not populating.

    1. The plugin does not currently support connected system data sources this is currently on the backlog but no immediate work is happening to update it.
    2. The plugin does not currently support postgresql.
  • Hi,


    We are doing a database migration from Appian, to a database located in AWS of Aurora PostgreSQL type.
    We have created the tables in the postgresql database and also performed the data migration, but we have had 2 problems when configuring the plugin:

    - The first one is: is it mandatory that the plugin node connection in the Jndi Name field is configured in the Appian Management Console, can't a connected system be used?

    - After creating the connection in Appian Admin Console and pointing to our postgresql database in AWS, we have executed the node and it returned the following error: "Unsupported database dor processing email: PostgreSQL"

    {errorOcurred=true, errorMessage=Unsupported database for processing email: PostgreSQL, timeLimit=false, mailCount=0, errorCount=0}

    Does this mean that the plugin does not support postgreSQL databases? Is there any extra configuration to do? Why does this problem occur?

    The only difference in the configuration with the Appian database was the Jndi Name, the rest is the same and with the Appian database, it worked without any problem.

    Thank you very much and best regards

  • Hi Raul,

    My requirement is to integrate the Outlook with Appian, as and when a mail is moved any specific folder in an outlook, a process has to start in Appian.

    Could you please let me know the detailed steps to use this plug in.

    Thanks in advance!!!

  • Hi,

    we are getting this error message in the logs:

    2023-10-31 15:04:40,983 [Appian Work Item - 367586 - WorkID 611 - execution02 - process 538402870 - model 2914 : UnattendedJavaActivityRequest] ERROR com.appiancs.msgraphmail.MSGraphMessageHandler - Error during email processing
    java.sql.SQLSyntaxErrorException: (conn=250054) SAVEPOINT a390d423-f2be-438d-965f-272736fc07ca does not exist.

    and the email has been sent to junk email folder.

    can you confirm why this error?

    regards
    Veronica
  • Yes, all plugins are supported on versions higher than the one specified unless otherwise indicated.

  • Moving emails post ingestion to the Deleted Items folder is the default behavior. There is a field "Processed Folder Name" that you can specify the name of the folder you would like messages to move to after processing.

  • The admin console governs only the file types uploaded by the user, not through programmatic means. Currently the plugin does not implement an allow list for attachment file types.

  • v4.1.1 Release Notes
    • Fixed email aliases. Aliases used by the sender in To and Cc fields are correctly recorded in the database To and Cc fields rather than the main/parent email address.
    • [This behaviour regressed at v4.0.0 with the move to Jakarta mail]

  • We are upgrading to Appian 23.2.  MSGraph Mail Poller is not working in the upgraded environments.  Is MSGraph Mail Poller compatible with 23.2?  In system logs I see "Unexpected error polling for mail com.microsoft.graph.core.ClientException: Error executing the request". 

    Is there any issue you've heard of / seen with Appian 23.2?  Is this supported?  (I see Compatible Version: 22.3 in Information).  This plug in worked with 23.1 no problems.