Based on the knowledge sources, here's what can be said about creating new
destination connectors in Airbyte:
Creating New Destination Connectors Creating new destination connectors is
more complex than creating source connectors. Here's why:
•
Connector Builder is not available for destinations. The no-code Connector Builder only supports creating
source connectors. [
Connector Builder overview]
•
The Low-Code CDK also does not support destinations. Both the Connector Builder and the Low-Code CDK are limited to source connectors. [
Connector development options]
What you'd need to do instead To build a destination connector (e.g., for Freshsales or Brevo), you would need to use the
Python CDK or the
Java/Kotlin Dataflow CDK, which require actual coding. The destination connector development process involves multiple steps such as:
• Project scaffolding and build setup
• Database/API connectivity implementation
• Write operation logic (append, overwrite, dedupe, CDC)
• Integration testing
This is estimated to take
2–7 days depending on the complexity and features needed. [
Step-by-step destination guide]
Important note on contributions Airbyte has also stated that
until a declarative YAML interface for API destinations is in place, they will not be accepting open source contributions for new API destinations. [
Early Access announcement]
Summary So in short, creating a new destination connector for tools like Freshsales or Brevo is
not as easy as creating a source connector — it requires development effort and coding skills. 👍 0 button 👎 0 button ℹ️
Tip: Mention
@kapa.ai in the thread for follow-ups or
DM the app for
1-to-1 help., with interactive elements