Automate Microsoft Teams Communications

This skill automates Microsoft Teams operations through Composio's Microsoft Teams toolkit, reached via Rube MCP. It covers five core workflows: sending channel messages (list teams, list channels, post the message, with team_id as a UUID and channel_id in thread format like '19:abc@thread.tacv2'); sending direct or group chat messages (list or create a chat, then post, with group chats requiring at least one 'owner'-role member); creating online meetings (subject, ISO 8601 start/end times, participant user IDs as GUIDs, producing a standalone meeting not linked to a calendar event - calendar-linked meetings instead go through OUTLOOK_CALENDAR_CREATE_EVENT with is_online_meeting=true); managing teams and channels (list, get, create channels, list and add members); and searching messages across chats and channels with KQL query syntax. Every workflow always calls RUBE_SEARCH_TOOLS first to get current tool schemas before acting.

Use it once Rube MCP is connected and an active Microsoft Teams connection exists via RUBE_MANAGE_CONNECTIONS with toolkit microsoft_teams (added as https://rube.app/mcp, no API keys needed, confirmed ACTIVE after Microsoft OAuth). It is not the right tool for a calendar-linked Teams meeting - use the Outlook Calendar event creation tool with the online-meeting flag for that instead - and IDs should never be guessed; every ID must be resolved from a list operation (MICROSOFT_TEAMS_TEAMS_LIST, MICROSOFT_TEAMS_LIST_USERS, etc.) rather than assumed.

Inputs are the target team/channel/chat/user IDs (resolved through list calls rather than supplied directly) plus message content, meeting details, or search queries. A documented ID-resolution pattern covers both teams/channels (list teams, find by display name, extract the UUID, list channels, find by display name, extract the thread-format channel ID) and users (list users, filter by name or email, extract the UUID). Outputs are posted messages, created chats or meetings, channel/team management results, or search results. Known pitfalls are extensive: TEAMS_LIST and other list calls paginate via @odata.nextLink (up to ~100 items/page, chats capped at 50 per page via top); messages over roughly 28KB trigger 400/413 errors and must be split; throttling returns 429 with a Retry-After header, requiring exponential backoff (1s/2s/4s) and keeping requests to a few per second; newly posted messages take 30-60 seconds to become searchable, so search cannot be used for immediate delivery confirmation; and 403 errors mean insufficient Microsoft Graph permissions or missing admin consent in the Azure AD tenant, not necessarily a code bug.

Built on Composio's Microsoft Teams toolkit via Rube MCP, which wraps Microsoft Graph. It cross-references Outlook Calendar for calendar-linked meetings (OUTLOOK_CALENDAR_CREATE_EVENT). A quick-reference table maps each task (list teams, post channel/chat message, create meeting, manage members, search messages, list joined teams, and more) to its exact tool slug and key parameters.

Developers and automation builders who need to script Microsoft Teams messaging, meeting creation, team/channel management, or message search through Composio/Rube MCP, and want the concrete parameter formats and rate-limit/pagination pitfalls up front rather than discovered through failed calls.