Hey, I’m building a tap for the Google Places API. Basically, it sends data like a company name and stores it somewhere. Wondering if this is a common use case. Usually, I haven’t seen taps passing output directly to another tap’s input

What's the other tap in this scenario?

tap-snowflake

Gotcha. So you need to enrich the output of one tap with that of another? That's certainly not a well-supported use case, thought there's the concepts of mappers, which can be used to enrich/map/obfuscate data but it gets complex when there's data joining involved. That said, an arguably better and more common approach is to join the data after it lands in your data(base|warehouse).

I think it’s more about reducing the scope for requesting data. For example, I can’t query the whole Google Places API. I’d like to provide a list of attributes to act as a filter for the requests and then pipe it to my db.

I'd use a config variable. You can have a list property for a config object and provide whatever you want to have it filter by.