postAutoFlowsByIdOperationsWithHttpInfo method

Future<Response> postAutoFlowsByIdOperationsWithHttpInfo(String id)

Edit a flow — rename it, retarget its trigger, or add, move and delete steps

Applies ONE flow operation and answers the thing it changed. The operation is named by type, with its arguments under request: CHANGE_NAME, UPDATE_TRIGGER, ADD_ACTION, UPDATE_ACTION, MOVE_ACTION, DELETE_ACTION edit the flow's LATEST version and answer with that version, and CHANGE_STATUS instead enables or disables the flow and answers with the FLOW. Two response shapes on one address is the rule a reader would otherwise get wrong, and it is why this route is not a typed op. Edits land on the latest version only — the published version a run executes is untouched until it is republished — and the whole resulting step tree is re-validated against the step-count and size caps after every operation, so a long sequence of ADD_ACTION calls cannot grow a flow past a bound one step at a time (422 when it would). Org-scoped and fails closed: a validated principal is required (403 without one), the flow and its version are read under the caller's OWN org so another tenant's id is a 404, and an operation whose request does not decode is a 400.

Note: This method returns the HTTP Response.

Parameters:

• String id (required):

Implementation

Future<Response> postAutoFlowsByIdOperationsWithHttpInfo(String id,) async {
  // ignore: prefer_const_declarations
  final path = r'/v1/auto/flows/{id}/operations'
    .replaceAll('{id}', id);

  // ignore: prefer_final_locals
  Object? postBody;

  final queryParams = <QueryParam>[];
  final headerParams = <String, String>{};
  final formParams = <String, String>{};

  const contentTypes = <String>[];


  return apiClient.invokeAPI(
    path,
    'POST',
    queryParams,
    postBody,
    headerParams,
    formParams,
    contentTypes.isEmpty ? null : contentTypes.first,
  );
}