Information
  • Author: Appian Corporation
  • Type: Plug-in (Function & Smart Service)
  • Support: This plug-in or utility is not supported by the author. The content is free to use with a licensed product, but it is made available as-is and Community supported.
  • Industry: All Industries
  • Compatible Version(s): 24.2
  • First Released:
  • Last Updated:
  • Cost: Free
Share
Home » AppMarket » MSGraph Email Poller

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
Parents

  • We are going to upgrade from 3.1.1 t0 4.0.1 . I was going through the deployment Instruction pdf and under Upgrade instruction found that it requires me to do all of the steps which i had done previously while upgrading to 3.1.1 , i.e. adding columns to APP POLLER and DOC tables, which are same as 3.1.1 and changing the tenant URL which we had done in 3.1.1 , which was to remove "login.microsoftononline..." from SCS (third party credential store). So could you confirm that if we upgrade to 4.0.1 , only thing for us is to upgrade the jar file and remap inputs and outputs?

Comment

  • We are going to upgrade from 3.1.1 t0 4.0.1 . I was going through the deployment Instruction pdf and under Upgrade instruction found that it requires me to do all of the steps which i had done previously while upgrading to 3.1.1 , i.e. adding columns to APP POLLER and DOC tables, which are same as 3.1.1 and changing the tenant URL which we had done in 3.1.1 , which was to remove "login.microsoftononline..." from SCS (third party credential store). So could you confirm that if we upgrade to 4.0.1 , only thing for us is to upgrade the jar file and remap inputs and outputs?

Children
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.