Why is Vtiger returning an unexpected or incorrect record ID when creating Cases via Zapier?

This issue can occur when Zapier captures or maps a different response field instead of the actual Vtiger record ID.
In Vtiger, the correct record ID is typically returned in the format moduleIDxrecordID (for example, 63x199928 for Cases). However, in some integrations, multiple fields such as id and ID may be present in the API response. If Zapier maps the wrong field or performs deduplication between similar fields, it may return an unexpected ID format.

To resolve this:

• Check the raw API response/output in Zapier
• Identify the correct Vtiger record ID field (moduleIDxrecordID format)
• Update the Zap mapping to use the correct field
• Review if any deduplication or field mapping logic in Zapier is affecting the output