airbox.fyi

GitLab

Read and write files in a GitLab project — ideal for Obsidian vaults synced via Git

No coding required. If you have never used an API key before, follow the walkthrough below step by step. Developers can skip to Quick reference at the bottom

Connect in Airbox

  1. Dashboard → Connections → + GitLab
  2. OAuth (if configured) or paste a PAT with api scope
  3. Optionally set default_repo and repos aliases in connection config
  4. For self-managed GitLab, set api_url (e.g. https://gitlab.example.com)
  5. Optionally set default_branch (defaults to main)
  6. Attach GitLab to your inbox routing (tool list)
  7. Keep an LLM provider as the inbox default — GitLab supplies file tools

Open the dashboard in a new tab if you want to follow along

Route your inbox

Your Airbox address does not use a connection until you attach one:

  1. Select an LLM provider as inbox default
  2. Enable GitLab under attached tools
  3. Save

Try it — send an email

Subject: (* @gitlab -repo=book #update (* "append to Chapter 3" *) *)

—or plain quotes—

Subject: @gitlab -repo=book #update "append to Chapter 3"

New to commands? See copy-paste examples and the syntax cheat sheet

Quick reference

Dashboard typegitlab
Email targets@gitlab, @gitlab/book/Projects/Chapter-3
Default model—
Keyshttps://gitlab.com/-/user_settings/personal_access_tokens

Short checklist

  • + GitLab OAuth or PAT
  • Set default_repo / repos aliases
  • Attach to inbox

What you get

  • search, read, write, append
  • GitLab.com or self-managed
  • Obsidian vault via Git

Notes

  • Project paths use group/name (same as GitLab URLs)
  • Self-hosted: set api_url on the connection to your instance base URL
  • See GitLab REST API docs: https://docs.gitlab.com/api/

Related