> For the complete documentation index, see llms.txt.
Skip to main content

Check out Port for yourself ➜ 

GitLab pipeline

The GitLab backend allows you to trigger GitLab pipelines for your self-service actions and automations.

Choose how to trigger your pipeline​

For self-service actions and automations, use a direct webhook to trigger your GitLab pipeline when Port can reach your GitLab API. This applies to both GitLab SaaS and self-hosted GitLab. Self-hosting GitLab does not, by itself, require the Port execution agent or Kafka.

Your setupRecommended execution methodSetup instructions
GitLab SaaS, or self-hosted GitLab with an API endpoint reachable from Port.Use the webhook backend with Use self-hosted agent set to No (agent: false).Configure a direct pipeline webhook.
Self-hosted GitLab with an API endpoint that Port cannot reach directly.Run the Port execution agent inside your network to forward pipeline requests.Configure an agent for private GitLab.

Kafka is the agent's default event transport, not a prerequisite for triggering GitLab pipelines. If you need an agent but cannot connect to Kafka, use its HTTP polling option with a webhook backend.

If you already use the GitLab Ocean integration in a Port workflow, you can also trigger pipelines through GitLab integration actions. That path uses the integration's actions processor; it does not require a separate Port execution agent. Follow that page's prerequisites for your integration deployment.