Kiwi
Kiwi

Kiwi for Microsoft Teams

Have the agent on a Kiwi step post a review request to a Microsoft Teams channel and read the replies, through the Microsoft Graph API.

  • Your agent works in Microsoft Teams through its own connection. Kiwi does not call Microsoft Teams and never holds its credentials.
  • A workflow skill can list Microsoft Teams among the tools it requires. When you supply your agent's available tools to a skill check and Microsoft Teams is not among them, the check reports SK15-UNSUPPORTED-TOOL.
  • A project Admin can add links to Microsoft Teams, with notes, under Connections and bind them to the steps that use them. The agent reads them with list_connections.
  • The agent can report the tools and plugins it ran with, including its Microsoft Teams connection, with report_configuration.
  • The agent submits links to its work in Microsoft Teams as the step's outputs. People review them, and sign-off stays with the people your workflow names.

What your agent can do in Microsoft Teams

  • Send a message to a team channel or to a chat, for example with the step's result.
  • Reply to a channel message so that a run's updates stay in one thread.
  • List a channel's messages and the replies to one of them to read a request and its discussion.
  • Send as the signed-in user with the delegated ChannelMessage.Send permission, since Microsoft Graph allows application permissions for sending only when migrating messages.

Set up

  1. Connect your agent to Kiwi

    Add Kiwi's hosted MCP server, https://kiwiflow.io/mcp, to your coding agent.

    Coding agentsQuickstart

  2. Connect your agent to Microsoft Teams

    Give your agent access to the Microsoft Teams API as its documentation describes. The credentials stay with your agent.

    Microsoft Teams documentation

  3. Example skill

    Publish instructions like these as a workflow skill that lists Microsoft Teams among its required tools.

    Read the team ID, channel ID and pull request from the assignment inputs.
Post a review request to the channel that names the pull request and its risk.
Read the replies to that message before the step ends.
Submit the message's webUrl and any reply that raises a concern as outputs.
The reviewer named in the assignment decides whether a concern blocks it.
If Graph returns 403 for the channel, call report_blocker with the error.
Get startedRead the setup guide