Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Microsoft Outlook

Microsoft Outlook integration for Flows360 workflows.

CategoryProductivity
Authenticationcustom
Version0.6.0
Published scopes0 published scopes
Last updatedSeptember 21, 2026

Overview

Connect Microsoft Outlook with Flows360

Microsoft Outlook integration for Flows360 workflows.

Use the Microsoft Outlook connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 12 actions and 3 triggers.

Available actions

  • Send Email
  • Download Attachment
  • Reply to Email
  • Create Draft Email
  • Add Label to Email
  • Remove Label from Email
  • Request Approval in Email
  • Move Email to Folder
  • Plus 4 additional declared actions.

Available triggers

  • New Email
  • New Email in Folder
  • New Attachment

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Microsoft Outlook
  • Package: @activepieces/piece-microsoft-outlook@0.6.0
  • Exact artifact digest: sha256:bce524324e6c98038c5bb99b39398f5571411a560ad24576dd842d7f7713acaf
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

OAUTH2. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Send Email (send-email), Sends an email using Microsoft Outlook. Classification: read.
  • Download Attachment (downloadAttachment), Download attachments from a specific email message. Classification: read.
  • Reply to Email (reply-email), Reply to an outlook email. Classification: read.
  • Create Draft Email (createDraftEmail), Creates a draft email message. Classification: read.
  • Add Label to Email (addLabelToEmail), Adds a category (label) to an email message. Classification: read.
  • Remove Label from Email (removeLabelFromEmail), Removes a category (label) from an email message. Classification: read.
  • Request Approval in Email (request_approval_in_mail), Send approval request email and then wait until the email is approved or disapproved Classification: read.
  • Move Email to Folder (moveEmailToFolder), Moves an email message to a specific folder. Classification: read.
  • Send Draft Email (sendDraftEmail), Sends a draft email message. Classification: read.
  • Forward Email (forwardEmail), Forwards an email message. Classification: read.
  • Find Email (findEmail), Searches for emails using full-text search. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Email, polling.
  • New Email in Folder, polling.
  • New Attachment, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects15
Supported actionsNot published
Triggers3

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Access token Required · protected credential
  • Cloud Environment Required
  • Access Mode Required
  • Tenant ID Required
  • Mailbox (App-only) Optional

Supported objects

ObjectReadWriteNotes
Send Email Yes No Sends an email using Microsoft Outlook.
Download Attachment Yes No Download attachments from a specific email message.
Reply to Email Yes No Reply to an outlook email.
Create Draft Email Yes No Creates a draft email message.
Add Label to Email Yes No Adds a category (label) to an email message.
Remove Label from Email Yes No Removes a category (label) from an email message.
Request Approval in Email Yes No Send approval request email and then wait until the email is approved or disapproved
Move Email to Folder Yes No Moves an email message to a specific folder.
Send Draft Email Yes No Sends a draft email message.
Forward Email Yes No Forwards an email message.
Find Email Yes No Searches for emails using full-text search.
Custom API Call Yes No Make a custom API call to a specific endpoint
New Email Yes No polling trigger declared by the pinned package.
New Email in Folder Yes No polling trigger declared by the pinned package.
New Attachment Yes No polling trigger declared by the pinned package.

Triggers

New Email · Poll

Triggers when a new email is received in the inbox.

Inputs

  • sender · string
  • recipient · string
New Email in Folder · Poll

Triggers when a new email is delivered into the specified folder.

Inputs

  • folderId · string
New Attachment · Poll

Triggers when a new email containing one or more attachments arrives.

Inputs

  • folderId · string
  • sender · string
  • attachmentNameFilter · string

Setup

Setup

  1. Add the Microsoft Outlook connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Cloud Environment (cloud), required.
  • Access Mode (accessMode), required.
  • Tenant ID (tenant), required.
  • Mailbox (App-only) (mailbox), optional.

OAuth scopes

  • {accessMode}
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-microsoft-outlook@0.6.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 12 actions and 3 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Microsoft Outlook connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-microsoft-outlook@0.6.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com