How to connect GitLab and Vitally
Create a New Scenario to Connect GitLab and Vitally
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 Vitally will be your first step. To do this, click "Choose an app," find GitLab or Vitally, 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 Vitally Node
Next, click the plus (+) icon on the GitLab node, select Vitally from the list of available apps, and choose the action you need from the list of nodes within Vitally.


GitLab
⚙
Vitally

Authenticate Vitally
Now, click the Vitally node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Vitally settings. Authentication allows you to use Vitally through Latenode.
Configure the GitLab and Vitally 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 Vitally 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
⚙
Vitally
Trigger on Webhook
⚙

GitLab
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring GitLab, Vitally, 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 Vitally integration works as expected. Depending on your setup, data should flow between GitLab and Vitally (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 Vitally
GitLab + Slack + Vitally: When a GitLab issue is resolved (new commit), send a notification to a designated Slack channel to inform the customer success team. Simultaneously, update the user in Vitally to reflect improved customer health.
Vitally + GitLab + Jira: When Vitally detects a churn risk based on user activity, create a Jira issue to investigate potential code issues in GitLab. This ensures engineering is aware of customer-impacting bugs.
GitLab and Vitally 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 Vitally
Use Vitally in Latenode to centralize customer success data and automate actions based on health scores. Sync data, trigger alerts for at-risk users, and personalize support workflows, all within Latenode's visual editor. Combine Vitally's insights with other tools for smarter, automated customer lifecycle management.
Similar apps
Related categories
See how Latenode works
FAQ GitLab and Vitally
How can I connect my GitLab account to Vitally using Latenode?
To connect your GitLab account to Vitally 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 Vitally accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I trigger Vitally updates on GitLab code merges?
Yes, you can! With Latenode, automate Vitally updates whenever code merges in GitLab. This keeps your customer data synchronized, ensuring proactive engagement based on development events.
What types of tasks can I perform by integrating GitLab with Vitally?
Integrating GitLab with Vitally allows you to perform various tasks, including:
- Automatically updating Vitally when a GitLab issue is closed.
- Creating new Vitally users from GitLab user accounts.
- Tracking GitLab merge requests related to specific Vitally customers.
- Sending Slack notifications on new Vitally events based on GitLab activity.
- Generating reports combining GitLab project data with Vitally health scores.
How does Latenode handle complex GitLab event triggers?
Latenode provides flexible tools, including JavaScript code blocks, to handle any GitLab event. Process, filter, and transform data with ease.
Are there any limitations to the GitLab and Vitally integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Rate limits imposed by GitLab and Vitally APIs may affect high-volume workflows.
- Complex data transformations may require JavaScript coding within Latenode.
- Initial setup requires understanding of both GitLab and Vitally data structures.