Outlook Groups icon

Outlook Groups

Interact with Microsoft Outlook Groups and SharePoint

Actions9

Overview

This node interacts with Microsoft Outlook Groups to retrieve all messages from a specified Microsoft 365 group mailbox. It is particularly useful for automating workflows that require processing or analyzing group conversations and their messages, such as archiving emails, extracting attachments, or integrating group communications into other systems.

A common scenario includes fetching all messages from a team’s shared mailbox to process attachments or monitor conversations automatically. For example, a user might want to download all email attachments from a group mailbox and upload them to SharePoint for centralized document management.

Properties

Name Meaning
Group ID The Microsoft 365 group from which to retrieve messages. This is selected from available groups in the tenant.
Return All Whether to return all messages or limit the number of results. If false, only up to the specified limit will be returned.
Limit Maximum number of messages to return when "Return All" is false. Value range: 1 to 100.
Include Attachments Whether to include message attachments in the output.
Save Attachments as Binary Data When including attachments, save them as binary data (true) or as base64-encoded strings within JSON (false).
Upload Attachments to SharePoint Automatically upload message attachments to a specified SharePoint site and document library.
SharePoint Site The SharePoint site where attachments will be uploaded if "Upload Attachments to SharePoint" is enabled.
Document Library The document library (drive) within the SharePoint site where attachments will be stored. Defaults to "root".
Folder Path The folder path inside the document library where attachments will be uploaded. Default is "Email Attachments".
Overwrite Existing Whether to overwrite existing files with the same name in SharePoint.
Add Timestamp to Filename Whether to add a timestamp suffix to filenames when uploading to SharePoint to avoid conflicts.

Output

The node outputs an array of message objects, each representing a post within group conversations. Each message object contains:

  • id: The unique identifier of the message.
  • conversationId: The conversation to which the message belongs.
  • threadId: The thread within the conversation.
  • topic / subject: The topic or subject of the conversation/message.
  • body: The content of the message body.
  • from: Information about the sender.
  • receivedDateTime: Timestamp when the message was received.
  • hasAttachments: Boolean indicating if the message has attachments.
  • attachments: An array of attachment metadata objects, each containing:
    • id, name, contentType, size
    • Optionally, contentBytes if attachments are included but not saved as binary.
  • binary: If "Save Attachments as Binary Data" is enabled, attachments are also available here as binary properties with file data, MIME type, filename, and size.
  • sharePointUploads: If attachments were uploaded to SharePoint, this array contains upload results per attachment, including success status, SharePoint file IDs, URLs, sizes, and errors if any.

If attachments are included and saved as binary, the binary data is accessible in the binary property of each message item.

Dependencies

  • Requires an API authentication token credential for Microsoft Graph API access.
  • Access to Microsoft 365 Groups with permissions to read group conversations and messages.
  • Optional: Access to SharePoint sites and document libraries with permissions to upload files if attachment upload is enabled.
  • The node uses internal helper functions to call Microsoft Graph API endpoints for groups, conversations, threads, posts, and attachments.
  • SharePoint upload supports both small (<4MB) and large file uploads via upload sessions.

Troubleshooting

  • No messages returned: Ensure the provided Group ID corresponds to a valid Microsoft 365 group with accessible conversations.
  • Permission errors: Verify that the API credentials have sufficient permissions to read group messages and optionally upload to SharePoint.
  • Attachment missing or empty: If attachments do not appear, check if "Include Attachments" is enabled. Also, some messages may not have attachments.
  • Binary data missing: If "Save Attachments as Binary Data" is enabled but no binary data appears, confirm that the previous nodes provide binary data or that the attachments contain contentBytes.
  • SharePoint upload failures: Errors during upload may occur due to incorrect SharePoint site or document library selection, insufficient permissions, or file conflicts. Check error messages in sharePointUploads output for details.
  • File name conflicts: Enable "Add Timestamp to Filename" or "Overwrite Existing" to handle duplicate file names in SharePoint.
  • API rate limits or timeouts: Large numbers of messages or attachments may cause throttling; consider limiting results or batching requests.

Links and References

This summary covers the static analysis of the node's execute method and related code for the "Message" resource and "Get All" operation.

Discussion