Skip to main content

Microsoft Outlook integration

Send, read, and organize Microsoft Outlook mail on behalf of your clients.

What it does

The Microsoft Outlook integration moves mailbox work for your clients into TaskJuice without anyone signing into Outlook by hand. Connect a client's Microsoft 365 (or personal Microsoft) account once and you can list and read messages with OData filters, send brand new email, reply inside an existing conversation, forward a message with a note, delete a message, organize incoming mail into new folders, and start a workflow whenever a new message lands in the mailbox or in a specific folder such as Inbox.

Connect a Microsoft Outlook account

  1. Open your workspace in TaskJuice and navigate to Connections.
  2. Choose Microsoft Outlook and click Connect.
  3. Sign in with the Microsoft work, school, or personal account whose mailbox you want to manage on behalf of your client.
  4. Grant the requested scopes (read and modify access to Mail, send access for outgoing messages, and read access to mailbox settings).
  5. TaskJuice returns you to the workspace with the connection ready to use in any workflow.

To revoke access at any time, visit My Apps and consents for work and school accounts, or Microsoft account privacy for personal accounts, and remove the TaskJuice entry.

Triggers

  • microsoft-outlook/new-message polls the connected mailbox on a configurable interval and emits one activation per cycle containing every message that matches the optional OData filter and search expression. Drop a Loop node downstream to process each message individually, or feed the array straight into a digest.
  • microsoft-outlook/new-message-in-folder polls a specific mail folder (Inbox by default, or any well-known folder name or folder ID) on a configurable interval and emits one activation per cycle containing every message observed in that folder since the previous cycle.

Actions

  • microsoft-outlook/list-messages returns the messages in the mailbox that match an optional OData filter, select, orderby, or search expression, with cursor pagination via @odata.nextLink.
  • microsoft-outlook/get-message returns a single message by ID, optionally projecting a subset of properties via OData $select.
  • microsoft-outlook/send-mail sends a new email message with subject, HTML or plain text body, To, CC, and BCC recipients.
  • microsoft-outlook/reply-to-message sends a reply to an existing message and keeps the reply inside the original conversation.
  • microsoft-outlook/forward-message forwards an existing message to one or more recipients with an optional comment.
  • microsoft-outlook/delete-message permanently removes a message from the mailbox.
  • microsoft-outlook/create-mail-folder creates a new mail folder at the root of the connected mailbox, optionally marked as hidden.

Known limitations

  • Microsoft Graph supports change notifications for mail resources, but the verification handshake and per-subscription clientState validation fall outside the declarative envelope used by TaskJuice. The new-message triggers therefore poll on a configurable interval (60 seconds minimum, five minutes by default), so latency is bounded by the chosen interval rather than instant.
  • Microsoft Graph applies per-application and per-tenant throttling. When a 429 is returned, TaskJuice surfaces it as a retryable rate-limit error and respects the recommended backoff window.
  • Sending and replying require the Mail.Send scope. Creating folders and deleting messages require the Mail.ReadWrite scope. Read-only access is sufficient for the polling triggers and the list and get actions.
  • Personal Microsoft accounts and work or school accounts share the same scope vocabulary, but tenant administrators can disable specific permissions. If the OAuth consent screen omits a scope, the corresponding actions will fail with a permission-denied error at runtime.
Was this helpful?
Microsoft Outlook integration | TaskJuice Docs