GitLab integration

Quick start

Call GitLab from your generated app's worker code via the OverSkill composio client. The toolkit slug below maps to GitLab's public Composio identifier — your app references it by name and OverSkill handles the OAuth round-trip.

// In your generated app's worker handler:
const composio = composioClient(env);

const result = await composio.execute(
  "GITLAB_ACTION_NAME",
  { /* action parameters — see Actions section below */ }
);

return new Response(JSON.stringify(result), {
  headers: { "Content-Type": "application/json" }
});

Replace ACTION_NAME with one of the slugs listed in the Actions section below. The composio client handles auth + rate limits automatically — no API key is exposed to user code.

Setup

OverSkill hosts the OAuth application for GitLab. End-users click Connect on the integration card in your app, complete the OAuth flow with GitLab, and OverSkill stores the access token scoped to their account. No client_id / client_secret configuration needed on your side.

Supported auth schemes: OAUTH2.

Available actions

58 actions exposed via the GitLab integration. Each maps to a callable slug — pass it to composio.execute(...) in your worker code.

• GITLAB_ARCHIVE_PROJECT
• GITLAB_CREATE_GROUP
• GITLAB_CREATE_PROJECT
• GITLAB_CREATE_PROJECT_ISSUE
• GITLAB_CREATE_REPOSITORY_BRANCH
• GITLAB_DELETE_PROJECT
• GITLAB_DOWNLOAD_PROJECT_AVATAR
• GITLAB_ERASE_JOB
• GITLAB_GET_COMMIT_REFS
• GITLAB_GET_COMMIT_SEQUENCE
• GITLAB_GET_GROUP
• GITLAB_GET_GROUP_MEMBER