Summary
When running sync in Airbyte with Stripe sourceDefinition, missing fields that are null in Stripe are not included in the payload. User wants to influence Airbyte to send complete payload even when fields are explicitly null.
Question
I use Stripe sourceDefinition version 5.6.0. No transformations are performed in my custom destination. When I run discovery schema for source, I see all the fields that I need. Some of them can be null and I handle it on receiving side. However, when I run sync, I receive data with some fields missing. It happens, when they are null in Stripe. But I already have logic for webhooks processing, which respects null - and I want to reuse it. How can I influence airbyte to send complete payload, even when fileds are explicitly null?
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.