ConnectCloud Developers

Get a published version with its definition (tenant:flows:read|write|admin; scoped flows the owning module's view)

GET /api/flows/v1/flows/{id}/versions/{number}

Module: Flows · operationId: getFlowVersion · Tag: Flows · Auth: access token (Authorization: Bearer <accessToken>)

Parameters

Name In Type Required Description
id path string (uuid) yes
number path integer yes

Responses

  • 200 The version (application/json)
  • 400 Invalid input (invalid); field names the first invalid field, details.fields every one. (application/json)
  • 401 Missing, invalid or expired token (no body).
  • 403 The token lacks the permission or has no active tenant (forbidden). Also: person_required (a service-account key on personal flows or the task inbox), live_test_forbidden, forbidden_grant, starter_excluded. (application/json)
  • 404 The record does not exist in the token's tenant – or it belongs to a scope the caller may not view (a scoped flow stays hidden). (application/json)
  • 503 A dependency is not available: scope_unavailable (the module that owns a flow's scope did not answer who may see and manage it – nothing of a scoped flow is shown or changed), identity_unavailable (HR), ai_unavailable, ai_failed. (application/json)

Fields of the 200 answer:

  • createdAt (string (date-time)): When it was published
  • createdBy (string): E-mail of who published it
  • note (string): Note given at publish
  • number (integer): Version number, counting from 1
  • permissions (array of string): What the runs of this version act with
  • webhooks (array of WebhookCredential): Only in the answer of the publish that created them
    • path (string, required): The address on the portal origin: /api/flows/v1/hooks/{token}
    • token (string, required): The webhook token (the credential in the path)
    • trigger (string, required): The trigger's id
    • secret (string): auth hmac: signs the body, header X-Flows-Signature: sha256=<hex of HMAC-SHA256(secret, body)>
  • yaml (string): Only when one version is read

Example 200 answer:

{
  "createdAt": "2026-11-12T14:03:27Z",
  "createdBy": "sophie.huber@muster-it.example",
  "note": "Empfänger auf die Systemadministration umgestellt",
  "number": 2,
  "permissions": [
    "desk:read"
  ],
  "yaml": "schemaVersion: 1\nkey: kritische-tickets-zusammenfassen\nname: Kritische Tickets zusammenfassen\ntriggers:\n  - { id: neues_ticket, kind: event, event: desk.item.created, filter: \"trigger.data.priority in ['hoch', 'kritisch']\" }\nnodes:\n  ticket:\n    kind: action\n    name: Ticket lesen\n    action: desk.item.get\n    params: { ref: \"{{ trigger.data.itemId }}\" }\n  info:\n    kind: mail\n    name: Systemadministration informieren\n    to: [\"person:jonas.bauer@muster-it.example\"]\n    subject: \"Kritisches Ticket {{ trigger.data.number }}\"\n    text: \"{{ nodes.ticket.output.title }}\"\nedges:\n  - neues_ticket -\u003e ticket\n  - ticket -\u003e info\n"
}

Example request

curl -X GET 'https://api.mbcom.cloud/api/flows/v1/flows/3f2b8c1e-7d4a-4e9b-9c2a-5b1d6e8f0a12/versions/1' \
  -H "Authorization: Bearer $ACCESS_TOKEN"

View as Markdown · Interactive reference · OpenAPI