GitLab · Arazzo Workflow

GitLab Inspect a Failed CI Job

Version 1.0.0

List failed jobs in a project and fetch full detail for the first one.

1 workflow 1 source API 1 provider
View Spec View on GitHub CodePlatformSoftware DevelopmentSource ControlArazzoWorkflows

Provider

gitlab

Workflows

inspect-failed-jobs
Find the most recent failed job and pull its full details.
Lists failed jobs, picks the first one, and reads the single-job endpoint for its complete record.
2 steps inputs: privateToken, projectId outputs: failedJobName, failedJobStage
1
listFailedJobs
List jobs scoped to the failed status.
2
getJobDetail
Retrieve the full detail for the first failed job.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: GitLab Inspect a Failed CI Job
  summary: List failed jobs in a project and fetch full detail for the first one.
  description: >-
    A CI triage flow. The workflow lists jobs scoped to the failed status,
    captures the first failed job, and retrieves its full detail so a caller can
    review the failure metadata. Every step spells out its request inline so the
    flow can be read and executed without opening the underlying OpenAPI
    description.
  version: 1.0.0
  x-realizes-capability-ids:
  - BC-4200.40
  x-capability-derivation:
    method: 'deterministic join: sourceDescriptions -> per-tag OpenAPI -> tag/capability edge. No classification at this step.'
    min_confidence: 0.7
    sources:
    - capability_id: BC-4200.40
      capability_name: Software Construction Management
      spec: gitlab-projects-api-openapi.yml
      confidence: 0.8
    model: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0
sourceDescriptions:
- name: projectsApi
  url: ../openapi/gitlab-projects-api-openapi.yml
  type: openapi
workflows:
- workflowId: inspect-failed-jobs
  summary: Find the most recent failed job and pull its full details.
  description: >-
    Lists failed jobs, picks the first one, and reads the single-job endpoint for
    its complete record.
  inputs:
    type: object
    required:
    - privateToken
    - projectId
    properties:
      privateToken:
        type: string
        description: GitLab Private-Token used to authenticate the API calls.
      projectId:
        type: integer
        description: The ID of the project.
  steps:
  - stepId: listFailedJobs
    description: List jobs scoped to the failed status.
    operationId: listProjectJobs
    parameters:
    - name: Private-Token
      in: header
      value: $inputs.privateToken
    - name: id
      in: path
      value: $inputs.projectId
    - name: scope
      in: query
      value:
      - failed
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      failedJobId: $response.body#/0/id
    onSuccess:
    - name: hasFailure
      type: goto
      stepId: getJobDetail
      criteria:
      - context: $response.body
        condition: $.length > 0
        type: jsonpath
    - name: noFailures
      type: end
      criteria:
      - context: $response.body
        condition: $.length == 0
        type: jsonpath
  - stepId: getJobDetail
    description: Retrieve the full detail for the first failed job.
    operationId: getSingleJob
    parameters:
    - name: Private-Token
      in: header
      value: $inputs.privateToken
    - name: id
      in: path
      value: $inputs.projectId
    - name: job_id
      in: path
      value: $steps.listFailedJobs.outputs.failedJobId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      jobName: $response.body#/name
      jobStatus: $response.body#/status
      jobStage: $response.body#/stage
      startedAt: $response.body#/started_at
  outputs:
    failedJobName: $steps.getJobDetail.outputs.jobName
    failedJobStage: $steps.getJobDetail.outputs.jobStage

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/gitlab-inspect-failed-jobs-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.