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 external_id to round-trip your internal ticket or order ID so you can join the webhook back to your system without a lookup table. Read custom_fields 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, external_id 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, custom_fields is an object keyed by numeric field ID (for example 301), not by field name.