--- title: "Connect Files.com and GitLab - APIANT.ai" description: "When \"Automation Run Completed\" fires in Files.com, your agent runs \"Add Note to Issue\" in GitLab." canonical: "https://apiant.ai/connect/files-com-to-gitlab" --- # Connect Files.com and GitLab When **Automation Run Completed** fires in [Files.com](https://apiant.ai/connections/files-com), your agent runs **Add Note to Issue** in [GitLab](https://apiant.ai/connections/gitlab), or **New Code Snippet Comment** in GitLab to **Add User to Group** in Files.com. Describe the whole flow and it is built, tested on every scenario and kept running. Files.com **7** triggers Files.com **16** actions GitLab **21** triggers GitLab **62** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Files.com and GitLab 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 Files.com and GitLab can do together ### From Files.com to GitLab - When **Automation Run Completed** in Files.com then **Add Note to Issue** in GitLab - When **Group Created** in Files.com then **Create Issue** in GitLab ### From GitLab to Files.com - When **New Code Snippet Comment** in GitLab then **Add User to Group** in Files.com - When **New Commit** in GitLab then **Update User** in Files.com 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 Files.com and GitLab ## Triggers and actions 28 triggers · 78 actions - Trigger **Automation Run Completed** Triggered when a run of the selected Files.com automation finishes, whether it succeeded, failed or was canceled. Each run is reported once, after it completes. - Trigger **File Deleted** Triggered when a file or folder is deleted in Files.com. Reports the path that was deleted and who deleted it. - Trigger **Group Created** Triggered when a new group is created in Files.com. Reports the group's name, members and login permissions. - Trigger **New File or Folder Created** Triggered when a file or folder is created in Files.com, whether uploaded, copied or created by an automation. Reports the new path and who created it. - Trigger **New File Uploaded** Triggered when a new file appears in the folder you choose. Reports the file's path, name, size and last-modified time. - Trigger **Share Link Created** Triggered when a new share link is created in Files.com. Reports the link's public address, what it shares and when it expires. - Trigger **User Created** Triggered when a new user is created in Files.com. Reports the user's name, username, email and login permissions. - Action **Add User to Group** Adds an existing Files.com user to a group, optionally as a group administrator. Returns the new group membership, including the group name and the user's username. - Action **Copy File** Copies a file or folder in Files.com to a new path, leaving the original in place. Returns the copy status, plus a migration ID when a large copy continues in the background. - Action **Create Folder** Creates a folder at the given path in Files.com, optionally creating any missing parent folders. Returns the new folder's path, name and creation details. - Action **Create Group** Creates a group in Files.com, optionally with its starting members, group administrators and login-protocol permissions. Returns the new group including its ID. - Action **Create Share Link** Creates a public share link for one or more files or folders in Files.com, optionally password-protected, expiring or use-limited. Returns the link's public address. - Action **Delete File** Deletes a file or folder from Files.com at the given path. Deleting a folder that still has contents requires the recursive option. - Action **Delete Folder** Deletes a folder from Files.com at the given path. Use the recursive option to delete a folder that still has files or subfolders in it. - Action **Delete Group** Deletes a group from Files.com by its ID. The group's members keep their own accounts; only the group is removed. - Action **Delete User** Deletes a user from Files.com by their ID, removing their access to the site. - Action **Download File** Gets a temporary download address for a file in Files.com, along with the file's name, size and checksums. Pass the download address to a later step to fetch or attach the file. - Action **List Folder Contents** Lists the files and folders inside a Files.com folder, with each item's path, name, type, size and last-modified time. - Action **Move File** Moves or renames a file or folder in Files.com to a new path. The original path no longer exists afterwards. - Action **Remove User from Group** Removes a user from a Files.com group. Looks up the membership for the group and user you name, then removes it. - Action **Run Automation** Starts a run of the Files.com automation you choose, the same as pressing Run in Files.com. The run continues in the background. - Action **Update User** Updates a Files.com user's details, login permissions and access settings. Fields you leave blank keep their current values. - Action **Upload File** Uploads a file into Files.com at the path you choose, fetching the bytes from the file's web address. Returns the stored file's path, name and size. - 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. ## Each app on its own - [ **Files.com** Files.com is Smart Cloud Storage for modern teams.](https://apiant.ai/connections/files-com) - [ **GitLab** GitLab is an open source code collaboration tool with a rich feature set including management of...](https://apiant.ai/connections/gitlab) Reviews ## What our customers say ## More from Files.com - [ **Files.com to CVE.report** CVE records with NVD KEV and EPSS enrichment](https://apiant.ai/connect/files-com-to-cve-report) - [ **Files.com to LeadSimple** LeadSimple is the CRM that property management and real estate companies use to scale and grow.](https://apiant.ai/connect/files-com-to-leadsimple) - [ **Files.com to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/files-com-to-hubspot) - [ **Files.com to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/files-com-to-salesforce) - [ **Files.com to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/files-com-to-slack) - [ **Files.com to Google Sheets** Google Sheets](https://apiant.ai/connect/files-com-to-google-sheets) ## More into GitLab - [ **ActiveCampaign to GitLab** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-gitlab) - [ **Airtable to GitLab** Organize anything with Airtable, a modern database created for everyone.](https://apiant.ai/connect/airtable-to-gitlab) - [ **Asana to GitLab** Asana is a collaborative information manager for workspace.](https://apiant.ai/connect/asana-to-gitlab) - [ **ClickUp to GitLab** ClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.](https://apiant.ai/connect/clickup-to-gitlab) - [ **Discord to GitLab** Discord is an all-in-one voice and text chat for gamers.](https://apiant.ai/connect/discord-to-gitlab) - [ **Freshdesk to GitLab** Freshdesk is a cloud-based customer support and helpdesk platform.](https://apiant.ai/connect/freshdesk-to-gitlab) Questions ## Files.com and GitLab, answered ### ### What can start an automation from Files.com? Any of Files.com's 7 triggers in the catalog, including Automation Run Completed, Group Created, New File or Folder Created and New File Uploaded. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in GitLab when something happens in Files.com? Any of GitLab's 62 actions, including Create Branch, Create Commit, Create File and Create Issue. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from GitLab to Files.com? Yes. When something happens in GitLab, your agent can act in Files.com too. This page covers both directions: GitLab's triggers and Files.com's actions are listed here as well. ### ### Do I have to build a connector for Files.com or GitLab? 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 Files.com and GitLab 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.