Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

GitLab

Collaboration tool for developers

CategoryDeveloper Tools
AuthenticationOAuth 2.0
Version0.2.0
Published scopes2 published scopes
Last updatedSeptember 19, 2026

Overview

Connect GitLab with Flows360

Collaboration tool for developers

Use the GitLab connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 2 actions and 1 trigger.

Available actions

  • Create Issue
  • Custom API Call

Available triggers

  • New Project Issue Event

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: GitLab
  • Package: @activepieces/piece-gitlab@0.2.0
  • Exact artifact digest: sha256:0bca133a56f2ff4294202acfccd964122f47f12976958985e03468ceb71a3d58
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

OAUTH2. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Issue (create_issue), Create a project issue Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Project Issue Event, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

AuthenticationOAuth 2.0
Supported objects3
Supported actions2
Triggers1

Authentication

Authentication method: OAuth 2.0

Required scopes

apiread_user

Authentication profiles

connection · oauth2

OAuth scopes: api, read_user

Supported objects

ObjectReadWriteNotes
Create Issue Yes No Create a project issue
Custom API Call Yes No Make a custom API call to a specific endpoint
New Project Issue Event Yes No webhook trigger declared by the pinned package.

Supported actions

Create Issue · Read

Create a project issue

create_issue · Risk: low · Retry: safe

Inputs

  • projectId · string · Required
  • title · string · Required
  • description · string · Optional
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

New Project Issue Event · Webhook

Triggers on project issue events when an issue is created or when an existing issue is updated, closed, or reopened.

Inputs

  • projectId · string
  • actiontype · string

Setup

Setup

  1. Add the GitLab connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.

OAuth scopes

  • api
  • read_user
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-gitlab@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 2 actions and 1 trigger declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required GitLab connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-gitlab@0.2.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com