App Connector · Developer & cloud
GitLab
Ask about a merge request instead of opening five tabs.
Read issues, merge requests, files, and pipelines.
What you can do
A connector lets the assistant use an app or tool for you. Once connected, ask it to work with GitLab.
Read the work
Issues, merge requests, branches, and the files in your projects.
Check the pipeline
Pipeline status and job logs, including the output of the job that failed.
Reply and open
Comment on an issue or a merge request, and open one, after you approve the text.
Things you can ask
Type these in chat once the connector is on.
What you need
Sign in with your GitLab account when Plexon asks. GitLab on your own servers works too; enter its address during setup.
Setup details
Sign in with your GitLab account when Plexon asks. Self-hosted works too: swap the address for your own host and keep the same path. There is no token to create, because GitLab does not accept one here.
Plexon encrypts saved passwords and connection keys on your computer.
When a task uses an online app, that app receives the request. Its results may also be sent to the AI service handling your chat. You can turn the connector on for one workspace and leave it off for another.
Once GitLab is on
A connected app is a source. These are the parts of Plexon that draw on it.
- AI Chat & Modes
Turn one on with your own account and the assistant works inside that app.
- Dynamic Workflows
An inbound message or a poll on a connected app starts a run.
A Tool step calls a connector directly, spending zero AI tokens.
- Dashboards
A widget's data can come from a connector tool call, refreshed on a timer.
- Action Record & Tool Rules
A call to a connected app is written down before it runs and again when it ends, with the app named on the row.
More in Developer & cloud
Connectors stack: turn on several and the assistant moves work between them.
Connect GitLab to Plexon
Install Plexon, open Apps, and follow the setup steps for GitLab. Then describe what you want to do in chat.