GitHub integration

Developer Tools & Infrastructure · 16 actions · OAuth or Bearer token auth

GitHub repository and code management platform

Put GitHub to work View GitHub integration docs

Overview

The ModuleX GitHub integration lets a ModuleX agent operate GitHub on your behalf — running create, update and remove actions across repositories, issues and pull requests — directly from a plain-English request, using your organization's own GitHub credentials. No pre-built workflow is required: the agent picks the right GitHub action for the task.

GitHub is a developer tools & infrastructure platform. ModuleX adds the agent layer: ask for an outcome and it selects and runs the right GitHub action — or, when you want a repeatable process, the composer assembles a GitHub workflow for you, streaming the nodes onto the canvas as it builds.

Ask the assistant

Drive GitHub in plain English

Type what you want. A ModuleX agent picks the right GitHub action — or chains several — and runs it. No workflow to build.

Create a new repository
resolves tocreate_repository
Find the repository I describe and remove it
resolves tolist_repositoriesdelete_repository
Update an existing issue
resolves toupdate_issue
Show me the repositories that match what I describe
resolves toget_repository

Use cases

What you can automate with GitHub

Find the right repository and remove it in one promptlist_repositoriesdelete_repository
Pull a list of issues for a reportlist_issues
Create a pull request straight from a requestcreate_pull_request
Look up a file content on demandget_file_content
Find the codes that match what you describesearch_code

At a glance

GitHub integration at a glance

VendorGitHub

CategoryDeveloper Tools & Infrastructure

Actions available16

AuthenticationOAuth or Bearer token

Uses your own credentialsYes

Works with the assistantYes

Works in the composerYes

Multi-step / tool-chainingYes

Technical referenceView docs

Integration version1.0.0

Last updatedJun 2026

Reference

All 16 GitHub actions

Repositories4

list_repositories

List repositories for the authenticated user or organization

create_repository

Create a new repository

delete_repository

Delete a repository (irreversible, requires delete_repo scope)

get_repository

Get repository details

Issues4

list_issues

List issues for a repository

create_issue

Create a new issue

get_issue

Get issue details

update_issue

Update an existing issue

Pull Requests4

list_pull_requests

List pull requests for a repository

create_pull_request

Create a new pull request

get_pull_request

Get pull request details

merge_pull_request

Merge a pull request

Branches1

create_branch

Create a new branch

File Contents1

get_file_content

Get file contents from a repository

Commits1

create_commit

Create a commit with file changes

Codes1

search_code

Search for code in repositories

See full parameters and response schemas in the GitHub integration docs

Two ways

Two ways to use GitHub in ModuleX

Ask the assistantType what you want done and a ModuleX agent picks the right GitHub action and runs it — no workflow to build.

Compose a workflowNeed it to happen every time? Describe the process and the composer wires GitHub into a repeatable workflow you can run on a schedule, from chat, or as an API.

Security

Connecting GitHub

OAuthGitHub uses OAuth. You connect your GitHub account once; ModuleX stores the access token encrypted and scoped to your organization, so your team shares a single secure connection.

Bearer tokenGitHub uses bearer-token authentication. You provide a GitHub access token; ModuleX encrypts it and scopes it to your organization so the whole team can use GitHub.

Step-by-step setup in the GitHub docs

Pairs well with GitHub

Agents often chain GitHub with these — connect them once and the agent can use all of them in a single task.

Microsoft Entra ID12 actions

FAQ

GitHub + ModuleX FAQ

A ModuleX agent can run any of GitHub's 16 actions — across repositories, issues, pull requests and branches — from a plain-English request, using your organization's own GitHub credentials.

No. The agent selects the right GitHub action from your prompt. A workflow is only needed when you want a repeatable process — and the composer builds that for you from a description.

Through OAuth — you connect your GitHub account once and ModuleX stores the token encrypted, scoped to your organization.

16, spanning repositories, issues, pull requests and branches.

GitHub runs on your own credentials, so any GitHub usage is billed by GitHub directly. ModuleX meters the agent run — and if you connect your own model keys, there's no ModuleX markup on model usage.

Put GitHub to work in ModuleX.

Connect GitHub once with your own credentials and let your agent run all 16 actions on demand.

Put GitHub to work View technical docs

Last updated: Jun 2026Browse all 175 integrations →