Zendesk Ticket Field Mapping to GC Data Action

How should I properly to map Zendesk custom fields to Genesys Cloud data actions? The Ticket-to-Interaction mapping seems fundamentally different from our old Zendesk setup. Getting a 400 Bad Request on /api/v2/data-actions when trying to push metadata.

The best way to fix this is to ensure the Zendesk custom field IDs match the exact schema expected by the Genesys Cloud data action definition. The API rejects any mismatched field types immediately. Check the documentation for the specific integer mapping requirements.