
When this happens...
New Commit
Merge Request Review Request
New Job Event
New Issue Comment
New Project Merge Request Event
New Project Issue Event
New Merge Request Comment
New Commit Comment
New Code Snippet Comment
New Group Issue Event
New Group Merge Request Event

Automatically do this!
Restore a Doc
Create a Card
Archive an Invoice
Restore a Board
Archive an Embed
Archive a Conversation
Create a Comment
Restore a Milestone
Restore a Folder
Create a Doc
Create a Template
Update an Embed
Update a Client
Update a Conversation
Update a Board
Update a Note
Update a Message
Update a Template
Archive a Folder
Archive a Doc
Restore an Invoice
Create a Client
Create a Conversation
Create a Board
Archive a Board
Restore an Embed
Archive a Milestone
Create a Folder
Create a List
Create a Milestone
Update a Card
Toggle Card Completion
Update a Doc
Create an Embed
Update a Folder
Update a Comment
Update a Milestone
Update a List
Add Membership to Milestone
Updates an Embed Membership
Update a Folder Membership
Update a Board List
Update a Board Label
When this happensTriggers
A trigger is an event that starts a workflow.
Triggers when a commit is made on a specified project.
Triggers when you are requested to review a merge request.
Trigger for a specified job event in a project.
Triggers when a new comment is made on an issue in the selected project.
Triggers on an open, merge, or close merge request event.
Triggers on project issue event. e.g. when an issue is opened, closed or updated.
Action is the task that follows automatically within your GitLab integrations.
Find merge request for a project.
Finds all Merge Requests that the authenticated user has access to.
Creates a new commit. Supports creating or updating a file.
Creates a new merge request.
Create a new branch in project
Add note to MR or thread

Discover viaSocket, an AI-powered workflow automation platform with 2,000+ integrations. Learn what it is, how it works, and how to set up no-code automated workflows.

Unlock your team's potential with 5 straightforward automation hacks designed to streamline processes and free up valuable time for more important work.

Explore workflow automation: its definition, benefits, how it works, real-world examples, and how to automate with viaSocket.

Discover what webhooks are, how they work, and when to use them. Compare push-based webhooks with APIs and polling, with practical examples and ViaSocket integration.
To start, connect both your GitLab and Kitchen.co accounts to viaSocket. Once connected, you can set up a workflow where an event in GitLab triggers actions in Kitchen.co (or vice versa).
Absolutely. You can customize how GitLab data is recorded in Kitchen.co. This includes choosing which data fields go into which fields of Kitchen.co, setting up custom formats, and filtering out unwanted information.
The data sync between GitLab and Kitchen.co typically happens in real-time through instant triggers. And a maximum of 15 minutes in case of a scheduled trigger.
Yes, viaSocket allows you to add custom logic or use built-in filters to modify data according to your needs.
Yes, you can set conditional logic to control the flow of data between GitLab and Kitchen.co. For instance, you can specify that data should only be sent if certain conditions are met, or you can create if/else statements to manage different outcomes.
GitLab is a comprehensive DevOps platform that provides source code management, CI/CD pipelines, and project management tools, enabling teams to collaborate efficiently on software development projects.
Learn MoreKitchen.co is a platform designed to streamline and enhance the culinary experience, offering tools and resources for both professional chefs and home cooks. It provides a range of features including recipe management, meal planning, and kitchen inventory tracking, making it an essential tool for anyone passionate about cooking.
Learn More