Updated: 2026-01-21

Status: text + DM attachments are supported; channel/group file sending requires `sharePointSiteId` + Graph permissions (see [Sending files in group chats](#sending-files-in-group-chats)). Polls are sent via Adaptive Cards.

- Adaptive Cards are supported for polls and arbitrary card sends (see below)

- `channels.msteams.sharePointSiteId`: SharePoint site ID for file uploads in group chats/channels (see [Sending files in group chats](#sending-files-in-group-chats)).

Bots can send files in DMs using the FileConsentCard flow (built-in). However, **sending files in group chats/channels** requires additional setup:

| Context | How files are sent | Setup needed |

|---------|-------------------|--------------|

| **DMs** | FileConsentCard → user accepts → bot uploads | Works out of the box |

| **Group chats/channels** | Upload to SharePoint → share link | Requires `sharePointSiteId` + Graph permissions |

| **Images (any context)** | Base64-encoded inline | Works out of the box |

Bots don't have a personal OneDrive drive (the `/me/drive` Graph API endpoint doesn't work for application identities). To send files in group chats/channels, the bot uploads to a **SharePoint site** and creates a sharing link.

1. **Add Graph API permissions** in Entra ID (Azure AD) → App Registration:

- `Sites.ReadWrite.All` (Application) - upload files to SharePoint

- `Chat.Read.All` (Application) - optional, enables per-user sharing links

2. **Grant admin consent** for the tenant.

3. **Get your SharePoint site ID:**

```bash

# Via Graph Explorer or curl with a valid token:

curl -H "Authorization: Bearer $TOKEN" \

"https://graph.microsoft.com/v1.0/sites/{hostname}:/{site-path}"

# Example: for a site at "contoso.sharepoint.com/sites/BotFiles"

curl -H "Authorization: Bearer $TOKEN" \

"https://graph.microsoft.com/v1.0/sites/contoso.sharepoint.com:/sites/BotFiles"

# Response includes: "id": "contoso.sharepoint.com,guid1,guid2"

```

4. **Configure Clawdbot:**

```json5

{

channels: {

msteams: {

// ... other config ...

sharePointSiteId: "contoso.sharepoint.com,guid1,guid2"

}

}

}

```

| Permission | Sharing behavior |

|------------|------------------|

| `Sites.ReadWrite.All` only | Organization-wide sharing link (anyone in org can access) |

| `Sites.ReadWrite.All` + `Chat.Read.All` | Per-user sharing link (only chat members can access) |

Per-user sharing is more secure as only the chat participants can access the file. If `Chat.Read.All` permission is missing, the bot falls back to organization-wide sharing.

| Scenario | Result |

|----------|--------|

| Group chat + file + `sharePointSiteId` configured | Upload to SharePoint, send sharing link |

| Group chat + file + no `sharePointSiteId` | Attempt OneDrive upload (may fail), send text only |

| Personal chat + file | FileConsentCard flow (works without SharePoint) |

| Any context + image | Base64-encoded inline (works without SharePoint) |

Uploaded files are stored in a `/ClawdbotShared/` folder in the configured SharePoint site's default document library.

Send any Adaptive Card JSON to Teams users or conversations using the `message` tool or CLI.

The `card` parameter accepts an Adaptive Card JSON object. When `card` is provided, the message text is optional.

**Agent tool:**

{

"action": "send",

"channel": "msteams",

"target": "user:<id>",

"card": {

"type": "AdaptiveCard",

"version": "1.5",

"body": [{"type": "TextBlock", "text": "Hello!"}]

}

}

**CLI:**

clawdbot message send --channel msteams \

--target "conversation:19:[email protected]" \

--card '{"type":"AdaptiveCard","version":"1.5","body":[{"type":"TextBlock","text":"Hello!"}]}'

See [Adaptive Cards documentation](https://adaptivecards.io/) for card schema and examples. For target format details, see [Target formats](#target-formats) below.

MSTeams targets use prefixes to distinguish between users and conversations:

| Target type | Format | Example |

|-------------|--------|---------|

| User (by ID) | `user:<aad-object-id>` | `user:40a1a0ed-4ff2-4164-a219-55518990c197` |

| User (by name) | `user:<display-name>` | `user:John Smith` (requires Graph API) |

| Group/channel | `conversation:<conversation-id>` | `conversation:19:[email protected]` |

| Group/channel (raw) | `<conversation-id>` | `19:[email protected]` (if contains `@thread`) |

**CLI examples:**

clawdbot message send --channel msteams --target "user:40a1a0ed-..." --message "Hello"

clawdbot message send --channel msteams --target "user:John Smith" --message "Hello"

clawdbot message send --channel msteams --target "conversation:19:[email protected]" --message "Hello"

clawdbot message send --channel msteams --target "conversation:19:[email protected]" \

--card '{"type":"AdaptiveCard","version":"1.5","body":[{"type":"TextBlock","text":"Hello"}]}'

**Agent tool examples:**

{

"action": "send",

"channel": "msteams",

"target": "user:John Smith",

"message": "Hello!"

}

{

"action": "send",

"channel": "msteams",

"target": "conversation:19:[email protected]",

"card": {"type": "AdaptiveCard", "version": "1.5", "body": [{"type": "TextBlock", "text": "Hello"}]}

}

Note: Without the `user:` prefix, names default to group/team resolution. Always use `user:` when targeting people by display name.

- `send` (text + optional media; MS Teams also supports `card` for Adaptive Cards)