Microsoft Outlook

Send, receive, and manage emails and contacts via Microsoft Graph.

Detail	Value
Category	Productivity
Base URL	https://graph.microsoft.com/v1.0
Authentication	OAuth2
Endpoints	6
Connector key	microsoft-outlook

Using Microsoft Outlook in a workflow

1. Go to Connections and click New Connection.
2. Pick Microsoft Outlook from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown. The full list is below.

Available endpoints

Endpoint	Summary
GET /me/messages	List email messages
POST /me/sendMail	Send an email
GET /me/messages/{messageId}	Get an email message
DELETE /me/messages/{messageId}	Delete an email
GET /me/contacts	List contacts
GET /me/mailFolders	List mail folders

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /me/messages

List email messages

Detail	Value
Operation ID	productivity.listMessages
Method	GET
Path	/me/messages

Parameters

Name	Location	Type	Required
$top	query	integer	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Microsoft Outlook connection from the Connection dropdown.
3. In the Operation dropdown, select productivity.listMessages.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Microsoft Outlook API reference.

POST /me/sendMail

Send an email

Detail	Value
Operation ID	productivity.sendMail
Method	POST
Path	/me/sendMail

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Microsoft Outlook connection from the Connection dropdown.
3. In the Operation dropdown, select productivity.sendMail.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Microsoft Outlook API reference.

GET /me/messages/{messageId}

Get an email message

Detail	Value
Operation ID	productivity.getMessage
Method	GET
Path	/me/messages/{messageId}

Parameters

Name	Location	Type	Required
messageId	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Microsoft Outlook connection from the Connection dropdown.
3. In the Operation dropdown, select productivity.getMessage.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Microsoft Outlook API reference.

DELETE /me/messages/{messageId}

Delete an email

Detail	Value
Operation ID	productivity.deleteMessage
Method	DELETE
Path	/me/messages/{messageId}

Parameters

Name	Location	Type	Required
messageId	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Microsoft Outlook connection from the Connection dropdown.
3. In the Operation dropdown, select productivity.deleteMessage.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Microsoft Outlook API reference.

GET /me/contacts

List contacts

Detail	Value
Operation ID	productivity.listContacts
Method	GET
Path	/me/contacts

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Microsoft Outlook connection from the Connection dropdown.
3. In the Operation dropdown, select productivity.listContacts.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Microsoft Outlook API reference.

GET /me/mailFolders

List mail folders

Detail	Value
Operation ID	productivity.listFolders
Method	GET
Path	/me/mailFolders

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Microsoft Outlook connection from the Connection dropdown.
3. In the Operation dropdown, select productivity.listFolders.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Microsoft Outlook API reference.