Quick question about AI Bot Flow 400 Error during Zendesk Macro Migration

Architect & Flows
1

Background

Migrating Zendesk macros to Genesys Cloud AI Bot intents. Using Architect v2 to map ticket tags to bot slots.

Issue

The POST /api/v2/architect/flows request fails with a 400 Bad Request. The payload includes a valid JSON structure for the AI Bot flow, but GC rejects it citing ‘Invalid node type for AI Bot integration’.

Troubleshooting

Verified the node definitions match the Zendesk automation rules. Checked SDK version 2.0.1. No obvious syntax errors in the flow JSON. Does the AI Bot require specific node configurations that differ from standard Architect flows?

2

As far as I remember, the Architect API rejects flows missing specific node types during migration.

node_type = "ai-bot-intent"

Ensure the JSON payload explicitly defines this type to avoid the 400 error.

3

Oh, this is a known issue… The ai-bot-intent node type is deprecated in current Architect v2 schemas. Using it causes immediate validation failures on the POST endpoint.

Switch to ai-bot-nlu for the NLU action and ai-bot-response for the reply. The payload structure requires these specific node types to map intents correctly.