Running into a wall trying to get a full JSON dump of our Architect flows using the CX as Code CLI. We’re trying to set up a proper git-based workflow for our flow definitions, so I need the actual flow JSON, not just the config wrapper.
I’ve got the CLI installed and authenticated via environment variables. The command I’m running is:
genesys cloud export --type flow --output ./flows
The command completes without error, but the resulting files in ./flows are just the metadata objects (name, description, id), not the flow definition itself. The flow property inside the exported JSON is null or missing entirely.
I’ve tried a few things:
- Using
--include-depsflag. Doesn’t change the output structure. - Specifying a specific flow ID with
--ids <id>. Still just metadata. - Checking the API directly. If I hit
/api/v2/architect/flows/{id}with a bearer token in Postman, I get the full flow JSON back. So the data exists and I have access. - Looking at the
genesys cloud exporthelp docs. There’s no flag for “deep export” or “include definition”.
Is this a known limitation of the CLI? Or am I missing a config file setting? The docs say it exports “resources”, but for Architect, the resource definition is the whole point.
Here’s what the exported JSON looks like:
{
"id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"name": "Main IVR Flow",
"description": "Primary routing logic",
"type": "flow",
"version": 12,
"createdTimestamp": "2023-10-25T14:30:00.000Z",
"updatedTimestamp": "2023-10-26T09:15:00.000Z"
}
No flow object. Just the header.
I can write a script to hit the API for each ID, but that feels like reinventing the wheel. The CLI should handle this.
What am I missing?