https://www.activepieces.com logo
For piece development prioritisation, I think it w...
# 🐶|general
c
For piece development prioritisation, I think it would be great if oauth2 type connections were prioritised over API key connections. Particularly for platforms that don’t have a documented self-serve way to create an oauth2 app on their platform. For connections like that, if there isn’t an existing piece/connection, it’s essentially a hard block. Unlike for API key type connections. This is frequently the primary or only factor when I’m deciding on where to build an automation. I also think it could be great to prioritise the creation of connection only pieces, as that would likely be the highest ‘roi’ on dev hours. Once a connection exists, we can make our own custom api requests and are no longer hard blocked. So creating a lot of pieces that have no actions besides making custom api requests would be very useful. Having several pre-made actions covered is a nice-to-have but being able to connect at all is an absolute. Thin connection-only pieces could also serve as a great foundation that could be built upon and improved over time. Just some thoughts, anyone else think this would make sense?