How to Integrate GitLab with Workstatus?

Overview

This document explains how to integrate GitLab with Workstatus, connect GitLab projects, and understand the synchronization behavior between both platforms.

Prerequisites

Before starting the integration process, make sure you have:

• A valid GitLab account
• Access to the GitLab project
• GitLab Personal Access Token (PAT)
• Access to the Workstatus account with project management permissions

Step 1: Generate GitLab Personal Access Token

• How to Generate Token in GitLab
• Login to your GitLab account.
• Click on your profile icon → Edit Profile → Access → Personal Access Token
• Enter the following details:
• Token Name
• Expiry Date (optional)
• Required Scopes: enable all Permission
• Click on Create Personal Access Token.
• Copy the generated token and save it securely.

Note: The token will be shown only once after creation.

Step 2: Integrate GitLab with Workstatus

• Integration Steps
• Login to Workstatus.
• Navigate to: Settings → Integrations → GitLab
• Enter the following details:
• GitLab Personal Access Token
• GitLab Domain URL (By default, the GitLab URL is already configured in Workstatus.)
• Click on the Next button.
• Once verified successfully, GitLab will be integrated with Workstatus.

Step 3: Connect GitLab Project with Workstatus Project

After successful integration:

• Click on Connect Project.
• Select the GitLab project that you want to connect.
• Choose one of the following options:
• Map with an existing Workstatus project
• Create a new Workstatus project
• Click on Sync button for Complete the project mapping process.

Step 4: Map GitLab Users with Workstatus Users

User Mapping Steps

• Navigate to the User Mapping section.
• Select the GitLab user from the GitLab users list.
• Select the corresponding Workstatus user.
• Click on the Sync button.

User Assignment Synchronization

• Once the user mapping is completed:
• All tasks assigned to the GitLab user will automatically be assigned to the mapped Workstatus user.
• User assignment synchronization works automatically during task sync.
• Sync Direction : GitLab → Workstatus
• Any task assignment changes made in GitLab will automatically reflect in Workstatus.

Step 5: Task Synchronization and CRUD Operations

Once the GitLab project is successfully connected with the Workstatus project:

All tasks from the GitLab project will automatically reflect in the mapped Workstatus project.

Task details, status, assignee, due date, priority, tags and estimated hours will sync from GitLab to Workstatus.

CRUD Operations on Tasks

Users can perform task operations such as:

• Create Task
• Update Task
• Delete Task
• View Task

When performing these operations, the user will be redirected to GitLab because task management is handled directly from GitLab.

After changes are made in GitLab, the updates will automatically sync to Workstatus.

Step 6 : Project Disconnect Behavior

If the GitLab project is disconnected from Workstatus:

• New tasks and updates from GitLab will no longer sync to Workstatus.
• Existing synced tasks will remain available in Workstatus.
• Users will only be able to mark existing tasks as completed in Workstatus.
• Any further CRUD operations will not sync after disconnection.
• You cannot edit or update task.
• You cannot delete task.
• You can only mark them as complete.

Updated on: 12/05/2026