Airbyte is an open-source data integration engine that helps you consolidate your data in your data warehouses, lakes and databases.

Airbyte

<@U04S8PLJWMT> i'm using  airbyte open source 1.4 and trying to connect <http://customer.io|customer.io> but when i try to enter the creds its failing, it also says its maintainted by fargos AI
The <http://Customer.io|Customer.io> source is maintained by <https://github.com/faros-ai/airbyte-connectors/tree/main/sources/customer-io-source|Faros AI>. so does this connectr work in airbyte or not?

The <http://Customer.io|Customer.io> **source connector does work in Airbyte**, but it is a **community / Faros‑maintained connector**, not an officially supported Airbyte connector.  From the docs:  - The <http://Customer.io|Customer.io> **source** is explicitly marked as maintained by Faros AI and lives in their repo. [[<http://Customer.io|Customer.io> source](<https://docs.airbyte.com/integrations/sources/customer-io>)]   - Airbyte’s docs list the Faros TypeScript CDK and connectors as **community maintained** and “not officially supported” by Airbyte; issues should be raised with the Faros project. [[Community CDKs](<https://docs.airbyte.com/platform/connector-development#community-maintained-cdks>)]   - A forum thread about a Faros‑maintained Jira source shows Airbyte staff directing users to raise issues on the Faros GitHub rather than Airbyte’s, reinforcing that Airbyte doesn’t debug those connectors. [[Jira + Faros](<https://discuss.airbyte.io/t/3106>)]    So:  1. **Yes, you can use the <http://Customer.io|Customer.io> source in Airbyte OSS 1.4**, but:    - Airbyte itself does not guarantee support or fixes.    - If credentials fail or config validation is broken, you’re expected to open an issue in the Faros AI connectors repo: <https://github.com/faros-ai/airbyte-connectors/issues/new>. [[<http://Customer.io|Customer.io> source](<https://docs.airbyte.com/integrations/sources/customer-io>)]  2. For your specific “enter creds and it fails” problem, the knowledge sources don’t include error details or troubleshooting for this connector, so I can’t say exactly why it’s failing. The docs only state that you need a **<http://Customer.io|Customer.io> App API Key** in the `app_api_key` field. [[<http://Customer.io|Customer.io> source](<https://docs.airbyte.com/integrations/sources/customer-io>)]  If the same config works directly against <http://Customer.io|Customer.io>’s API but fails in Airbyte, the next step is to:  - Double‑check you’re using an **App API Key** (not Track API key, etc.), and - Open an issue in the Faros AI repo with:   - Airbyte version (1.4.x),   - Connector name/version (`source-customer-io` and its version),   - Full error message and screenshot.