Really loving Airbyte so far, thanks for the great product and even better community support! I'm working on a less straightforward use case and would love some advice on if there's a good pattern for supporting it (or if it's not a good fit!). We have an application that lets users pull data, then we build visualizations on top of this data for each customer. We're currently handling the integrations via custom code (no tap or other services), which lets us easily append customer specific data (eg: our internal customer id). I'm trying to figure out if there's a good way to integrate Airbyte in a similar way that supports a self sign up flow. I think there's an alpha API which lets me programmatically create configurations, but is there an easy way for me to either: Add custom data to each integration event or assign a raw table name ahead of time so I can map it to a specific customer in our system? I was thinking I could probably modify an existing connector, but I'm wondering if I'm missing an easier way to handle this.

Hi @Zach that is a great question. Today we don't support enriching data. We want to stay as close as possible to the source data definition. However this month we are working on a better naming scheme that gives more control to users. At that point I think we can handle your use case where you will be able to add a specific id to each of the table names. One way you could make it work today though: create one destination per customer so you can use a different schema/database this way you only need to remember the dstination id for each customer and everytime you create a new connection for one customer, you use the associated destination id. WDYT?

@Michel Thanks for the quick (after hours) response and the solution! Since the named tables are on the roadmap in the near future, I'll likely hold off on testing this out for now. I'll keep an eye out on the releases!