Integrate GitLab with Way We Do to automate workflows, sync data between apps, and eliminate repetitive tasks with AI-powered automation.
Add a New User to Way We Do when New Commit in GitLab
Complete a Checklist Step in Way We Do when New Commit in GitLab
Add a Checklist Comment to Way We Do when New Commit in GitLab
Start Checklist Instance in Way We Do when New Commit in GitLab
Find a Checklist by Title in Way-we-do when New Commit in GitLab
Start from a real workflow other teams are already running.
GitLab
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
Way We Do
Automatically do this!
Add a New User
Complete a Checklist Step
Add a Checklist Comment
Start Checklist Instance
Find a Checklist by Title
Find a Checklist Instance by ID
Find a Checklist Instance by Title
Find a Checklist Step by ID
Find a Procedure by Title
Find a Procedure or Checklist by ID
Find a User
Find a Checklist Step by Title
Add Collaborators
List Checklist Instance Comments
List Checklist Instances
List Collaborator Invites
Get Company
List All Company Roles
List Completed Checklist Steps
List Procedure Acceptance
List All Procedures
List All Security Roles
List All Time Zones
List All Users
Add a New User to Way We Do when New Commit in GitLab
Use this flowComplete a Checklist Step in Way We Do when New Commit in GitLab
Use this flowAdd a Checklist Comment to Way We Do when New Commit in GitLab
Use this flowStart Checklist Instance in Way We Do when New Commit in GitLab
Use this flowFind a Checklist by Title in Way-we-do when New Commit in GitLab
Use this flowFind a Checklist Instance by ID in Way We Do when New Commit in GitLab
Use this flowFind a Checklist Instance by Title in Way We Do when New Commit in GitLab
Use this flowFind a Checklist Step by ID in Way-we-do when New Commit in GitLab
Use this flowFind a Procedure by Title in Way-we-do when New Commit in GitLab
Use this flowFind a Procedure or Checklist by ID in Way We Do when New Commit in GitLab
Use this flowEverything you can automate between GitLab and Way We Do.
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

Follow a simple walkthrough to create, test, and launch your first automation.
Connect your apps
Link the apps you want to automate.
Configure your workflow
Set up triggers, actions, and map your data.
Test & publish
Test your workflow and publish it.
Recognized by leading review platforms and trusted by 10,000+ businesses worldwide.
Just describe the task in plain English. viaSocket AI selects the right apps, builds the workflow, maps the fields, and prepares everything for review before you publish.

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.

Five practical automation hacks to cut repetitive tasks and boost productivity using viaSocket, covering lead generation, onboarding, accounting, support, and HR.

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.
viaSocket Support
We're here to help
Instant answers
AI assistant available 24/7
Expert support
Connect with our specialists
Trusted & secure
Your data is safe with us
No credit card required. Set up your first workflow in minutes.
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 moreWay We Do is a cloud-based platform that helps businesses create, manage, and execute their standard operating procedures (SOPs) and policies. It enables organizations to streamline their processes, ensure compliance, and improve operational efficiency by providing a centralized location for all procedural documentation.
Learn moreSign up for a free viaSocket account, then authorize both your GitLab and Way We Do accounts. From there, pick a trigger in one app and an action in the other. Your first workflow can be live in under five minutes.
Yes. viaSocket uses instant triggers where available, so data moves between GitLab and Way We Do as soon as the event happens. Scheduled polling triggers run at a maximum interval of 15 minutes.
Yes. You can map specific fields, apply filters to skip records that do not match your conditions, and transform values before they reach Way We Do. No coding required.
Yes. You can set up a workflow where GitLab triggers actions in Way We Do, and a separate workflow where Way We Do triggers actions in GitLab. Both run independently and in real time.
viaSocket logs every run so you can see exactly what succeeded and what failed. Failed tasks can be retried from the dashboard without re-configuring the workflow.
Yes, there is a free plan that covers basic workflows between GitLab and Way We Do. Paid plans unlock higher task limits, faster polling, and advanced features like multi-step workflows and conditional logic.
No. The entire GitLab and Way We Do integration is built through a visual, point-and-click interface. Code blocks are available if you want them, but they are never required.