build-cloud-flow

dci build-cloud-flow

Creates a new CloudFlow and generates its nodes and connections based on the provided natural language intent. The operation streams incremental build events, including the ID of the newly created flow, as they are produced.

Request

Content-Type: application/json

Schema

{
  "type": "object",
  "required": [
    "question"
  ],
  "properties": {
    "question": {
      "type": "string",
      "description": "Natural language description of the CloudFlow to build from scratch."
    },
    "conversationId": {
      "type": "string",
      "description": "ID of an existing conversation to continue. When omitted, a new conversation is started."
    }
  }
}

Output

OK - Build event stream.

By default dci renders the result as a table. Use --output json to get the full structure described below — see Output formats.

Returns: string

Raw JSON schema

{
  "type": "string"
}

Errors

On failure, dci prints a single error message — with a hint when one is available — and exits with a typed code your scripts can branch on. See Errors and exit codes for the full contract.

HTTP status	Exit code	Error code	Meaning
400	30	VALIDATION_ERROR	The arguments or request body were rejected. Review the command's flags and payload.
401	10	AUTHENTICATION_FAILED	Not signed in, or the API token is invalid. Run dci login or check DCI_API_KEY.
403	11	PERMISSION_DENIED	The DoiT user or the active customer context does not have access.
406	1	API_ERROR	The request failed; the printed error message has details.
500, 502	40	API_SERVER_ERROR	The API failed to process the request. Retryable; contact DoiT support if it persists.

Aliases: buildcloudflow