# Teams shows a local DOCX path instead of sending the file

**URL:** <https://community.openclaw.ai/t/teams-shows-a-local-docx-path-instead-of-sending-the-file/32>\
**Category:** Troubleshooting\
**Tags:** attachments, channels, media, permissions, troubleshooting\
**Created:** [September 14, 2026, 5:36pm UTC](https://community.openclaw.ai/t/teams-shows-a-local-docx-path-instead-of-sending-the-file/32 "2026-09-14T17:36:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ArchivedMember](https://avatars.discourse-cdn.com/v4/letter/a/e56c9b/32.png) [@ArchivedMember](https://community.openclaw.ai/u/ArchivedMember)\
**Post date:** [September 14, 2026, 5:36pm UTC](https://community.openclaw.ai/t/teams-shows-a-local-docx-path-instead-of-sending-the-file/32/1 "2026-09-14T17:36:30Z")

</div>

> **Adapted community discussion:** Paraphrased and condensed from an anonymized public OpenClaw Discord support conversation from August 2026. Technical guidance was reviewed for OpenClaw 2026.9.3.

I use OpenClaw with Microsoft Teams. My agent generated a DOCX file, but the reply only showed a local workspace path instead of attaching the document. Can Teams receive the actual file?

---

<div class="post-metadata">

**Author:** ![OpenClawSupport](https://avatars.discourse-cdn.com/v4/letter/o/49beb7/32.png) [@OpenClawSupport](https://community.openclaw.ai/u/OpenClawSupport)\
**Post date:** [September 14, 2026, 8:46pm UTC](https://community.openclaw.ai/t/teams-shows-a-local-docx-path-instead-of-sending-the-file/32/2 "2026-09-14T20:46:17Z")

</div>

Yes. Teams can receive a DOCX attachment, usually as a downloadable file card. The path means generation succeeded but delivery did not happen. Creating a file and uploading it are separate actions.

For a one-to-one chat, the Teams app manifest needs file support. Team channels and group chats also need the documented SharePoint and Microsoft Graph configuration. The Gateway must be able to read the generated file from its own execution environment.

Preview an explicit media send before sending anything externally:

```bash
openclaw message send \
  --channel msteams \
  --account ACCOUNT \
  --target TARGET \
  --media FILE_PATH \
  --dry-run --json

```

A dry run validates the payload but does not contact Teams. A live send still needs approval for the exact file and destination. If the file exists only inside another container, node, or sandbox, stage just that reviewed artifact somewhere the Gateway can read.