FruxonDocs
ApiWorkflows

Creates a Workflow canonically owned by the Application in the route.

The Application in the route wins — any owner supplied in the body is overwritten before validation, so a Workflow can never be created into a different Application than the one the caller was authorized against. The Workflow starts with no deployed revision; publish its flow graph through the revisions endpoints. Requires the Editor role. Responds 201 with a `Location` header pointing at the new Workflow, or 400 with per-field validation errors.

POST
/v1/tenants/{tenant}/networks/{network}/workflows

Authorization

Bearer
AuthorizationBearer <token>

JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.

In: header

Path Parameters

network*string

Id of the Application that will own the Workflow.

Formatuuid
tenant*string

The tenant identifier

Request Body

The Workflow definition. Its owning-Application field is ignored and replaced by the route value.

id*string
Length1 <= length
displayName?string|null
description?string|null
avatarFileId?string|null
tags?|null
networkId?string

The Application selected to own this Workflow at creation.

Formatuuid
[key: string]?never

Response Body

curl -X POST "https://api.fruxon.com/v1/tenants/string/networks/497f6eca-6276-4993-bfeb-53cbbbba6f08/workflows" \  -H "Content-Type: application/json" \  -d '{    "id": "string"  }'
{
  "id": "string",
  "displayName": "string",
  "description": "string",
  "avatarFileId": "string",
  "tags": [
    "string"
  ],
  "enabled": false,
  "currentRevision": 0,
  "createdAt": 0,
  "modifiedAt": 0,
  "networkId": "00000000-0000-0000-0000-000000000000"
}
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}
Empty
Empty
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}