integration-service
latest
false
UiPath logo, featuring letters U and I in white

Integration Service user guide

Last updated Mar 16, 2026

Microsoft Outlook 365 events

The Microsoft Outlook 365 connector supports:

  • Predefined events, which are already configured and represent specific actions on specific objects. For example, Calendar event created.
  • Generic events, for which you must define the event record to monitor. For example, New record created for an event record.
EventSupported objects
Calendar event createdCalendar
Calendar event updatedCalendar
Calendar event receivedCalendar
Calendar event repliedCalendar
Email receivedMessage
Email moved to trashMessage
Email sentMessage
New record createdCalendar, Message
Existing record updatedCalendar, Message

Event polling is performed every five minutes, by default. The polling interval is configurable. For details, refer to the Triggers documentation.

Event outputs

Each Microsoft Outlook 365 event outputs a reference to an object, which you can retrieve with the corresponding activities. The following table shows the Microsoft events and output object types:

Using the UiPathEventObjectId with Microsoft Outlook 365 integration

The value of the UiPathEventObjectId property can be different depending on what integration services you use. For example, when you use the Microsoft Outlook 365 connector for the integration, you can only use the UiPathEventObjectId value with the Get Mai activity from the Microsoft 365 package. This is because both the integration service connector and the Microsoft 365 activities are using Microsoft Graph as the underlying service and can read or write the same values.

When you use activities such as Outlook Desktop or Get Exchange Mail Messages, these will require a different mail ID.

The following is an example of how to use the UiPathEventObjectId with the Microsoft Outlook 365 integration and disconnected triggers.

Creating the connection

  1. Go to Automation Cloud.
  2. Select Integration Service from the rail menu.
  3. Under Connectors, search for Microsoft Outlook 365, and select the connector.
  4. Select Connect to Microsoft Outlook 365 and log in with your Microsoft Office 365 account. If the connection is successful, continue with the following section, Building the process.

Building the process

  1. Create a new process in Studio.
  2. Define the following input arguments of type String: UiPathEventObjectId.
  3. Configure the Microsoft Office 365 Scope and the activities you want to use. In this example, we will use Get Email by ID and log the subject of the email.
  4. For Get Email by ID, use the UiPathEventObjectId argument as an input for the Email ID property.
  5. Publish the process to Orchestrator and add it to the same folder as the machine and user that you want to use.

For more details on how to use the integration service trigger arguments, check Using triggers in Integration Service.

Creating the trigger

  1. Go to Automation Cloud.
  2. Select Integration Service from the rail menu.
  3. Under Triggers, you can view all triggers you created in Orchestrator.
  4. Select the connector, connection, event, the process to execute, and runtime license.
  5. Select Add trigger. In this example, we will use the event New email received. Each time you receive an email, the process uses the UiPathEventObjectId to identify the mail and retrieve its subject.
Note:

It might take a few minutes before the process is triggered.

Once the process is started, you can view the attempt in Integration Services, under Triggers, when you select the trigger, and then Attempts' history.

Once the job is completed, you can check the logs to validate the results.

Connected and disconnected triggers

When using Microsoft Outlook 365 events, the behavior of the UiPathEventObjectId property depends on the trigger type used in Orchestrator. For example:

  • Connected triggers - A Connected trigger is created automatically when you use trigger or event activities inside a Studio process. When such a trigger runs, Orchestrator captures and exposes additional event metadata as input arguments. For example, the following properties:

    • UiPathEventConnector: uipath-microsoft-outlook365
    • UiPathEvent: EMAIL_RECEIVED
    • UiPathEventObjectType: Message
    • UiPathEventObjectId:AAMkADAxYTMwYmMyLWI3ZjgtNDgyMC1hZjBhLTkzYjg1ZjZkMzNjNgBGAAAAAABa9oHsd0YYRqFEIHEYum2TBwCwCVF6abPNR7M-vldRPu9OAAG_PIPlAACwCVF6abPNR7M-vldRPu9OAAaIt5wTAAA=
    • UiPathTime: Wed Oct 08 2025 14:09:07 GMT+0200 (Central European Summer Time)
    • UiPathCorrelationId: a2a09ce9-078e-4542-b35a-96d939d6c6a3
    • UiPathAdditionalEventData.processedEventId:v2::pp::1759925348021::13013::a5e7ca96b888238a The trigger automatically consumes this additional event metadata to fetch the corresponding object.
  • Disconnected triggers - You must manually create a Disconnected trigger in Orchestrator and can use it to start any automation.

    You can combine Disconnected triggers with certain activities, for example, Get Mail by ID, by using the UiPathEventObjectId value captured from a Connected trigger execution. This allows you to retrieve the same object from the source system in a follow-up or independent process.

You can configure both Connected and Disconnected triggers in Orchestrator, under the Processes tab, when creating or editing a process.

Was this page helpful?

Connect

Need help? Support

Want to learn? UiPath Academy

Have questions? UiPath Forum

Stay updated