01AI and integrations · module
GitLab and development tasks
Links GitLab commits and merge requests to tasks and moves tasks to review
- Git server
- Repository
- Commit
- Merge request
- Task
- Project
- User
- 11
- capabilities
- 7
- record types
- 4
- automations
- 3
- integrations and AI tools
02What the module does
Less routine. More value.
The GitLab integration connects your self-hosted GitLab with tasks in Draivix. Commits and merge requests are automatically linked to tasks, and opening a merge request moves the task to review. Management can see actual development work right on the task without having to look it up in GitLab.
- Repositories linked to projectsRegister GitLab servers in Draivix, import repositories and assign them to projects so development work stays organized under the right project.
- Events verified by secret tokenGitLab sends push and merge request events to Draivix via webhook—an automated notification. Any request without a valid secret token is rejected.
- Commits automatically find their taskEach commit—a saved code change—is linked to a task by the ID in its message, the branch map or smart matching. Matches below the 0.8 threshold are not linked.
- See who worked on whatCommits are also linked to users, so management can see which person worked on a given development task without looking it up in GitLab.
- Merge requests right on the taskMerge requests—requests to merge code changes—are visible directly on tasks and repositories, letting you check development progress without switching to GitLab.
- Tasks move to review automaticallyWhen a merge request is opened, the task moves to review automatically, keeping task status aligned with development without manual updates.
- Missed commits are backfilledEvery night, the system fetches commits from the last three days to backfill any missed webhooks and keep the work overview on tasks complete.
- Development on a single dashboardA dashboard widget displays developer activity, giving management an overview of what is happening in development without opening another system.
- GitLab accounts managed from DraivixDraivix can create and deactivate GitLab accounts for your team. Members of selected teams are pre-filled in the form, saving the administrator manual data entry.
- New accounts with the right permissionsEach new account is added to the configured group with the configured access level—Developer by default—so team permissions follow a consistent standard.
- Encrypted credentialsServer tokens and secrets are stored encrypted, so GitLab credentials are never kept in plain text in Draivix.
What is currently in progress
- Moving a task on the first commit is declared in configuration but not yet implemented.
- Mapping task statuses to GitLab events cannot yet be customized by the company; automatic completion upon merge is disabled.
- Pipeline events are logged only and do not affect tasks.
03How it works
How it works step by step.
How the integration works
In Draivix, you register your GitLab server and its repositories, which can be imported and assigned to projects. GitLab sends events to Draivix via webhook. Every request must carry the server's secret token; requests with a missing or invalid token are rejected. The endpoint is rate-limited to 60 requests per minute, and events are processed in the background.
Read in detail
Push and merge request events are processed. Pipeline events are received and logged only. Server secrets are stored encrypted.
Linking commits to tasks
A commit is matched to a task first by the task ID in the commit message, then by the branch map, and finally by smart matching with a similarity threshold of 0.8. Commits below this threshold are not linked. Commits are also linked to users.
Read in detail
Each task displays its list of commits and merge requests, and a dashboard widget shows developer activity. Every night at 2:25, the system fetches commits from the last three days to backfill any missed webhooks.
Task status driven by merge requests
When a merge request is opened, the task moves to review. The task is identified by the TASK-n tag in the branch name, title or description of the merge request. The status change triggers a standard event, so a workflow in the Automation module can react to it—for example, by notifying the reviewer.
Read in detail
Moving a task to completed when a merge request is merged is disabled by default so tasks awaiting acceptance are not closed prematurely.
GitLab accounts
Draivix can create and deactivate GitLab accounts for your people. Members of selected teams are pre-filled in the form. Each new account is added to the configured group with the configured access level (Developer by default).
04What runs automatically
Automations that save time.
Commits are linked automatically
When a GitLab webhook arrives, the event is processed in the background and commits are linked to tasks without developers having to log anything manually.
Opening a merge request starts review
As soon as a merge request is opened, the task moves to review. The task is identified by the TASK-n tag in the branch name, title or description of the merge request.
Nightly commit sync
The nightly SyncGitCommits job at 2:25 backfills commits from the last three days, keeping the work overview on tasks accurate even if a webhook fails to deliver.
Status changes trigger next steps
When a task's status changes, a standard event is fired. A workflow in the Automation module can respond to it—for example, by notifying the reviewer.
External integrations
- Connected to your GitLabDraivix communicates with your self-hosted GitLab via the GitLab REST API—for instance, when importing repositories and provisioning accounts for your team.
- GitLab reports events automaticallyGitLab sends push, merge request and pipeline webhooks. Push and merge request events are processed; pipeline events are logged only and do not affect tasks.
What the AI agent handles
Agent work visible right on the task
Agents connected via newerp-agents-mcp link their work to tasks and commits using 12 dedicated tools, so you see both agent and human work on each task.
A person approves whenever money, a customer, or an exception is involved.
05Frequently asked questions
How does Draivix know which task a commit belongs to?
By the task ID in the commit message, by the branch map, or by smart matching with a 0.8 similarity threshold. Commits below the threshold are not linked.
Does GitLab update the task status?
Yes. Opening a merge request moves the task to review. Completing the task when merged is disabled by default.
Is the GitLab webhook secure?
Yes. Every request must include the server's secret token or the system rejects it, and the endpoint is protected by a rate limit of 60 requests per minute.
Does the integration work with self-hosted GitLab?
Yes. The integration is designed for a self-hosted GitLab instance that you register as a server in Draivix.
- Project managementProjects from quote to invoice: plans, Gantt charts, costs, milestones and handover
- Companies, contacts and activitiesA single directory of companies and contacts, tasks, meetings, calls and AI meeting notes
- Automation and workflowsNo-code “when X happens, do Y” rules and scheduled recurring records
- MCP for external AI agentsConnect Claude Code, Codex and other agents to your ERP under specific user permissions
- Dashboards and overviewsWidget-based home screen: counters, charts, lists, kanban boards, calendars and reports
- AI assistant in DraivixAn in-app assistant that finds data, drafts changes and saves them once you confirm
Let’s start together
Tell us how your business works.
We will show you what a system that takes over part of that work could look like.
Book a consultation