Trigger and monitor a GitLab CI pipeline via API

domain: gitlab.com · 4 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Create a pipeline trigger token (project settings) or use a PAT
  2. POST /projects/{id}/pipeline with ref and variables, or /trigger/pipeline with the trigger token
  3. Poll GET /projects/{id}/pipelines/{pipeline_id} for status
  4. Fetch failed job logs: GET /projects/{id}/jobs/{job_id}/trace

Known gotchas

Related routes

Trigger a GitLab pipeline via pipeline trigger token API
docs.gitlab.com · 5 steps · unrated
Trigger a downstream multi-project GitLab CI pipeline and block on its result using strategy depend
docs.gitlab.com · 5 steps · unrated
Trigger a Coolify deployment from a CI pipeline via its deploy webhook
coolify.io · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans