+
Connect GitHub to Gitlab
Automate GitHub and Gitlab with AI
Some teams keep code on GitHub and CI on GitLab, and the two drift on branch and pipeline state. Your Operator agent on OpenClaw watches both so a GitHub merge can trigger or check the GitLab pipeline, failing pipelines post back against the GitHub pull request, and issues opened in one mirror to the other with a link. Ask which branches are green and it reads GitLab pipelines beside the open GitHub pull requests.
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 Gitlab
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 Gitlab
Archive Project
Tool to archive a project. Use when you need to mark a project read-only after finishing active development. Call after confirming no further changes are required.
Create GitLab Group
Tool to create a new group in GitLab. Use when you need to establish a new group for projects or collaboration.
Create Project
Tool to create a new project in GitLab. Implements POST /projects endpoint.
Create Project Issue
Tool to create a new issue in a GitLab project. Use when you need to report a bug, request a feature, or track a task within a specific project.
Create Repository Branch
Tool to create a new branch in a project. Use when you need to create a new branch from an existing branch or a specific commit in a GitLab project.
Delete Project
Tool to delete a GitLab project by its ID. Use when you need to remove a project, either by marking it for later deletion or deleting it immediately.
How it works
Tell the agent what you want to happen between GitHub and Gitlab, 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 Gitlab 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 Gitlab
- How do I connect GitHub and Gitlab to Operator?
- You authorize GitHub and Gitlab 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 Gitlab?
- 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 Gitlab actions on its own, so you do not map fields or pick triggers.
- Can my agent keep GitHub and Gitlab in sync?
- Yes. It can watch GitHub and act in Gitlab, 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 Gitlab integrations
Put your agent on GitHub and Gitlab
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