--- title: "Connect GitLab and Pleo - APIANT.ai" description: "When \"New Code Snippet Comment\" fires in GitLab, your agent runs \"Add tax code\" in Pleo, or \"New Employee\" in Pleo to \"Add Note to Issue\" in GitLab." canonical: "https://apiant.ai/connect/gitlab-to-pleo" --- # Connect GitLab and Pleo When **New Code Snippet Comment** fires in [GitLab](https://apiant.ai/connections/gitlab), your agent runs **Add tax code** in [Pleo](https://apiant.ai/connections/pleo), or **New Employee** in Pleo to **Add Note to Issue** in GitLab. Describe the whole flow and it is built, tested on every scenario and kept running. GitLab **21** triggers GitLab **62** actions Pleo **2** triggers Pleo **24** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want GitLab and Pleo to do together? Give your AI client this address. `https://mcp.apiant.ai` One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser. ### Set it up in your client ### Claude Code Run this in the directory you want to work in. `claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### Claude, web and desktop Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Cursor Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Codex and the ChatGPT desktop app Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Any other MCP client Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) Example flows ## What GitLab and Pleo can do together ### From GitLab to Pleo - When **New Code Snippet Comment** in GitLab then **Add tax code** in Pleo - When **New Commit** in GitLab then **Add account** in Pleo ### From Pleo to GitLab - When **New Employee** in Pleo then **Add Note to Issue** in GitLab - When **New Tag** in Pleo then **Create Issue** in GitLab Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships. Everything your agent can do with GitLab and Pleo ## Triggers and actions 23 triggers · 86 actions - Trigger **Deployment Event (instant)** Fires on a deployment status change (deployment_events). - Trigger **New Code Snippet Comment** Triggers when a new comment is made on a code snippet in the selected project - Trigger **New Commit** Triggers when a new commit is pushed to a GitLab project's repository. - Trigger **New Commit Comment** Triggers when a new comment is made on a commit in the selected project - Trigger **New Group Issue Event** Triggers on group issue events, e.g. when an issue is opened, updated, or closed. - Trigger **New Group Merge Request Event** Triggers on an open, merge, close, or update merge request event. - Trigger **New Issue** Triggers when a new issue is created in a GitLab project. - Trigger **New Issue Comment** Triggers when a new comment is made on an issue in the selected project - Trigger **New Job Event** Triggers for a specified job event in a project. - Trigger **New Merge Request** Triggers when a new merge request is opened in a GitLab project. - Trigger **New Merge Request Comment** Triggers when a new comment is made on a merge request in the selected project - Trigger **New Pipeline** Triggers when a new CI/CD pipeline is created in a GitLab project. - Trigger **New Project** Triggers when a new GitLab project is created that the connected user can see. - Trigger **New Project Issue Event** Triggers on project issue events, e.g. when an issue is opened, updated, or closed. - Trigger **New Project Merge Request Event** Triggers on an open, merge, close, or update merge request event. - Trigger **New Release** Triggers when a new release is created in a GitLab project. - Trigger **New Release (instant)** Fires when a release is created or updated (releases_events). - Trigger **New Tag** Triggers when a new tag is added to a GitLab project's repository. - Trigger **New Tag (instant)** Fires when a tag is pushed (tag_push_events). - Trigger **Pipeline Event (instant)** Fires on a pipeline status change (pipeline_events). - Trigger **Wiki Page Event (instant)** Fires when a wiki page is created or updated (wiki_page_events). - Action **Accept Merge Request** Merges an open merge request into its target branch, optionally squashing commits, deleting the source branch, or setting it to merge automatically once checks pass. - Action **Add Comment to Commit** Adds a comment to a commit in a GitLab project, optionally on a specific line of a file. - Action **Add Note to Issue** Adds a comment to an issue in a GitLab project. - Action **Add Note to Merge Request** Adds a comment to a merge request in a GitLab project. - Action **Add Note to Snippet** Adds a comment to a project snippet in GitLab and returns the created comment. - Action **Approve Merge Request** Approves a merge request as the connected GitLab user and returns the merge request's updated approval state. - Action **Cancel Pipeline** Cancels all running and pending jobs in a GitLab pipeline and returns the pipeline with its updated status. - Action **Create Branch** Creates a new branch in a GitLab project's repository from an existing branch or commit. - Action **Create Commit** Creates a commit on a branch of a GitLab project, applying a batch of file changes (create, update, delete, move, chmod). - Action **Create File** Creates a new file in a GitLab project's repository by committing it to a branch. - Action **Create Issue** Creates a new issue in a GitLab project, with optional description, labels, assignees, milestone and due date. - Action **Create Label** Creates a label in a GitLab project with the name and color you choose. - Action **Create Merge Request** Creates a new merge request in a GitLab project from a source branch to a target branch. - Action **Create Milestone** Creates a milestone in a GitLab project, with an optional description, start date and due date. - Action **Create Pipeline** Starts a new CI/CD pipeline on a branch or tag of a GitLab project, optionally with pipeline variables and inputs. - Action **Create Project** Creates a new GitLab project in your personal namespace or in a group you choose. - Action **Create Release** Creates a release in a GitLab project from an existing tag, or from a branch or commit that is tagged as part of the release. - Action **Create Snippet** Creates a personal snippet with a title and one file of content in your GitLab account. - Action **Create Tag** Creates a new Git tag in a GitLab project pointing at a branch, commit or existing tag. Add a message to make it an annotated tag. - Action **Create Wiki Page** Creates a new wiki page in a GitLab project with the given title and content. - Action **Delete Branch** Deletes a branch from a GitLab project's repository. The default branch and protected branches cannot be deleted. - Action **Delete File** Deletes a file from a GitLab project's repository by committing its removal to a branch. - Action **Delete Issue** Deletes an issue from a GitLab project. Only administrators and project owners can delete issues. - Action **Delete Tag** Deletes a tag from a GitLab project's repository. - Action **Find Group Merge Requests** Returns merge requests across a GitLab group and its subgroups, filtered by state, author, assignee, reviewer, labels, milestone, branch, dates or search text. - Action **Find Project Merge Requests** Finds merge requests in a GitLab project, filtered by text search, state, author, assignee, reviewer, labels, branches, dates and more. - Action **Find Projects** Finds GitLab projects whose name, path or description matches your search text, optionally narrowed by membership, ownership, visibility, topic and activity dates. - Action **Find User** Finds GitLab users by username, public email, or a name/username/email search, with optional filters on account state and type. - Action **Get Branch** Returns a repository branch in a GitLab project, including its protection status, merge status and latest commit. - Action **Get Commit** Returns a single commit from a project's repository, identified by its SHA or by a branch or tag name, including stats and the latest pipeline. - Action **Get File** Returns a file from a GitLab repository, including its name, size, commit details and Base64-encoded content. - Action **Get Group** Returns the details of a GitLab group, such as its name, path, visibility and parent group. - Action **Get Issue** Returns a single issue in a GitLab project, including its title, description, state, labels, assignees and milestone. - Action **Get Job** Returns a single CI/CD job in a GitLab project, including its status, stage, pipeline, commit and runner details. - Action **Get Merge Request** Returns a single merge request in a GitLab project, including its state, branches, author, reviewers and pipeline. - Action **Get Merge Request Approvals** Returns the approval state of a merge request: whether it is approved, who approved it, and how many approvals are still required. - Action **Get Pipeline** Returns a single CI/CD pipeline in a project, including its status, ref, commit, timing and who triggered it. - Action **Get Project** Returns a single GitLab project by its ID or full path, including its settings, visibility and links. - Action **Get Release** Returns a project's release for the given Git tag, including its description, commit, milestones and assets. - Action **Get Snippet** Returns a personal snippet by its ID, including its title, file name, visibility, author and links. - Action **Get Snippet Note** Returns a single comment (note) posted on a project snippet. - Action **Get Wiki Page** Returns a wiki page from a GitLab project, including its title, content and format. - Action **List Branches** Returns the branches in a GitLab project's repository, sorted by name, optionally filtered by a search term or regular expression. - Action **List Commit Comments** Returns the comments left on a commit in a GitLab project. - Action **List Commits** Returns the commits in a GitLab project's repository, optionally filtered by branch, author, file path or date range. - Action **List Groups** Returns the GitLab groups visible to the connected user, optionally filtered by name, visibility, ownership or access level. - Action **List Labels** Returns the labels defined for a GitLab project, optionally filtered by keyword and including issue and merge request counts. - Action **List Milestones** Returns the milestones of a GitLab project, optionally filtered by state, title, search text or dates. - Action **List Pipelines** Returns the pipelines in a GitLab project, optionally filtered by branch, status, commit, date range or user. - Action **List Project Jobs** Returns the CI/CD jobs in a project, newest first, optionally filtered to one job status such as success or failed. - Action **List Project Members** Returns the direct members of a GitLab project, optionally filtered by name, email or username. - Action **List Releases** Returns the releases of a GitLab project, newest first by release date. - Action **List Tags** Returns the Git tags in a GitLab project's repository, optionally filtered by name and sorted. - Action **Retry Job** Retries a single CI/CD job in a GitLab project and returns the new job that was queued. - Action **Retry Pipeline** Retries the failed or canceled jobs in a GitLab pipeline and returns the updated pipeline. - Action **Update File** Updates the content of an existing file in a GitLab repository by committing the change to a branch. - Action **Update Issue** Updates an existing issue in a GitLab project, including closing or reopening it, changing its title, description, labels, assignees, milestone or dates. - Action **Update Merge Request** Updates an existing merge request in a GitLab project — title, description, assignees, reviewers, labels, milestone, target branch or state. - Action **Update Milestone** Updates a project milestone's title, description, dates, or open/closed state. - Action **Update Project** Updates an existing GitLab project's name, description, visibility, default branch, topics, merge settings and feature visibility. Returns the updated project. - Action **Update Release** Updates an existing release's name, description, milestones or release date in a GitLab project. - Action **Update Wiki Page** Updates the title, content or format of an existing wiki page in a GitLab project. - Trigger **New Employee** Triggered when a new employee is added in Pleo. - Trigger **New Tag** Triggers when a new tag is added to the selected tag group. - Action **Add account** Creates an account in a Pleo company's chart of accounts, matching a record in your accounting system, and returns the new account. - Action **Add tag group** Creates a new tag group (a cost-centre dimension such as Projects or Departments) in Pleo. - Action **Add tax code** Creates a tax code in a Pleo company, with its name, rate and type. - Action **Add team** Creates a new team in a Pleo company or organisation and returns the created team. - Action **Create Tag** Creates a new tag in a Pleo tag group, such as a cost centre or project, and returns the created tag. - Action **Delete tag** Deletes a tag from Pleo by its ID. - Action **Delete tag group** Deletes a tag group from Pleo by its ID. - Action **Delete tax code** Deletes a tax code from a Pleo company. - Action **Get an Employee** Returns one Pleo employee by ID, including their name, email, job title, phone, role, company and avatar. - Action **Get company balance** Returns the current balance of every Pleo account belonging to a company, including available funds, pending debits and overdraft. - Action **Get Expense** Returns a single Pleo expense (accounting entry) by its ID, including its amounts, merchant, category, tags, review and export status, and receipt IDs. - Action **Get tag** Returns a Pleo tag by its ID, including its name, code, tag group and archived status. - Action **Get tag group** Returns a tag group by its ID, including its name, code, archived status, metadata and total number of tags. - Action **Get Tax Code** Returns a single tax code from Pleo, including its name, rate, type and archived status. - Action **Get team** Returns a Pleo team by its ID, including its name, code, company, organisation and employee IDs. An error occurs if the team is not found. - Action **List accounts** Returns the accounts in a Pleo company's chart of accounts, optionally narrowed by name, code, external ID, account ID or archived status. - Action **List employees** Returns the employees in your Pleo company, optionally filtered by company, email or external ID. - Action **List tag groups** Returns the tag groups for a Pleo company, or for all companies in an organisation. - Action **List tags** Returns the tags in a Pleo tag group, optionally including archived tags. - Action **List tax codes** Returns the tax codes for a Pleo company, optionally filtered by code, type, archived status or specific tax code IDs. - Action **List teams** Returns the teams in a Pleo company or organisation, optionally filtered by name, member employee or team. - Action **Update tag** Updates a tag's code, name, archived state and additional dimension values in Pleo, and returns the updated tag. - Action **Update tag group** Updates a tag group's name, code, archived status and metadata. All values replace the tag group's current ones. - Action **Update tax code** Updates an existing tax code in Pleo, including its name, rate, type and archived status, and returns the updated tax code. ## Each app on its own - [ **GitLab** GitLab is an open source code collaboration tool with a rich feature set including management of...](https://apiant.ai/connections/gitlab) - [ **Pleo** Pleo offers smart company cards that automate expense reports and simplify company spending.](https://apiant.ai/connections/pleo) Reviews ## What our customers say ## More from GitLab - [ **GitLab to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/gitlab-to-hubspot) - [ **GitLab to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/gitlab-to-salesforce) - [ **GitLab to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/gitlab-to-slack) - [ **GitLab to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/gitlab-to-google-sheets) - [ **GitLab to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gitlab-to-gmail) - [ **GitLab to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/gitlab-to-google-calendar) ## More into Pleo - [ **HubSpot to Pleo** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-pleo) - [ **Google Sheets to Pleo** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-pleo) - [ **Gmail to Pleo** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-pleo) - [ **Google Calendar to Pleo** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-pleo) - [ **Google Drive to Pleo** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-pleo) - [ **Mailchimp to Pleo** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/mailchimp-to-pleo) Questions ## GitLab and Pleo, answered ### ### What can start an automation from GitLab? Any of GitLab's 21 triggers in the catalog, including New Code Snippet Comment, New Commit, New Commit Comment and New Group Issue Event. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Pleo when something happens in GitLab? Any of Pleo's 24 actions, including Create Tag, Update tag, Update tag group and Update tax code. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Pleo to GitLab? Yes. When something happens in Pleo, your agent can act in GitLab too. This page covers both directions: Pleo's triggers and GitLab's actions are listed here as well. ### ### Do I have to build a connector for GitLab or Pleo? No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running. ### ### Can my AI client use GitLab and Pleo without building an automation? Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both. ### ### What happens when something fails? Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships. ### ### Is there a free plan? Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.