--- title: "Connect GitLab and Gravity Forms - APIANT.ai" description: "When \"New Code Snippet Comment\" fires in GitLab, your agent runs \"Add Entry Note\" in Gravity Forms." canonical: "https://apiant.ai/connect/gitlab-to-gravity-forms" --- # Connect GitLab and Gravity Forms When **New Code Snippet Comment** fires in [GitLab](https://apiant.ai/connections/gitlab), your agent runs **Add Entry Note** in [Gravity Forms](https://apiant.ai/connections/gravity-forms), or **Form Submission** in Gravity Forms 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 Gravity Forms **1** trigger Gravity Forms **30** 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 Gravity Forms 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 Gravity Forms can do together ### From GitLab to Gravity Forms - When **New Code Snippet Comment** in GitLab then **Add Entry Note** in Gravity Forms - When **New Commit** in GitLab then **Create Entry** in Gravity Forms ### From Gravity Forms to GitLab - When **Form Submission** in Gravity Forms then **Add Note to Issue** in GitLab - When **Form Submission** in Gravity Forms 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 Gravity Forms ## Triggers and actions 22 triggers · 92 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 **Form Submission** Triggers when the specified form is submitted. - Action **Add Entry Note** Adds a note to a form entry. Use it to write a progress record back onto a submission — for example noting that the submission was synced to your CRM, who handled it, or why it was skipped — so the note is visible to anyone reviewing that entry in WordPress. - Action **Create Entry** Creates a new form entry. - Action **Create Feed** Attaches a new add-on feed to a form. A feed is one add-on's configuration on a form — the rule that says what should happen when the form is submitted, such as creating a WordPress user, adding the person to a mailing list, or taking a payment. - Action **Create Form** Creates a new form on the WordPress site and returns its id. Supply the form's title and, if you want the form ready to collect data, the fields it should show. - Action **Create Form Feed** Attaches a new add-on feed to a named form. Does the same thing as Create Feed, but takes the form as part of the address rather than in the settings — use whichever reads better in your automation. - Action **Delete Entry** Removes a form entry. By default the entry is moved to the trash and can still be restored from the Entries list; you can choose instead to delete it outright so it cannot be recovered. - Action **Delete Feed** Permanently removes an add-on feed from a form, so that add-on no longer acts on the form's submissions. The form itself and its entries are untouched. - Action **Delete Form** Moves a form to the trash on the WordPress site. The form stops accepting submissions and disappears from the forms list, and the site owner can still restore it or empty the trash in WordPress. - Action **Delete Note** Permanently removes an entry note. Use it to clear a note you logged against a submission, for example after a failed sync was retried successfully. - Action **Get Entry** Retrieve a single form entry, including every field value the person submitted. - Action **Get Feed** Returns one add-on feed by its id, including the add-on's settings. A feed is one add-on's configuration attached to a form — the rule that says what should happen when the form is submitted. - Action **Get Form** Returns one form's full definition, including every field on it, its notifications and its confirmations. Use it to read a form's field ids and labels before mapping data into that form. - Action **Get Form Results** Returns the summarised answers for a survey, quiz or poll form — how many people picked each choice, and how many answered each free-text question — rather than the individual entries. On a form with a lot of entries the summary is built in the background, so the result can come back marked as still being calculated. - Action **Get Note** Returns a single entry note by its id, including the note text, the entry it belongs to, when it was recorded and who it is credited to. - Action **List Entries** Returns form entries from across every form on the site, newest first, and can narrow the results to one form or to entries whose answer to a chosen question matches a value you give. - Action **List Entry Notes** Returns every note attached to one form entry — both notes people have added and the notes Gravity Forms records automatically, such as notification failures. Use it to read back what has already been logged against a submission. - Action **List Feeds** Returns every add-on feed configured on the site. A feed is one add-on's configuration attached to a form — the rule that says what should happen to a submission, such as sending it to a mailing list or charging a payment. - Action **List Form Entries** Returns the entries submitted on one particular form, newest first, and can narrow them to entries whose answer to a chosen question matches a value you give. - Action **List Form Feeds** Returns the add-on feeds attached to one form — the rules that say what happens when that form is submitted. Returns an empty list when the form has no feeds. - Action **List Forms** Returns every active form on the WordPress site, with each form's id, title and entry count. Use it to look up the id a form needs before working with that form's entries. - Action **List Notes** Returns every entry note on the site, across all forms and entries. Use it to sweep recently logged notes when you do not already know which entry you are looking for; to read the notes on one known entry, use List Entry Notes instead. - Action **Send Entry Notifications** Sends the notification emails an entry's form is set up to send, for an entry that already exists — useful for re-sending a confirmation, or for notifying people about an entry that was created through the API rather than by someone filling the form in. - Action **Submit Form** Submit a form the way a visitor would — Gravity Forms runs the form's own validation, saves the entry, and fires its notifications and confirmation. - Action **Update Entry** Change the answers on an existing form entry. Answers you leave blank keep the values they already have. - Action **Update Entry Properties** Changes an entry's housekeeping flags without touching any of its answers — whether it is starred, whether it counts as read, and whether it sits in the active list, the trash or spam. - Action **Update Feed** Changes an existing add-on feed's settings. Settings you do not include are left as they are, so you can change one thing without restating the rest of the add-on's configuration. - Action **Update Feed Properties** Switches an add-on feed on or off, and sets the order it runs in. The add-on's own settings are left completely untouched, so this is the safe way to pause a feed without risking its configuration. - Action **Update Form** Replaces an existing form's definition with the one you supply. Gravity Forms overwrites the whole form, so read the form first with Get Form and send back every part of it you want to keep. - Action **Update Note** Replaces the text of an existing entry note. Use it to revise a note you logged earlier against a submission — for example updating "Sync started" to "Synced to CRM as contact 4821". - Action **Validate Submission** Checks a set of answers against a form's own validation rules without saving an entry or sending any notifications. Returns whether the answers would be accepted, and the per-field error messages when they would not. ## 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) - [ **Gravity Forms** Gravity Forms is a premier WordPress plugin that makes it easy to create powerful forms on the fly.](https://apiant.ai/connections/gravity-forms) 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 Gravity Forms - [ **Adyen to Gravity Forms** Payment infrastructure platform enabling enterprises to accept, settle, and move funds globally with...](https://apiant.ai/connect/adyen-to-gravity-forms) - [ **Slack to Gravity Forms** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-gravity-forms) - [ **Google Calendar to Gravity Forms** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-gravity-forms) - [ **Google Drive to Gravity Forms** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-gravity-forms) - [ **ActiveCampaign to Gravity Forms** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-gravity-forms) - [ **Notion to Gravity Forms** A new tool that blends your everyday work apps into one. It's the all-in-one workspace for you and your team.](https://apiant.ai/connect/notion-to-gravity-forms) Questions ## GitLab and Gravity Forms, 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 Gravity Forms when something happens in GitLab? Any of Gravity Forms's 30 actions, including Create Entry, Create Feed, Create Form and Create Form Feed. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Gravity Forms to GitLab? Yes. When something happens in Gravity Forms, your agent can act in GitLab too. This page covers both directions: Gravity Forms's triggers and GitLab's actions are listed here as well. ### ### Do I have to build a connector for GitLab or Gravity Forms? 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 Gravity Forms 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.