con un clic
con un clic
Add iMessage channel integration via Chat SDK. Local (macOS) or remote (Photon API) mode.
Install rtk token-compression proxy into agent containers. Routes Bash tool calls through rtk for 60–90% token savings on dev commands (git, cargo, pytest, docker, kubectl, etc.).
Format messages for WhatsApp, including mentions that render as real WhatsApp tags. Use when responding in a WhatsApp conversation (platform_id / chatJid ends with @s.whatsapp.net or @g.us).
Add WhatsApp channel via native Baileys adapter. Direct connection — no Chat SDK bridge. Uses QR code or pairing code for authentication.
Add Google Calendar as an MCP tool (list calendars, list/search/create events, free/busy queries) using OneCLI-managed OAuth. Multi-calendar and multi-account supported. Mirrors /add-gmail-tool's stub pattern — no raw credentials ever reach the container; OneCLI injects real tokens at request time.
Add Gmail as an MCP tool (read, search, send, label, draft) using OneCLI-managed OAuth. The agent gets Gmail tools in every enabled group; OneCLI injects real tokens at request time so no raw credentials are ever in the container or on disk in usable form.
| name | add-teams |
| description | Add Microsoft Teams channel integration via Chat SDK. |
Connect NanoClaw to Microsoft Teams for interactive chat in team channels, group chats, and direct messages.
NanoClaw doesn't ship channels in trunk. This skill copies the Teams adapter in from the channels branch.
Skip to Credentials if all of these are already in place:
src/channels/teams.ts existssrc/channels/index.ts contains import './teams.js';@chat-adapter/teams is listed in package.json dependenciesOtherwise continue. Every step below is safe to re-run.
git fetch origin channels
git show origin/channels:src/channels/teams.ts > src/channels/teams.ts
Append to src/channels/index.ts (skip if the line is already present):
import './teams.js';
pnpm install @chat-adapter/teams@4.27.0
pnpm run build
Two paths — manual (Azure Portal) or auto (Teams CLI).
Requires Node.js 18+, a Microsoft 365 account with sideloading permissions, and a public HTTPS endpoint (ngrok, Cloudflare Tunnel, or similar).
Install the CLI:
npm install -g @microsoft/teams.cli@preview
Sign in and verify:
teams login
teams status
Create the Entra app, client secret, and bot registration:
teams app create \
--name "NanoClaw" \
--endpoint "https://your-domain/api/webhooks/teams"
The CLI prints the credentials as CLIENT_ID, CLIENT_SECRET, and TENANT_ID. Map them to NanoClaw's env keys:
CLIENT_ID → TEAMS_APP_IDCLIENT_SECRET → TEAMS_APP_PASSWORDTENANT_ID → TEAMS_APP_TENANT_IDPick Install in Teams from the post-create menu and confirm in the Teams dialog.
Continue to Configure environment.
The steps below describe the manual Azure Portal path.
Or use Azure CLI:
az group create --name nanoclaw-rg --location eastus
az bot create \
--resource-group nanoclaw-rg \
--name nanoclaw-bot \
--app-type SingleTenant \
--appid YOUR_APP_ID \
--tenant-id YOUR_TENANT_ID \
--endpoint "https://your-domain/api/webhooks/teams"
https://your-domain/api/webhooks/teamsOr via CLI:
az bot msteams create --resource-group nanoclaw-rg --name nanoclaw-bot
Create a manifest.json:
{
"$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.16/MicrosoftTeams.schema.json",
"manifestVersion": "1.16",
"version": "1.0.0",
"id": "YOUR_APP_ID",
"packageName": "com.nanoclaw.bot",
"developer": {
"name": "NanoClaw",
"websiteUrl": "https://your-domain",
"privacyUrl": "https://your-domain",
"termsOfUseUrl": "https://your-domain"
},
"name": { "short": "NanoClaw", "full": "NanoClaw Assistant" },
"description": {
"short": "NanoClaw assistant bot",
"full": "NanoClaw personal assistant powered by Claude."
},
"icons": { "outline": "outline.png", "color": "color.png" },
"accentColor": "#4A90D9",
"bots": [{
"botId": "YOUR_APP_ID",
"scopes": ["personal", "team", "groupchat"],
"supportsFiles": false,
"isNotificationOnly": false
}],
"permissions": ["identity", "messageTeamMembers"],
"validDomains": ["your-domain"]
}
Create two icon PNGs (32x32 outline.png, 192x192 color.png), zip all three files together.
Sideload in Teams:
Sideloading requires Teams admin access. Free personal Teams does NOT support sideloading. Use a Microsoft 365 Business account or developer tenant.
By default, the bot only receives messages when @-mentioned. To receive all messages in a channel without @-mention, add RSC permissions to manifest.json:
{
"authorization": {
"permissions": {
"resourceSpecific": [
{ "name": "ChannelMessage.Read.Group", "type": "Application" }
]
}
}
}
Add to .env:
TEAMS_APP_ID=your-app-id
TEAMS_APP_PASSWORD=your-client-secret
# For Single Tenant only:
TEAMS_APP_TENANT_ID=your-tenant-id
TEAMS_APP_TYPE=SingleTenant
Sync to container: mkdir -p data/env && cp .env data/env/env
The Chat SDK bridge automatically starts a shared webhook server on port 3000 (configurable via WEBHOOK_PORT env var). The server handles /api/webhooks/teams for Teams and other webhook-based adapters. This port must be publicly reachable from the internet for Azure Bot Service to deliver activities.
For local development without a public URL, use a tunnel (e.g., ngrok http 3000) and update the messaging endpoint in Azure Bot Configuration.
If you're in the middle of /setup, return to the setup flow now.
Otherwise, run /manage-channels to wire this channel to an agent group.
teamsteams:{base64-encoded-conversation-id}:{base64-encoded-service-url} — auto-generated by the adapter, not human-readable. Use the auto-created messaging group ID for wiring.