Operator
← All integrations
GitHub logo+Outlook logo

Connect GitHub to Outlook

Automate GitHub and Outlook with AI

Engineering updates that live only in GitHub never reach the people who live in Outlook. Your Operator agent on OpenClaw watches pull requests, releases, and failed checks in GitHub, then sends formatted summaries or approval requests to the Outlook threads and distribution lists you name. Reply in mail asking to merge or hold and it acts on the linked GitHub item when you confirm.

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 Outlook

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...

All 846 GitHub actions →

What your agent does in Outlook

  • Accept calendar event invite

    Accepts or tentatively accepts a calendar meeting invite on behalf of a user. Use this action when a user has received a meeting invitation and wants to indicate their attendance status (either confirmed or tentative). The organizer will...

  • Add event attachment

    Adds an attachment to a specific Outlook calendar event. Use when you need to attach a file or nested item to an existing event.

  • Add mail attachment

    Tool to add an attachment to an email message. Use when you have a message ID and need to attach a small (<3 MB) file or reference.

  • Batch move messages

    Batch-move up to 20 Outlook messages to a destination folder in a single Microsoft Graph $batch call. Use when moving multiple messages to avoid per-message move API calls.

  • Batch update messages

    Batch-update up to 20 Outlook messages per call using Microsoft Graph JSON batching. Use when marking multiple messages read/unread or updating other properties to avoid per-message PATCH calls.

  • Create Calendar Event

    Creates a new Outlook calendar event, ensuring `start_datetime` is chronologically before `end_datetime`.

All 282 Outlook actions →

How it works

Tell the agent what you want to happen between GitHub and Outlook, 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 Outlook 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 Outlook

How do I connect GitHub and Outlook to Operator?
You authorize GitHub and Outlook 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 Outlook?
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 Outlook actions on its own, so you do not map fields or pick triggers.
Can my agent keep GitHub and Outlook in sync?
Yes. It can watch GitHub and act in Outlook, 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 Outlook integrations

Put your agent on GitHub and Outlook

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