+
Connect GitHub to Microsoft teams
Automate GitHub and Microsoft teams with AI
CI failures and review requests belong in Microsoft Teams where the squad already works. Operator.io points your OpenClaw agent at GitHub and Teams so failed checks post to the channel you choose, merged PRs announce with a link, and a Teams message can request status on a repo or open issue. Tell it to summarize overnight builds and it reads GitHub Actions and replies in the thread.
It reaches both apps directly or through connectors like Composio MCP and Pipedream MCP, which handle the sign in and token refresh, so there is no Zap to build and no API keys to paste.
What your agent can do with GitHub and Microsoft teams
What your agent does in GitHub
Abort Repository Migration
Tool to abort a repository migration that is queued or in progress. Use when you need to cancel an ongoing migration operation.
Accept a repository invitation
Accepts a PENDING repository invitation that has been issued to the authenticated user.
Add app access restrictions
Adds GitHub Apps to the list of apps allowed to push to a protected branch. The branch must already have protection rules with restrictions enabled. This endpoint only works for organization repositories, not personal repositories. Apps...
Add a repository collaborator
Adds a GitHub user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation ma...
Add assignees to an issue
Adds assignees to a GitHub issue. This action only adds users - it does not remove existing assignees. Changes are silently ignored if the authenticated user lacks push access to the repository.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's GitHub account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the...
What your agent does in Microsoft teams
Add chat member
Tool to add a conversationMember to a Microsoft Teams chat. Use when adding a user to an existing chat conversation.
Add tab to channel
Tool to add a new tab to a Microsoft Teams channel. Use when you need to pin an app or website as a tab in a channel.
Add member to team
Tool to add a user to a Microsoft Teams team. Use when granting or updating membership for a user.
Add team members (bulk)
Tool to add multiple members to a Microsoft Teams team in a single operation. Use when adding several users at once to improve efficiency.
Archive channel
Tool to archive a channel in a Microsoft Teams team. Use when you need to archive a specific channel within a team.
Archive team channel
Tool to archive a channel in a Microsoft Teams team using the group ID. Use when you need to archive a specific channel within a team.
How it works
Tell the agent what you want to happen between GitHub and Microsoft teams, for example to watch one and act in the other, or to keep the two in step. It reads what it needs from GitHub, works out what to do, and runs the matching action in Microsoft teams without you mapping a single field.
You can have it run once, on a schedule, or whenever something changes. Ask it for a status any time and it reads the latest from both apps back to you in the same chat.
Common questions about GitHub and Microsoft teams
- How do I connect GitHub and Microsoft teams to Operator?
- You authorize GitHub and Microsoft teams once each from your Operator dashboard. Operator holds both connections and refreshes the access tokens for you, so your agent keeps working across them without you signing in again.
- What can my agent do across GitHub and Microsoft teams?
- You describe the outcome in plain language and your agent works between the two, reading from one and acting in the other. It picks the right GitHub and Microsoft teams actions on its own, so you do not map fields or pick triggers.
- Can my agent keep GitHub and Microsoft teams in sync?
- Yes. It can watch GitHub and act in Microsoft teams, or keep both in step, reading from one and running the matching update in the other. This runs on demand when you ask or on a schedule you set.
- Do I need to build a workflow or write code?
- No. There is no workflow to build, no fields to map, and no API keys to paste. Operator manages both connections, and you give the agent instructions in plain language.
GitHub and Microsoft teams integrations
Put your agent on GitHub and Microsoft teams
Sign in, connect both apps, and hand your agent the work. The same setup reaches every app in the catalog. Your first week is free.
Try for free