Appbricx
Features

Build

  • Coding agents and MCP
  • UI components and hooks
  • Templates
  • Verify testing
  • Builder console

Data

  • Postgres database
  • Data API
  • Realtime

Users

  • Row-level security
  • Sign-in and auth
  • Organisations and teams
  • Payments

Logic

  • Workflows and jobs
  • Server functions and webhooks
  • AI in your app
  • Integrations

Ship and own

  • Backups and rollback
  • Hosting and domains
  • Self-host and export
All features
ShowcaseTemplatesIntegrationsPricingDocs
Log inStart free
  • Features
  • Showcase
  • Templates
  • Integrations
  • Pricing
  • Docs
  • Log in

Build

  • Coding agents and MCP
  • UI components and hooks
  • Templates
  • Verify testing
  • Builder console

Data

  • Postgres database
  • Data API
  • Realtime

Users

  • Row-level security
  • Sign-in and auth
  • Organisations and teams
  • Payments

Logic

  • Workflows and jobs
  • Server functions and webhooks
  • AI in your app
  • Integrations

Ship and own

  • Backups and rollback
  • Hosting and domains
  • Self-host and export
  1. Home
  2. Integrations
  3. Developer tools
  4. GitLab

GitLab

Create issues, list projects, and open merge requests on GitLab. In Appbricx, your workflows and server functions call it by name once it is connected.

Connect GitLabFull reference

What you can do

2 actions, each one call from a workflow or a server function. Triggers come from your app: a row changing, a schedule or a webhook.

  • Create Issuecreate_issue
    Create a project issue
  • Custom API Callcustom_api_call
    Make a custom API call to a specific endpoint

Set it up

About two minutes, once per project or once for the whole workspace.

  1. Open Integrations in the builder

    Backend panel, Integrations tab, then GitLab. To connect it for every project, use Workspace settings, Integrations.

  2. Sign in to GitLab

    You sign in to GitLab and approve access. Appbricx keeps the tokens, encrypted, and refreshes them.

    • api

    This uses an OAuth app: the platform's, or your own from the admin panel, and you can bring your own credentials.

  3. Call an action

    From a workflow, by integration id and action name. The call answers with success, output and, when it fails, the reason.

    Workflow
    // .workflow.js (native ctx)
    export async function run(ctx) {
      const res = await ctx.integrations.invoke("gitlab", "create_issue", {
        "projectId": "<projectId>",
        "title": "<issue title>"
      });
      if (!res.success) throw new Error(res.error);
      ctx.log.info("GitLab answered", { output: res.output });
    }

More in Developer tools

  • GitHub
  • Bitly
  • { }Custom API
  • Datadog
  • DigitalOcean
  • Figma
  • All of Developer tools
Category
Developer tools
Sign-in
OAuth
Actions
2
Integration id
gitlab
Maintained
With the platform
Package
@activepieces/piece-gitlab@0.1.4
Docs
Actions, inputs and examples

GitLab and its logo are trademarks of their owner, shown only to identify the service this integration connects to. Their use does not imply endorsement by, or affiliation with, that company.

Connect GitLab once. Every workflow can use it.

Start freeAll integrations
Appbricx

The backend, runtime and hosting for apps your coding agent builds. On our cloud, in yours, or on your own servers.

Features

Coding agents and MCPUI components and hooksTemplatesVerify testingBuilder consolePostgres databaseData APIRealtimeRow-level securitySign-in and authOrganisations and teamsPaymentsWorkflows and jobsServer functions and webhooksAI in your appIntegrationsBackups and rollbackHosting and domainsSelf-host and exportAll features

Product

ShowcaseTemplatesIntegrationsPricingFor coding agentsSelf-hostBring your own AI keyFAQ

Compare

Appbricx vs SupabaseLovable alternativeBolt alternativeFor freelancersFor agencies

Resources

DocumentationReferenceBlogSupportContact

© 2026 Appbricx. All rights reserved.

TermsPrivacyCookiesAcceptable Use