Elevenlabs agents push fails with 422 UnprocessableEntityError (without workflow)

[adiixs]

Description

The elevenlabs agents push command fails with a 422 UnprocessableEntityError.

Importantly, this specific agent's configuration doesn't even have a workflow, and the start node is in this configuration.

Reproduction steps

elevenlabs agents init
elevenlabs agents pull --agent <agent-id-without-workflow>
elevenlabs agents push

Important note: the agent configuration should not have workflow configured, as on example below.

Actual behavior

The push command fails with the following error:

UnprocessableEntityError
Status code: 422
Body:

{
  "detail": [
    {
      "type": "value_error",
      "loc": [
        "body",
        "workflow",
        "nodes"
      ],
      "msg": "Value error, Workflow must contain a start node.",
      "input": {
        "startNode": {
          "type": "start",
          "position": {
            "x": 544,
            "y": 64
          },
          "edge_order": []
        }
      },
      "ctx": {
        "error": {}
      }
    }
  ]
}

Agent configuration

   ...
   "workflow": {
        "edges": {},
        "nodes": {
            "start_node": {
                "type": "start",
                "position": {
                    "x": 128,
                    "y": 64
                },
                "edge_order": []
            }
        },
        "prevent_subagent_loops": false
    }

Expected behavior

Agents push command should succeed even if workflow is not configured.

[jschippergoauto]

I'm having the same issue since 2026-01-30, this worked fine the day before. Changing the node in the JSON file does not help.

Edit: using version 0.3.3 pushes successfully. It looks like this PR broke it: #54

[PennyroyalTea]

Fixed in #60.

The root cause was the SDK bump in #51 (2.26.0 -> 2.29.0) -- the newer SDK started returning a workflow object (with a start_node entry) even for agents without an explicit workflow. On push, toCamelCaseKeys was converting those node/edge identifier keys (start_node -> startNode), so the API could no longer find the required start node and rejected the request with a 422.

The fix preserves workflow nodes and edges child keys from case conversion, since they are user-defined identifiers rather than schema fields.

[PennyroyalTea]

Released in 0.4.1.