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
  • Hi, 

    We have several emails ending up in the exception folder, today we have 12 emails where the error in the logs is:

    2025-04-11 02:48:22,537 [Appian Work Item - 2042542 - WorkID 832 - execution00 - process 36048198 - model 1283 : UnattendedJavaActivityRequest] ERROR com.appiancs.msgraphmail.MSGraphDBHandler - Error writing mail to database
    java.lang.NullPointerException

    We would appreciate it if you could provide us with more detailed information about this error so that we can prevent emails from being sent to the exceptions folder.

    Thanks in advance

  • Seems to be solved with the release 4.2.7

  • You need to make sure the that application tied to the client credentials you have received have access to the mailbox you are trying to connect to.

  • Hi Team,

    We are using msgraph mail poller plugin to read emails. We are getting below error while reading emails. Could you please help on this ?

    Error Message : Error code: ErrorAccessDenied Error message: Access to OData is disabled: [RAOP] : Blocked by tenant configured AppOnly AccessPolicy settings. GET

    Thank you in advance for your help

  • v4.2.7 Release Notes
    • Security patch updated
  • Microsoft setup steps

    • Create top level mailbox per environment for email polling
    • Create mailbox folders for processed emails and failed emails
    • Set up server side forward and deliver rules to copy emails from Shared Inboxes to Top Level Inbox
    • Register Azure application
      • Mail.ReadWrite (for polling)
      • Mail.Send (for reply capabilities from each mailbox)
      • Top Level Inbox requires sendAs permission to all Shared Inboxes
      • Restrict application access to only Shared Inboxes & Top Level Inbox
      • OAuth 2.0 Client Credentials grant type
      • Application Permission:
        • Mail.ReadWrite (for polling)
        • Mail.Send (for reply capabilities from each mailbox)
        • Top Level Inbox requires sendAs permission to all Shared Inboxes
        Restrict application access to only Shared Inboxes & Top Level Inbox
  • Hi, Can someone help me what are the basic pre-requisites to configure this.

  • Anyone else facing the issue with null subject? It is kind of critical for us, as until the message with null/empty subject is deleted from the mailbox manually, the mail poller is blocked

  • Hello, we have started to receive new type of error after the upgrade to the version 4.2.6. If the email does not contain subject, mail poller fails with an error Cannot invoke "String.equals(Object)" because "subject" is null. This error persists until the message without subject is removed from the Inbox.

    Can some error handling be added for these cases?

    Thanks!

  • I see the error message "Error executing the request" in output from the smart service. The process doesn't faild and it ends correctly.
    What's the problem?