Hari Haran R
12/17/2025, 9:38 AMkapa.ai
12/17/2025, 9:38 AMapp_api_key correctly. [[Customer.io source](https://docs.airbyte.com/integrations/sources/customer-io)] 2. **Customer.io *destination*** - This is a newer destination connector that explicitly requires Airbyte 1.8 or later, or Airbyte Cloud. [[Customer.io destination](https://docs.airbyte.com/integrations/destinations/customer-io)] - If you try to use this destination on OSS 1.4, you should expect problems or it may not work at all, because the connector is built against newer platform capabilities (e.g., Bulk CDK, rejected-records handling, etc.). Given you’re on OSS 1.4, the most likely reason your “customer.io connector is not working” is: - You are trying to use the Customer.io destination, which officially supports 1.8+ only, not 1.4. What you can do: - If you need Customer.io as a destination, you’ll need to: - Upgrade your Airbyte OSS to 1.8 or later, or - Use Airbyte Cloud, which supports that destination. [[Customer.io destination](https://docs.airbyte.com/integrations/destinations/customer-io)] - If you only need to read from Customer.io (as a source), use the Customer.io source connector and configure it with an App API Key. [[Customer.io source](https://docs.airbyte.com/integrations/sources/customer-io)] If you’re still seeing a specific error on 1.4 after this, the knowledge provided here doesn’t include detailed error logs for Customer.io on 1.4, so I can’t say more precisely what’s failing. In that case, Airbyte recommends checking the connection’s error message in the UI and, if you have Enterprise support, opening a ticket via the Help Center. [[Enterprise support](https://docs.airbyte.com/platform/1.6/community/getting-support#airbyte-enterprise-self-hosted-support)]