Hey guys! I manage a multi-org setup where we have separate Genesys Cloud organizations for dev, staging, and prod. We are constantly building new digital channel flows in dev and then trying to promote them. The problem is that when we export an Architect flow and import it into prod, it completely breaks! The flow references queues and data tables by their GUIDs, but those objects have completely different IDs in the production org. Is there a way to use the Platform API to sync configuration objects so the IDs match across all three organizations? Or how else are people handling deployment without manually fixing every single drop-down in Architect after an import?
You cannot synchronize GUIDs across different Genesys Cloud organizations. Each object creation generates a unique ID specific to that environment. To solve the deployment issue, use Archy, the Genesys Cloud Architect scripting tool.
When you configure Archy, you define an archyDeploy.yaml file. This file allows you to map dependencies dynamically.
You specify the queue name in the YAML, and during deployment, Archy calls the Platform API to look up the correct GUID in the target organization and injects it into the flow.
Hello. I faced this exact problem when I was migrating digital channels from Zendesk into multiple Genesys Cloud environments. The first reply is correct about Archy.
However, if you are strictly using the Platform API for your own deployment scripts, you must build a translation layer. When I copy a Data Table, I use the GET /api/v2/flows/datatables endpoint to search by the table name in the target org.
Then, I take that new ID and do a string replacement in the exported flow JSON before I push it. It requires careful coding but it works very well.
Transitioning from PureConnect, we also struggled with this environment segregation. PureConnect handled server promotions much differently. To add to the previous responses, if you use the Platform API for custom deployment, heavily utilize external tags and standard naming conventions.
We append _DEV or _PROD to resource names. Your deployment script should strip the suffix, query the target organization API for the base name, retrieve the target GUID, and execute the substitution.
Never hardcode GUIDs in integration scripts.