Hey folks - generic question here. I'm working on a project where the client doesn't currently use Airbyte. They have a need to connect to an API for a 3rd party (very niche 3rd party) to call some custom endpoints. What are the pro's/con's to building a custom connector in Airbyte for this rather than simply building this separately as a standalone function, for example? I can see the potential long term benefits that if we introduce Airbyte, they have the option to add more sources as they evolve, but in the short term, is it overkill?

I think you've got it - it might be overkill right now, but the longterm potentially could benefit them.