--- title: "Connect GitLab and Greenhouse - APIANT.ai" description: "When \"New Code Snippet Comment\" fires in GitLab, your agent runs \"Create Candidate Note\" in Greenhouse." canonical: "https://apiant.ai/connect/gitlab-to-greenhouse" --- # Connect GitLab and Greenhouse When **New Code Snippet Comment** fires in [GitLab](https://apiant.ai/connections/gitlab), your agent runs **Create Candidate Note** in [Greenhouse](https://apiant.ai/connections/greenhouse), or **Application Updated** in Greenhouse 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 Greenhouse **15** triggers Greenhouse **38** 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 Greenhouse 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 Greenhouse can do together ### From GitLab to Greenhouse - When **New Code Snippet Comment** in GitLab then **Create Candidate Note** in Greenhouse - When **New Commit** in GitLab then **Add Attachment to Candidate** in Greenhouse ### From Greenhouse to GitLab - When **Application Updated** in Greenhouse then **Add Note to Issue** in GitLab - When **Candidate Updated** in Greenhouse 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 Greenhouse ## Triggers and actions 36 triggers · 100 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 **Application Rejected** Triggers when an application in Greenhouse is rejected, returning the rejected application with its candidate, job, rejection reason and custom fields. - Trigger **Application Updated** Triggers when an application is created or updated in Greenhouse, including stage moves, rejections and hires. - Trigger **Candidate Hired** Triggers when a candidate's application is marked as hired in Greenhouse, delivering the hired application. - Trigger **Candidate Updated** Triggers when a candidate is created or updated in Greenhouse, returning the candidate's profile, contact details, tags and custom fields. - Trigger **Job Updated** Triggers when a job (hiring plan) is created or updated in Greenhouse. - Trigger **New Candidate** Triggers when a new candidate or prospect is added to Greenhouse. - Trigger **New Candidate Application** Triggers when a new application is submitted or added for a candidate in Greenhouse, optionally limited to specific jobs, stages, sources or statuses. - Trigger **New Job** Triggers when a new job (requisition / hiring plan) is created in Greenhouse. - Trigger **New Job Post** Triggers when a new job post (a candidate-facing listing of a job) is created in Greenhouse. - Trigger **New Note** Triggers when a new note is added to a candidate's profile in Greenhouse, including logged emails and activity entries. - Trigger **New Offer** Triggers when a new offer is created on a candidate's application in Greenhouse. - Trigger **New Scheduled Interview** Triggers when an interview on a candidate's application is scheduled on the calendar in Greenhouse. - Trigger **New Scorecard** Triggers when an interviewer submits a scorecard for a candidate's interview in Greenhouse. - Trigger **New Scorecard Due** Triggers when an interview has taken place and the interviewer's scorecard is still in draft, waiting to be submitted. - Trigger **Offer Updated** Triggers when an offer is created or updated in Greenhouse, including status changes such as accepted or rejected. - Action **Add Attachment to Candidate** Attaches a file (resume, cover letter, offer letter or other document) to a candidate's application in Greenhouse, from a public file URL or base64 file content. - Action **Add Candidate Education** Adds an education entry (school, degree, field of study and dates) to a candidate's profile in Greenhouse. - Action **Add Candidate Employment** Adds a work history entry (employer, job title and dates) to a candidate's profile in Greenhouse. Leave the end date blank to record it as the candidate's current job. - Action **Add Tag to Candidate** Applies an existing tag from your organization's tag list to a candidate. Returns the applied tag record. - Action **Convert Prospect to Candidate** Converts a prospect application into a candidate application on a job, optionally placing it on a chosen interview stage. Returns the new candidate application. - Action **Create Application** Creates a new application for an existing Greenhouse candidate, either on a job or as a prospect application. - Action **Create Candidate** Creates a new candidate in Greenhouse, either applied to a job or as a prospect, and returns the new candidate and their application. - Action **Create Candidate Note** Adds a note, logged email, or activity-feed entry to a Greenhouse candidate, optionally tied to one of their applications. - Action **Create Interview** Records an interview that is already scheduled on an external calendar against a candidate's application, at a chosen slot on the job's interview plan. It does not create a calendar event or send invites. - Action **Create Job** Creates a new job in Greenhouse from an existing template job, with the requested number of openings, department, offices and custom field values. - Action **Create Job Note** Adds a note to a job in Greenhouse, written on behalf of the user you choose and visible to job admins or to users allowed to see private job notes. - Action **Create Job Post** Creates a new job post by copying an existing job post onto a job board, optionally with a new title, description, and publication status. - Action **Create Offer** Creates an offer on an existing Greenhouse application, with an optional start date, opening and offer/compensation custom field values. - Action **Create Opening** Adds a new opening (headcount slot) to an existing Greenhouse job, optionally with your own position id and opening custom field values. - Action **Create Prospect** Creates a new prospect in Greenhouse: a candidate profile with a prospect application, optionally tied to jobs, a prospect pool, a department or an office. - Action **Delete Application** Permanently deletes a single application, along with its interview stages, scorecards and rejection details. The candidate and their other applications are kept. - Action **Delete Candidate** Permanently deletes a candidate along with all of their applications, attachments, scorecards and notes. This cannot be undone. - Action **Delete Interview** Cancels and deletes a scheduled interview in Greenhouse, along with its interviewer assignments and reminders. Only interviews that are scheduled or awaiting feedback can be deleted. - Action **Delete Note** Permanently deletes a note from a candidate's activity feed. This cannot be undone. - Action **Delete Opening** Permanently removes an opening from its job. Only closed openings with no offer and no hired application can be deleted. - Action **Find Application** Returns up to 100 job applications that match a free-text search and/or filters such as candidate, job, stage, source, department, office or hiring team. - Action **Find Candidate** Returns up to 100 candidates and prospects that match a free-text search and/or filters such as job, stage, tag, source or recruiter, plus the first match on its own. - Action **Find Due Scorecard** Finds scorecards that are still due — interview evaluations an interviewer has not yet submitted — for the applications, interviewers or interview kits you specify. - Action **Find Job** Returns up to 100 jobs matching a free-text search term and optional filters such as status, department, office, hiring team member or custom field answer. - Action **Find Offer** Finds offers extended to candidates, filtered by application, candidate, job, opening, status or date, and returns the matching offers plus the first match. - Action **Hire Application** Marks a candidate's application as hired and closes the matching opening on the job. - Action **Merge Candidates** Merges a duplicate candidate into another candidate. The primary candidate keeps its profile and absorbs the duplicate's applications, attachments, notes and tags; the duplicate is deleted. - Action **Move Application** Moves an application to a different interview stage on the same job, or transfers it to another job. Stage transition rules, including automated emails, fire as they would in Greenhouse. - Action **Reject Application** Rejects a candidate's application with a rejection reason, optionally sending the candidate a templated rejection email and setting application custom fields. - Action **Remove Tag from Candidate** Removes a tag from a candidate by deleting the applied-tag record. The tag itself stays in your Greenhouse tag list. - Action **Unreject Application** Reverses a rejection on an application, returning it to the in-process state on the stage it was rejected from. The earlier rejection reason and notes are cleared. - Action **Update Application** Updates the attribution and details of an existing Greenhouse application, such as its source, referrer, recruiter, coordinator, prospect pool and stage, and custom fields. - Action **Update Candidate** Updates an existing Greenhouse candidate's profile — name, company, title, contact details, tags, linked users and custom fields. Only the values you fill in are changed. - Action **Update Interview** Updates a scheduled interview's time, location, video conferencing link, calendar event id, organizer or interviewer panel. Changes the Greenhouse record only and sends no calendar invites. - Action **Update Job** Updates an existing Greenhouse job's name, notes, offices, department, requisition id and custom fields, and returns the updated job. - Action **Update Job Post** Updates a Greenhouse job post: change its public title, replace its description, or publish it (live) or return it to draft. - Action **Update Offer** Updates an existing offer's start date, opening, sent/created/resolved dates and offer custom fields, including compensation. Returns the updated offer. - Action **Update Opening** Updates an opening on a Greenhouse job — its external id, target start date, custom fields, or open/closed status with a close reason. ## 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) - [ **Greenhouse** Greenhouse is a hiring software company. We create the technology, know-how and support for your business'...](https://apiant.ai/connections/greenhouse) 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](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 Greenhouse - [ **Google Sheets to Greenhouse** Google Sheets](https://apiant.ai/connect/google-sheets-to-greenhouse) - [ **Gmail to Greenhouse** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-greenhouse) - [ **Google Calendar to Greenhouse** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-greenhouse) - [ **Google Drive to Greenhouse** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-greenhouse) - [ **ActiveCampaign to Greenhouse** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-greenhouse) - [ **Airtable to Greenhouse** Organize anything with Airtable, a modern database created for everyone.](https://apiant.ai/connect/airtable-to-greenhouse) Questions ## GitLab and Greenhouse, 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 Greenhouse when something happens in GitLab? Any of Greenhouse's 38 actions, including Create Application, Create Candidate, Create Candidate Note and Create Interview. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Greenhouse to GitLab? Yes. When something happens in Greenhouse, your agent can act in GitLab too. This page covers both directions: Greenhouse's triggers and GitLab's actions are listed here as well. ### ### Do I have to build a connector for GitLab or Greenhouse? 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 Greenhouse 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.