Builder: Support gzip compressed XML in low-code connector via Cloud

[Airbyte Support (Airbyte-Support)]

Describe the feature request
The current low-code connector builder does not support decompressing gzip-compressed XML data, which is a limitation when loading gzip-compressed XML files from a presigned S3 URL. The customer wants to load such data using the builder but cannot due to this capability gap.

Describe the solution you'd like
Support for gzip decompression combined with XML decoding within the connector builder, enabling users to process gzip-compressed XML files directly.

[Airbyte Support Bot (airbyte-support-bot)]

Hi Airbyte Support (@Airbyte-Support), thank you for raising this!

We're looking into support for combining gzip decompression with XML decoding in the low-code Connector Builder, and we've escalated the request to our team for investigation: airbytehq/oncall#13387

A couple of things that would help the team scope this:

• Are you configuring a GzipDecoder (or any decoder chain) in the manifest today, and if so what does that portion of the YAML look like? Pasting it inline in a fenced code block is ideal.
• If you're seeing an error rather than a missing option, the exact error text from the test read, plus the Airbyte version (Cloud or OSS) and CDK version, would help.
• Does the presigned S3 response return Content-Encoding: gzip, or is it a gzip payload with a Content-Type like application/gzip / binary/octet-stream? The two behave differently in the declarative decoders.

Please make sure to mask or remove any sensitive information (API keys, passwords, tokens, presigned URLs, connection strings) before sharing manifests or logs.

---

Need more help? Join Airbyte Community Slack for peer support, or if you're a Cloud customer, open a support ticket referencing this URL.