Outbound Campaign 422 Error When Mapping Zendesk Custom Fields to Genesys List Columns

General Discussion
1

I’m trying to figure out why the Outbound Campaign API is rejecting our list upload payload with a 422 Unprocessable Entity. We are in the final stages of migrating from Zendesk to Genesys Cloud. In Zendesk, we handled outbound lists by simply appending custom fields to the ticket JSON. It was incredibly straightforward. We assumed the Genesys Cloud approach would be similar, just with a different API endpoint.

The specific error message states: “Invalid column mapping. The source field ‘zendesk_custom_priority’ does not match any configured list column type.” We are using the /api/v2/outbound/lists endpoint to create the initial list structure. The payload includes a definition for ‘zendesk_custom_priority’ as a string type. However, when we attempt to associate this list with a campaign via /api/v2/outbound/campaigns, the 422 error persists.

We have verified that the column exists in the list definition. We even tried mapping it to a generic text field in the campaign settings, but the validation fails before the campaign is even created. This is frustrating because the Zendesk workflow allowed dynamic field injection without pre-defining rigid schemas. Genesys Cloud seems to require a strict one-to-one mapping that we are struggling to configure correctly.

Is there a specific sequence for creating list columns before defining the campaign? Or is there a hidden constraint on how custom fields from a Zendesk export must be transformed before ingestion? We are using the latest Genesys Cloud API SDK (v3.2.1). Any advice on aligning these schemas would be appreciated. We want to ensure the migration preserves the context of why the call is being made, just like it did in Zendesk.

2

This is caused by strict schema validation on the list upload endpoint. The 422 error means the JSON structure doesn’t match the expected format for custom field mapping. Check if the z field is defined in the list schema before uploading.

"custom_fields": [
 {
 "id": "z_custom_id",
 "value": "..."
 }
]