How to connect GitLab and Kommo
Create a New Scenario to Connect GitLab and Kommo
In the workspace, click the “Create New Scenario” button.

Add the First Step
Add the first node – a trigger that will initiate the scenario when it receives the required event. Triggers can be scheduled, called by a GitLab, triggered by another scenario, or executed manually (for testing purposes). In most cases, GitLab or Kommo will be your first step. To do this, click "Choose an app," find GitLab or Kommo, and select the appropriate trigger to start the scenario.

Add the GitLab Node
Select the GitLab node from the app selection panel on the right.


GitLab

Add the Kommo Node
Next, click the plus (+) icon on the GitLab node, select Kommo from the list of available apps, and choose the action you need from the list of nodes within Kommo.


GitLab
⚙
Kommo

Authenticate Kommo
Now, click the Kommo node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Kommo settings. Authentication allows you to use Kommo through Latenode.
Configure the GitLab and Kommo Nodes
Next, configure the nodes by filling in the required parameters according to your logic. Fields marked with a red asterisk (*) are mandatory.
Set Up the GitLab and Kommo Integration
Use various Latenode nodes to transform data and enhance your integration:
- Branching: Create multiple branches within the scenario to handle complex logic.
- Merging: Combine different node branches into one, passing data through it.
- Plug n Play Nodes: Use nodes that don’t require account credentials.
- Ask AI: Use the GPT-powered option to add AI capabilities to any node.
- Wait: Set waiting times, either for intervals or until specific dates.
- Sub-scenarios (Nodules): Create sub-scenarios that are encapsulated in a single node.
- Iteration: Process arrays of data when needed.
- Code: Write custom code or ask our AI assistant to do it for you.

JavaScript
⚙
AI Anthropic Claude 3
⚙
Kommo
Trigger on Webhook
⚙

GitLab
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring GitLab, Kommo, and any additional nodes, don’t forget to save the scenario and click "Deploy." Activating the scenario ensures it will run automatically whenever the trigger node receives input or a condition is met. By default, all newly created scenarios are deactivated.
Test the Scenario
Run the scenario by clicking “Run once” and triggering an event to check if the GitLab and Kommo integration works as expected. Depending on your setup, data should flow between GitLab and Kommo (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect GitLab and Kommo
GitLab + Kommo + Slack: When a GitLab issue is closed (or updated), the corresponding Kommo deal stage is updated to reflect the change, and a message is sent to a Slack channel to notify the team.
Kommo + GitLab + Jira: When a new lead reaches a specific stage in Kommo, a new issue is created in both GitLab and Jira to track the development tasks associated with that lead.
GitLab and Kommo integration alternatives

About GitLab
Use GitLab in Latenode to automate CI/CD pipelines and track code changes. Trigger workflows on commit, issue, or merge requests to update project management tools, send notifications, or provision environments. Simplify development workflows with flexible, low-code automation and scale easily via Latenode.
Similar apps
Related categories
About Kommo
Integrate Kommo with Latenode to automate sales processes. Trigger actions in other apps when deals change status, or create Kommo leads from form submissions. Build custom workflows with no-code tools or JavaScript, scaling your sales automation without complex coding. Use Latenode's visual editor to connect Kommo to your entire tech stack.
Similar apps
Related categories
See how Latenode works
FAQ GitLab and Kommo
How can I connect my GitLab account to Kommo using Latenode?
To connect your GitLab account to Kommo on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select GitLab and click on "Connect".
- Authenticate your GitLab and Kommo accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I create Kommo tasks from new GitLab issues?
Yes, you can! Latenode's visual editor allows seamless automation. Instantly create tasks ensuring sales teams act on important development updates, improving response time.
What types of tasks can I perform by integrating GitLab with Kommo?
Integrating GitLab with Kommo allows you to perform various tasks, including:
- Automatically creating Kommo tasks from new GitLab issues.
- Updating Kommo lead stages when GitLab merge requests are approved.
- Sending Kommo notifications for critical GitLab pipeline failures.
- Adding GitLab issue links to Kommo contact notes for context.
- Creating GitLab issues from new Kommo deal stages.
How do I handle errors during GitLab and Kommo workflows?
Latenode provides robust error handling. Configure retry logic or send error alerts, ensuring reliable automation and data integrity between GitLab and Kommo.
Are there any limitations to the GitLab and Kommo integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Rate limits of GitLab and Kommo APIs may affect high-volume workflows.
- Complex data transformations may require JavaScript knowledge.
- Custom fields in GitLab or Kommo might need manual mapping.