+
Connect Discord to GitHub
Automate Discord and GitHub with AI
Open source and dev communities on Discord want GitHub activity without living in email alerts. Operator.io runs OpenClaw on Discord and GitHub so new issues, pull requests, and releases post to the channel your contributors read, and a Discord message can become a GitHub issue with labels and repo filled from context. Ask for the state of a repo and it reads GitHub and answers 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 Discord and GitHub
What your agent does in Discord
Consume Entitlement
Marks a one-time purchase consumable entitlement as consumed for a given application. Only applicable to entitlements backed by one-time purchase consumable SKUs.
Delete Test Entitlement
Deletes a currently active test entitlement for a given application. Use this to clean up test entitlements that are no longer needed.
Delete User Application Role Connection
Deletes the current user's application role connection for the specified application. Removes the platform metadata and linked role connection.
Edit Application Command Permissions
Edits the permissions for a specific application command in a guild. Requires OAuth2 Bearer token (bot tokens will error). The authorizing user must have MANAGE_GUILD and MANAGE_ROLES permissions in the target guild.
Get Application Command Permissions
Retrieves the permissions for a specific application command in a guild. Requires OAuth2 Bearer token (bot tokens will error). The authorizing user must have MANAGE_GUILD and MANAGE_ROLES permissions in the target guild.
Get Batch Application Command Permissions
Retrieves permissions for all commands of an application in a guild. Returns a list of permission objects for each command. Requires OAuth2 Bearer token (Bot tokens will error).
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...
How it works
Tell the agent what you want to happen between Discord and GitHub, for example to watch one and act in the other, or to keep the two in step. It reads what it needs from Discord, works out what to do, and runs the matching action in GitHub 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 Discord and GitHub
- How do I connect Discord and GitHub to Operator?
- You authorize Discord and GitHub 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 Discord and GitHub?
- Tell it the job and it moves between Discord and GitHub as one task, choosing which actions to run on each side. There is nothing to map and no trigger to configure; you give instructions the way you would to a person.
- Can my agent keep Discord and GitHub in sync?
- Yes. It can watch Discord and act in GitHub, 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.
Discord and GitHub integrations
Put your agent on Discord and GitHub
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