---
schema_version: "1"
id: c31730c9d29cbbbfc6fd1bca7103f7a77ba11c9682c542978f11f5e4795c098f
title: Microsoft Outlook 365 1.3 Examples
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/microsoft-outlook-365-connector/latest/microsoft-outlook-365-connector-examples.md
canonical_url: https://docs.mulesoft.com/microsoft-outlook-365-connector/latest/microsoft-outlook-365-connector-examples
source_site: docs.mulesoft.com
content_type: documentation
content_hash: ca671d5d383568b38687ad1cfc83c6dd3b4d9e2a90a3d3f351bc964516307baf
description: MuleSoft Documentation Site
release: "1.3"
latest: true
---
---
product: Microsoft Outlook 365 Connector
version: 1.3
is-latest-version: true
---
# Microsoft Outlook 365 1.3 Examples
> For the full documentation index, see: https://docs.mulesoft.com/llms.txt
The following examples show how to perform operations that interact with messages, events, and
attachment resources in Microsoft Outlook 365 Connector:
- [Create Message](#create-message)
- [Delete Message](#delete-message)
- [Get Message](#get-message)
- [List Messages](#list-messages)
- [Delete Event](#delete-event)
- [Create Event](#create-event)
- [Update Event](#update-event)
- [List Events](#list-events)
- [Get Event](#get-event)
- [Forward Event](#forward-event)
- [Cancel Event](#cancel-event)
- [Accept Event](#accept-event)
- [Decline Event](#decline-event)
- [List Event Attachments](#list-event-attachments)
- [Add Event Attachment](#add-event-attachment)
- [Add Message Attachment](#add-message-attachment)
- [List Message Attachments](#list-message-attachments)
- [Get Message Attachment](#get-message-attachment)
- [Get Event Attachment](#get-event-attachment)
- [Send Message](#send-message)
- [Send Mail](#send-mail)
- [Create Reply All to Message](#create-reply-all-to-message)
- [Reply All to Message](#reply-all-to-message)
> [!NOTE] Some operations need prerequisite data, for example, to get a message or an event based on
> its ID, you must create a message or an event first.
## Create Message
This Mule flow creates a message to send later. The message is saved in the Drafts folder.
This example uses the following operations:
- **HTTP Listener**
Accepts data from HTTP requests
- **Transform Message**
Transforms the HTTP input used to create a message
- **Create message**
Creates a draft of the message
- **Transform Message**
Outputs the results of the **Create message** operation in JSON format
- **Logger**
Shows the HTTP response from the **Create message** operation
### XML for This Example
Paste this code into the Studio XML editor to quickly load the flow for this example into your Mule
app:
```xml
awesome!"
},
"toRecipients":[
{
"emailAddress":{
"address":"muletest@mulesoft.com"
}
},
{
"emailAddress":{
"address":"muletest@mulesoft.com"
}
}
]
}]]>
```
### Steps for Running This Example
1. Verify that your connector is configured.
2. Save the project.
3. From a web browser, test the application by entering
`[http://localhost:8083/create-msg](http://localhost:8083/create-msg)`.
## Delete Message
This Mule flow deletes an existing message.
This example uses the following operations:
- **HTTP Listener**
Accepts data from HTTP requests
- **Delete message**
Deletes a message from the specified user’s mailbox
### XML for This Example
Paste this code into the Studio XML editor to quickly load the flow for this example into your Mule
app:
```xml
```
### Steps for Running This Example
1. Verify that your connector is configured.
2. Save the project.
3. From a web browser, test the application by entering
`[http://localhost:8083/delete-msg](http://localhost:8083/delete-msg)`.
## Get Message
This Mule flow retrieves an existing message.
This example uses the following operations:
- **HTTP Listener**
Accepts data from HTTP requests
- **Get message**
Retrieves the properties and relationships of a message object
### XML for This Example
Paste this code into the Studio XML editor to quickly load the flow for this example into your Mule
app:
```xml
```
### Steps for Running This Example
1. Verify that your connector is configured.
2. Save the project.
3. From a web browser, test the application by entering
`[http://localhost:8083/get-msg](http://localhost:8083/get-msg)`.
## List Messages
This Mule flow retrieves all of the messages from the signed-in user’s mailbox.
This example uses the following operations:
- **HTTP Listener**
Accepts data from HTTP requests
- **List messages**
Retrieves messages from the signed-in user’s mailbox, including messages from the Deleted Items
and Clutter folders
### XML for This Example
Paste this code into the Studio XML editor to quickly load the flow for this example into your Mule
app:
```xml
```
### Steps for Running This Example
1. Verify that your connector is configured.
2. Save the project.
3. From a web browser, test the application by entering
`[http://localhost:8083/list-messages](http://localhost:8083/list-messages)`.
## Delete Event
This Mule flow deletes an existing event.
This example uses the following operations:
- **HTTP Listener**
Accepts data from HTTP requests
- **Delete event**
Removes the specified event from the calendar
- **Logger**
Shows the HTTP response from the **Delete event** operation
### XML for This Example
Paste this code into the Studio XML editor to quickly load the flow for this example into your Mule
app:
```xml
```
### Steps for Running This Example
1. Verify that your connector is configured.
2. Save the project.
3. From a web browser, test the application by entering
`[http://localhost:8083/delete-event](http://localhost:8083/delete-event)`.
## Create Event
This Mule flow creates an event in a default user’s calendar or in a specified calendar.
This example uses the following operations:
- **HTTP Listener**
Accepts data from HTTP requests
- **Create event**
Creates an event in a default user’s calendar or in a specified calendar
- **Transform Message**
Outputs the results of the **Create event** operation in JSON format
- **Logger**
Shows the HTTP response from the **Create event** operation
### XML for This Example
Paste this code into the Studio XML editor to quickly load the flow for this example into your Mule
app:
```xml
```
### Steps for Running This Example
1. Verify that your connector is configured.
2. Save the project.
3. From a web browser, test the application by entering
`[http://localhost:8083/create-event](http://localhost:8083/create-event)`.
## Update Event
This Mule flow updates an existing event.
This example uses the following operations:
- **HTTP Listener**
Accepts data from HTTP requests
- **Update event**
Updates the properties of the event object
- **Transform Message**
Outputs the results of the **Update event** operation in JSON format
- **Logger**
Shows the HTTP response from the **Update event** operation
### XML for This Example
Paste this code into the Studio XML editor to quickly load the flow for this example into your Mule
app:
```xml
```
### Steps for Running This Example
1. Verify that your connector is configured.
2. Save the project.
3. From a web browser, test the application by entering
`[http://localhost:8083/update-event](http://localhost:8083/update-event)`.
## List Events
This Mule flow lists all events.
This example uses the following operations:
- **HTTP Listener**
Accepts data from HTTP requests
- **List events**
Retrieves a list of event objects from the user’s mailbox
- **Transform Message**
Outputs the results of the **List events** operation in JSON format
- **Logger**
Shows the HTTP response from the **List events** operation
### XML for This Example
Paste this code into the Studio XML editor to quickly load the flow for this example into your Mule
app:
```xml
```
### Steps for Running This Example
1. Verify that your connector is configured.
2. Save the project.
3. From a web browser, test the application by entering
`[http://localhost:8083/list-events](http://localhost:8083/list-events)`.
## Get Event
This Mule flow retrieves an existing event.
This example uses the following operations:
- **HTTP Listener**
Accepts data from HTTP requests
- **Get event**
Gets the properties and relationships of the specified event object
- **Transform Message**
Outputs the results of the **Get event** operation in JSON format
- **Logger**
Shows the HTTP response from the **Get event** operation
### XML for This Example
Paste this code into the Studio XML editor to quickly load the flow for this example into your Mule
app:
```xml
```
### Steps for Running This Example
1. Verify that your connector is configured.
2. Save the project.
3. From a web browser, test the application by entering
`[http://localhost:8083/get-event](http://localhost:8083/get-event)`.
## Forward Event
This Mule flow forwards an existing event.
This example uses the following operations:
- **HTTP Listener**
Accepts data from HTTP requests
- **Forward event**
Forwards the meeting request to a new recipient
- **Logger**
Shows the HTTP response from the **Forward event** operation
### XML for This Example
Paste this code into the Studio XML editor to quickly load the flow for this example into your Mule
app:
```xml
```
### Steps for Running This Example
1. Verify that your connector is configured.
2. Save the project.
3. From a web browser, test the application by entering
`[http://localhost:8083/forward-event](http://localhost:8083/forward-event)`.
## Cancel Event
This Mule flow cancels an existing event.
This example uses the following operations:
- **HTTP Listener**
Accepts data from HTTP requests
- **Cancel event**
Cancels the specified event from a user’s calendar
- **Logger**
Shows the HTTP response from the **Cancel event** operation
### XML for This Example
Paste this code into the Studio XML editor to quickly load the flow for this example into your Mule
app:
```xml
```
### Steps for Running This Example
1. Verify that your connector is configured.
2. Save the project.
3. From a web browser, test the application by entering
`[http://localhost:8083/cancel-event](http://localhost:8083/cancel-event)`.
## Accept Event
This Mule flow accepts an existing event.
This example uses the following operations:
- **HTTP Listener**
Accepts data from HTTP requests
- **Accept event**
Accepts the specified event from a user’s calendar
- **Logger**
Shows the HTTP response from the **Accept event** operation
### XML for This Example
Paste this code into the Studio XML editor to quickly load the flow for this example into your Mule
app:
```xml
```
### Steps for Running This Example
1. Verify that your connector is configured.
2. Save the project.
3. From a web browser, test the application by entering
`[http://localhost:8083/accept-event](http://localhost:8083/accept-event)`.
## Decline Event
This Mule flow declines an existing event.
This example uses the following operations:
- **HTTP Listener**
Accepts data from HTTP requests
- **Decline event**
Declines the specified event from a user’s calendar
- **Logger**
Shows the HTTP response from the **Decline event** operation
### XML for This Example
Paste this code into the Studio XML editor to quickly load the flow for this example into your Mule
app:
```xml
```
### Steps for Running This Example
1. Verify that your connector is configured.
2. Save the project.
3. From a web browser, test the application by entering
`[http://localhost:8083/decline-event](http://localhost:8083/decline-event)`.
## List Event Attachments
This Mule flow lists the attachments of an existing event.
This example uses the following operations:
- **HTTP Listener**
Accepts data from HTTP requests
- **List event attachments**
Retrieves a list of attachment objects attached to an event
- **Transform Message**
Outputs the results of the **List event attachments** operation in JSON format
- **Logger**
Shows the HTTP response from the **List event attachments** operation
### XML for This Example
Paste this code into the Studio XML editor to quickly load the flow for this example into your Mule
app:
```xml
```
### Steps for Running This Example
1. Verify that your connector is configured.
2. Save the project.
3. From a web browser, test the application by entering
`[http://localhost:8083/list-event-attachments](http://localhost:8083/list-event-attachments)`.
## Add Event Attachment
This Mule flow adds an attachment to an existing event.
This example uses the following operations:
- **HTTP Listener**
Accepts data from HTTP requests
- **Add event attachment**
Adds an attachment to an event
- **Transform Message**
Outputs the results of the **Add event attachment** operation in JSON format
- **Logger**
Shows the HTTP response from the **Add event attachment** operation
### XML for This Example
Paste this code into the Studio XML editor to quickly load the flow for this example into your Mule
app:
```xml
```
### Steps for Running This Example
1. Verify that your connector is configured.
2. Save the project.
3. From a web browser, test the application by entering
`[http://localhost:8083/add-event-attachment](http://localhost:8083/add-event-attachment)`.
## Add Message Attachment
This Mule flow adds an attachment to an existing message.
This example uses the following operations:
- **HTTP Listener**
Accepts data from HTTP requests
- **Add message attachment**
Adds an attachment to a message
- **Transform Message**
Outputs the results of the **Add message attachment** operation in JSON format
- **Logger**
Shows the HTTP response from the **Add message attachment** operation
### XML for This Example
Paste this code into the Studio XML editor to quickly load the flow for this example into your Mule
app:
```xml
```
### Steps for Running This Example
1. Verify that your connector is configured.
2. Save the project.
3. From a web browser, test the application by entering
`[http://localhost:8083/add-message-attachment](http://localhost:8083/add-message-attachment)`.
## List Message Attachments
This Mule flow lists all of the attachments of an existing message.
This example uses the following operations:
- **HTTP Listener**
Accepts data from HTTP requests
- **List message attachments**
Retrieves a list of attachment objects attached to a message
- **Transform Message**
Outputs the results of the **List message attachments** operation in JSON format
- **Logger**
Shows the HTTP response from the **List message attachments** operation
### XML for This Example
Paste this code into the Studio XML editor to quickly load the flow for this example into your Mule
app:
```xml
```
### Steps for Running This Example
1. Verify that your connector is configured.
2. Save the project.
3. From a web browser, test the application by entering
`[http://localhost:8083/list-message-attachments](http://localhost:8083/list-message-attachments)`.
## Get Message Attachment
This Mule flow retrieves an attachment from an existing message.
This example uses the following operations:
- **HTTP Listener**
Accepts data from HTTP requests
- **Get message attachment**
Reads the properties and relationships of an attachment that is attached to a user message
- **Logger**
Shows the HTTP response from the **Get message attachment** operation
### XML for This Example
Paste this code into the Studio XML editor to quickly load the flow for this example into your Mule
app:
```xml
```
### Steps for Running This Example
1. Verify that your connector is configured.
2. Save the project.
3. From a web browser, test the application by entering
`[http://localhost:8083/get-message-attachment](http://localhost:8083/get-message-attachment)`.
## Get Event Attachment
This Mule flow retrieves an attachment from an existing event.
This example uses the following operations:
- **HTTP Listener**
Accepts data from HTTP requests
- **Get event attachment**
Reads the properties and relationships of an attachment that is attached to an event
- **Logger**
Shows the HTTP response from the **Get event attachment** operation
### XML for This Example
Paste this code into the Studio XML editor to quickly load the flow for this example into your Mule
app:
```xml
```
### Steps for Running This Example
1. Verify that your connector is configured.
2. Save the project.
3. From a web browser, test the application by entering
`[http://localhost:8083/get-event-attachment](http://localhost:8083/get-event-attachment)`.
## Send Message
This Mule flow sends a message from the Drafts folder, which the **Create message** operation
created previously.
This example uses the following operations:
- **HTTP Listener**
Accepts data from HTTP requests
- **Send message**
Sends a message from the Drafts folder
- **Logger**
Shows the HTTP response from the **Send message** operation
### XML for This Example
Paste this code into the Studio XML editor to quickly load the flow for this example into your Mule
app:
```xml
```
### Steps for Running This Example
1. Verify that your connector is configured.
2. Save the project.
3. From a web browser, test the application by entering
`[http://localhost:8083/send-message](http://localhost:8083/send-message)`.
## Send Mail
This Mule flow sends a message without creating a draft message first.
This example uses the following operations:
- **HTTP Listener**
Accepts data from HTTP requests
- **Send mail**
Sends the message specified in the request body
- **Logger**
Shows the HTTP response from the **Send mail** operation
### XML for This Example
Paste this code into the Studio XML editor to quickly load the flow for this example into your Mule
app:
```xml
```
### Steps for Running This Example
1. Verify that your connector is configured.
2. Save the project.
3. From a web browser, test the application by entering
`[http://localhost:8083/send-mail](http://localhost:8083/send-mail)`.
## Create Reply All to Message
This Mule flow creates a reply-all message that is saved in the Drafts folder. The message can then
be sent using the **Send message** operation.
This example uses the following operations:
- **HTTP Listener**
Accepts data from HTTP requests
- **Create reply all to message**
Creates a draft to reply to the sender and all the recipients of the specified message
- **Transform Message**
Outputs the results of the **Create reply all to message** operation in JSON format
- **Logger**
Shows the HTTP response from the **Create reply all to message** operation
### XML for This Example
Paste this code into the Studio XML editor to quickly load the flow for this example into your Mule
app:
```xml
```
### Steps for Running This Example
1. Verify that your connector is configured.
2. Save the project.
3. From a web browser, test the application by entering
`[http://localhost:8083/create-reply-all-to-message](http://localhost:8083/create-reply-all-to-message)`.
## Reply All to Message
This Mule flow creates a reply-all message, which is sent without creating it first in the Drafts
folder using the **Create message** operation.
This example uses the following operations:
- **HTTP Listener**
Accepts data from HTTP requests
- **Reply all to message**
Replies to all recipients of a message
- **Logger**
Shows the HTTP response from the **Reply all to message** operation
### XML for This Example
Paste this code into the Studio XML editor to quickly load the flow for this example into your Mule
app:
```xml
```
### Steps for Running This Example
1. Verify that your connector is configured.
2. Save the project.
3. From a web browser, test the application by entering
`[http://localhost:8083/reply-all-to-message](http://localhost:8083/reply-all-to-message)`.
## See Also
- [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors)
- [Salesforce Help](https://help.salesforce.com)