Replies: 1 comment
-
Thanks so much for filling in the survey! Please keep the responses coming, it's hugely appreciated :) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
🎉 The wait is over!
Thank you for taking the time to share your feedback during our Data Activation discovery period. I’m excited to share that Data Activation is now available in Early Access and you can try it out today to move data into Hubspot & Customer.io destinations!
To get started:
👉 Check out our docs here for setup details and best practices.
👉 You can get started today and see value in just a few minutes.
👉 If you have feedback or want to discuss your use case further, please fill out this form — we’d love to hear from you!
We’re thrilled to announce that Airbyte has been hard at work building out Data Activation capabilities (reverse ETL). With Data Activation, you can now use Airbyte to load your consolidated and transformed data into the SaaS tools (HubSpot, Customer.io, and more) where actions get taken. This is a major step forward in making Airbyte not just your solution for consolidating data from 600+ sources into data warehouses, databases or data lakes, but an end-to-end data movement platform.
We’ve been listening: as part of evolving as an Open Standard for moving data, Airbyte should allow for pushing insights back out into SaaS tools. Our ambitions are to eventually support 200+ fully Open Source API destinations, and by releasing Data Activation into early access, we’re taking our first steps.
The early access includes:
Of these, we are particularly excited for UI capabilities to map source fields to the required destination schemas. SaaS tools are particularly finicky to write data into: they require fixed data structure, types and have dozens of validation rules. We help introspect destination schemas for you to reduce the margin of error in configuring new syncs, and allow you to map fields all in one place:
We fully intend on building out an equivalent declarative language (see our manifest for API destinations to support the growth and maintenance of a future 200+ API destinations in the Airbyte Catalog. Until this YAML interface is in place, we will not be accepting Open Source contributions for new API sources.
Get Involved
This is just our first step with Data Activation. We’re looking for early access users to help shape what’s next (sending test records, roadmap for new destinations, and much more). If you’d like to participate, fill out this form now.
Beta Was this translation helpful? Give feedback.
All reactions