Office 365 - Synthreo Builder

Office 365 node for Builder - integrate AI agent workflows with Microsoft 365 services including Outlook email, Teams messages, OneDrive files, and SharePoint document libraries.

Purpose

The Office 365 node integrates Microsoft Office 365 services into ThreoAI workflows. It supports Teams and Outlook actions, enabling message and email automation. This node requires authorization with an Office 365 account before use.

Use this node when your workflow needs to send emails through Outlook, read messages from a Teams channel, send Teams notifications, or perform actions on existing emails such as flagging or changing importance.

Authorization

Before configuring any action, you must authorize the node with a valid Office 365 account. Click the Authorize button in the node settings and complete the Microsoft OAuth login flow. The node will store the authorization token for subsequent workflow runs.

Ensure the account used has the appropriate Microsoft 365 licenses and permissions for the actions you intend to perform (for example, Teams access for Teams actions, and a mailbox for Outlook actions).

Inputs

This node does not require inputs by default. Inputs are only needed when using the Perform Action option, which requires providing mail IDs to execute the action on a specific email.

Outputs

The node returns data from Teams or Outlook actions, such as:

Message lists from Teams channels or personal chats
Email send status from Outlook
Message send confirmation from Teams
Email action status from Outlook Perform Action operations

Parameters

Teams Parameters

Action	Chat Type	Parameters
Read Messages	Personal	Maximum number of messages to read; filter criteria
Read Messages	Team	Maximum number of messages to read; filter criteria
Send Messages	Personal	Select the group chat to send the message to
Send Messages	Team	Select the team and channel to send the message to

Outlook Parameters

Action	Parameters
Send Email	Recipient (To), CC, Subject, Body
Read Email	Currently has known issues - see note below
Perform Action	Email ID, Action Type

Teams Actions in Detail

Read Messages - Personal Chat

Retrieves messages from a personal group chat. Configure:

Maximum Messages: The upper limit of messages to retrieve in a single workflow run. Keep this value low (10 to 50) for faster execution.
Filter Criteria: An optional filter to narrow down which messages are returned.

Read Messages - Team Channel

Retrieves messages posted to a specific team channel. Configure:

Maximum Messages: Upper limit of messages to retrieve. Lower values improve performance.
Filter Criteria: Optional filter to narrow results by sender, date, or keyword.

Send Messages - Personal Chat

Posts a message to a personal group chat. Configure:

Chat Selection: Select the target group chat from the dropdown populated after authorization.

Send Messages - Team Channel

Posts a message to a channel inside a team. Configure:

Team and Channel Selection: Select the target team and channel from the dropdowns populated after authorization.

Outlook Actions in Detail

Send Email

Sends an email from the authorized Outlook account. Parameters:

Parameter	Description
To	Primary recipient email address. Supports dynamic values from upstream nodes.
CC	Additional recipients to copy. Optional.
Subject	Subject line for the email.
Body	Email body content. Supports HTML and dynamic variables.

Read Email

Note: The Read Email action currently has known issues. Avoid using this action in production workflows until this is resolved.

Perform Action

Executes a management action on an existing email. Requires:

Email ID: The unique identifier of the email to act on. This must be passed from an upstream node that provides email data.
Action Type: One of the following options:

Action Type	Details
Mark as Read	Marks the target email as read.
Mark as Unread	Marks the target email as unread.
Manage Flag	Add a follow-up flag (requires start and end time), Mark as Complete (requires completed date/time), or Clear Flag (removes any existing flag).
Change Importance	Sets the importance level to Low, Normal, or High.

Example Usage

Teams Automation: Read the last 10 messages from a specific team channel and pass the content to an LLM node to generate a summary, then post the summary to a different channel.
Outlook Automation: Automatically send follow-up emails to a list of recipients after a workflow completes its processing steps.
Outlook Perform Action: When a workflow detects a high-priority client email, use the Perform Action step to set its importance to High and add a follow-up flag with a due date.

Troubleshooting

Issue	Likely Cause	Resolution
Authorization fails	Account does not have the required Microsoft 365 licenses	Confirm the account has Teams and Exchange Online access.
Teams channel not visible in dropdown	Bot or app not added to the team	Add the Synthreo application to the team in Microsoft Teams admin settings.
Emails not sending	SMTP or Exchange restrictions on the tenant	Contact your Microsoft 365 administrator to verify outbound email is permitted.
Perform Action fails with “Email ID not found”	The Email ID from an upstream node is stale or incorrect	Verify the Email ID property name from the upstream node’s output and ensure it is a current, valid ID.
Read Messages returns no results	Filter criteria is too restrictive or no messages match	Clear filter criteria and test with a broad query first, then refine.

Best Practices

Always authorize with the correct Office 365 account before configuring actions. Using a shared service account rather than a personal account is recommended for production workflows.
For Teams Read Messages, keep the maximum number of messages low for faster execution. Only retrieve as many messages as the workflow actually needs to process.
Avoid using Read Email until the known issues are resolved. Use the Email Receiver node for IMAP-based email retrieval as an alternative.
Use Perform Action to automate email triage, but ensure the correct Email ID is provided from an upstream node to avoid unintended changes to the wrong email.
Test workflows in a non-production Teams channel or with a test email account before deploying to live channels and inboxes.

Email Receiver - for retrieving emails via IMAP when the Outlook Read Email action is not suitable.
Send Email - for sending emails via SMTP without requiring an Office 365 account authorization.
HTTP Client - for calling the Microsoft Graph API directly if you need Office 365 capabilities not covered by this node.