Box Comment and Task to Teams Collaboration

Overview

This solution keeps Box file collaboration visible in Microsoft Teams and closes the loop back to Box. A scheduled flow polls comments and tasks on the files in a watched Box folder and mirrors any new ones into a mapped Teams channel (with file context and a deep link). A second, event-driven flow watches that Teams channel and, when someone replies to a mirrored message, posts the reply back onto the originating Box file as a comment.

Why it matters: comments and tasks buried in Box go unseen by people who live in Teams. Surfacing them - and pushing replies back - keeps collaboration in one place without anyone leaving the tool they already use.

Two cloud flows plus one Dataverse mapping table in a single solution. Ships Off (demo).

Use Case

A team stores working files in Box but coordinates day-to-day in Teams. They want Box file discussions and tasks to appear automatically in the right Teams channel, and quick replies typed in Teams to land back on the Box file so the record of the conversation stays complete on both sides.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Box	shared_box	ListFolder
HHTTP	shared_http	GET /files/{id}/comments GET /files/{id}/tasks POST /comments
Microsoft Teams	shared_teams	OnNewChannelMessage PostMessageToConversation
Microsoft Dataverse	shared_commondataserviceforapps	ListRecords

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Watch multiple folders

Replace the single monitored folder id with a JSON folder-to-channel map and loop folders, routing each to its own Teams channel.

@mention the file owner

Read owned_by from the Box file and prepend a Teams mention to the message body.

Surface task due dates

The task message includes due_at; add a Condition to flag tasks due within N days as high importance.

Strip HTML from replies

Teams bodies are HTML; add a Compose to convert to plain text before posting the Box comment.

Switch to Box webhooks

Replace the scheduled poll with a Box webhook posting to an HTTP-request-triggered flow for near-real-time mirroring.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

https://app.box.com/file/@{item()?['Id']}

concat('flowlibs_boxitemid eq ''', items('Apply_to_each_Comment')?['id'], '''')

equals(empty(variables('varReplyParentId')), false)

first(outputs('Find_Parent_Map')?['body/value'])?['flowlibs_boxfileid']