Connect GitLab to Notion

Workers run your sync on Notion’s infrastructure. To set up your replacement, @-mention your existing synced database in a chat with Notion AI and include the GitLab sync skill.

Have these ready:

• Your existing GitLab synced database in Notion. Make sure Notion AI can access it.

• The complete list of GitLab projects to include. You can provide project URLs, numeric IDs, or paths such as my-team/my-project. Learn how to view projects in GitLab →

• A GitLab personal or project access token with read_api and access to every selected project.

• Access to Workers and the tools Notion AI needs to create and deploy a Worker in your workspace.

• This skill page, which you’ll copy into your Notion account: GitLab Guide: Worker Sync. This skill is for GitLab.com. If you use a self-managed GitLab instance, tell Notion AI before setup. The guide’s API address and credential configuration need adaptation and validation for your instance.

Open a chat with Notion AI in the workspace that contains your existing synced database.

Copy the prompt below. Replace @Existing GitLab sync database by typing @ and selecting the actual database from the mention menu. If issues and merge requests are in separate synced databases, mention both.

Select an actual database mention in the prompt. Typing the database’s name alone doesn’t give Notion AI a link to inspect.

Confirm the complete project list, including projects hidden by your current Notion view’s filters. A token limited to one project won’t be enough for a sync that also needs access to other projects.

Follow Notion AI’s instructions to provide your GitLab token through the secure credential input. It needs read_api and access to the selected projects.

Don’t paste the token into the chat, a Notion page, or a database property. The Worker uses a brokered credential so its code doesn’t need to read the raw token.

This setup uses a new Worker credential. Your existing GitLab connection doesn’t automatically supply it.

If Notion AI can’t access the skill or the Worker tools, resolve that access first. The linked guide also contains setup instructions for someone on your team who can use the Notion CLI.

The skill creates a private GitLab Sync page containing five synced databases and a dashboard:

GitLab Dashboard brings these records together in charts and working queues. It includes open issues, open merge requests, failed pipelines, recent releases, and project activity.

The five synced databases contain the records. The dashboard displays views of those records. Your old issue or merge request database may have covered fewer data types than this skill’s default setup.

Check these differences before switching:

• People and labels: Authors, assignees, and labels are stored as text in this guide. They aren’t Notion person or multi-select properties.

• Project relations: Issues, merge requests, pipelines, and releases should link to their selected project records.

• Record identity: Records from different projects must remain distinct even when they use the same project-local issue or merge request number.

• Additional content: The guide doesn’t sync issue comments, merge request discussions, repository files, or job logs. Ask Notion AI to assess any extra fields your existing workflow needs.

Wait until Notion AI confirms that all five syncs are healthy and that the initial import is complete.

1. Compare each selected project with GitLab. Check a sample of open and closed issues, merged requests, pipelines, and releases.

2. Confirm that project relations and dashboard views show the expected records.

3. Check that a recent GitLab change reaches the replacement after a successful refresh.

4. Review the old database’s custom properties and Notion-only values with Notion AI. Transfer what you need using stable GitLab record IDs.

5. Update links, linked database views, relations, and automations that should use the replacement. Review the new page’s sharing permissions.

6. Once your team is using the replacement, ask Notion AI to help retire the old sync while keeping the old database available for reference.

You don’t need to delete the old database to use the Worker. Keep it until you’ve checked that your team’s information and workflows are accounted for.

The skill sets up five hourly syncs, one for each data type. Projects sync first during setup so the other databases can relate their records to the right projects.

Each successful refresh reads all pages of results for the configured projects and updates the matching Notion database. The Worker continues running when Notion is closed.

Updates flow from GitLab to Notion. Make changes to synced values in GitLab; changes in Notion aren’t written back.

Hourly is the schedule, not a guarantee that every refresh finishes within a fixed time. Large project histories and GitLab request limits can delay completion.

The skill starts with a private GitLab Sync page. Share it only with the people who should see the imported records.

Notion’s permissions control access to the synced data. A GitLab project’s Visibility property or an issue’s Confidential property doesn’t enforce that source permission in Notion. Review the data included by the token before sharing the page.

Confirm the complete project list and token access. Give Notion AI the project’s URL or numeric ID if its path has changed. Don’t run a refresh with a shortened list just to work around an access error.

Ask Notion AI to check the project selection, whether it’s checking issues and merging requests in every state, and every page of results. Check the Notion view’s filters as well.

Ask Notion AI to check the source databases, their latest sync results, and project relations before rebuilding the dashboard. A dashboard can be empty while the initial import is still running.

Ask Notion AI to inspect the existing Worker, database URLs, and page structure before creating anything else. The skill calls for five actual synced databases and one dashboard under GitLab Sync. Have Notion AI identify any duplicates before removing them.

Ask Notion AI to check the Worker’s latest runs, token expiry, token permissions, and access to every selected project. For a self-managed instance, also check the configured GitLab host. Request limits can delay updates.

• Sync data from other tools to Notion

• Connect Asana