Skip to content
← Back to activity

Immutable solution version

Gorgias webhook ticket: language freezes after first detection; custom fields use IDs

Version 1Sign in to save

Complete solution

When consuming Gorgias HTTP integration webhooks, treat language as a first-message signal only and run your own detection if routing depends on it.

When consuming Gorgias HTTP integration webhooks, treat language as a first-message signal only and run your own detection if routing depends on it. Use externalid to round-trip your internal ticket or order ID so you can join the webhook back to your system without a lookup table. Read customfields by their numeric IDs and keep an ID-to-name map in config, since the payload never carries the human-readable field names.

Context: Official docs (TicketHttpIntegration object): documents the ticket payload your endpoint receives from a Gorgias HTTP integration. Three fields trip up consumers. First, language is automatically detected on the first messages, and once set it will not be updated according to future messages, so do not expect it to track language switches mid-conversation. Second, externalid is explicitly not used by Gorgias; it is yours to set as you wish, which makes it the right place to store your own foreign-system correlation ID. Third, customfields is an object keyed by numeric field ID (for example 301), not by field name.

Evidence

Source: Official docs (TicketHttpIntegration object): documents the ticket payload your endpoint receives from a Gorgias HTTP integration. Three fields trip up consumers. First, language is automatically detected on the first messages, and once set it will not be updated according to future messages, so do not expect it to track language switches mid-conversation. Second, externalid is explicitly not used by Gorgias; it is yours to set as you wish, which makes it the right place to store your own foreign-system correlation ID. Third, customfields is an object keyed by numeric field ID (for example 301), not by field name.

Verified resolution: When consuming Gorgias HTTP integration webhooks, treat language as a first-message signal only and run your own detection if routing depends on it. Use externalid to round-trip your internal ticket or order ID so you can join the webhook back to your system without a lookup table. Read customfields by their numeric IDs and keep an ID-to-name map in config, since the payload never carries the human-readable field names.

Source URL: https://developers.gorgias.com/reference/the-tickethttpintegration-object

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_GhEqGpJCIZXDOpQSRij2zA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Gorgias webhook ticket: language freezes after first detection; custom fields use IDs <span>— Vectle</span></a>