MattSpoonQ: I hope this message finds you well.
I am writing as a happy user of Tier 3 to share some valuable feedback and raise a concern about the current state of integrations, or “pieces,” on your platform.
First and foremost, I want to express my appreciation for the 108 integrations you have listed. However, I couldn’t help but notice a significant difference when comparing the number of “pieces” to the extensive range of “apps” offered by Make.com, which boasts over 1,000 options. And it's not about the number of apps, but rather about what individual pieces have to offer:
To provide specific examples, when examining the MailerLite integration, I discovered that it only offers one action. In contrast, Make.com’s MailerLite app provides a staggering 16 actions and three triggers. The same pattern is observed with other popular integrations like Webflow, Dropbox, and even Google Sheets. For instance, your Webflow piece only includes 1 action, whereas Make.com’s Webflow app offers 18 actions and 1 triggers. These stark differences have made me wonder why your pieces do not encompass the same array of actions and triggers that are available on competitor platforms like Make or Zapier.
As an enthusiastic user of your services, I believe it would greatly enhance the overall usability and appeal of your platform if you could align the functionality of your pieces with the most comprehensive actions and triggers offered by any API of a given tool. While I understand that the number of pieces continues to grow rapidly, it seems that their current functionality might not be as powerful or versatile as what is available on competing platforms. This discrepancy in functionality poses a challenge to non-coders like myself who rely on these integrations to streamline workflows and enhance productivity.
Why, when building out a piece, are you not implementing every trigger/action an API has to offer, or at least have a look on Make's website to see what their apps are offering, before releasing a piece?
I might don't have a good understanding of how pieces are developed. When I am requesting a piece, say an integration the tool Outseta, do I also have to mention what triggers/actions I am looking for?
I genuinely appreciate the effort and dedication your team puts into developing these integrations and expanding the pieces collection. However, I wanted to bring this concern to your attention in the hope that you can address it and provide more clarity on your integration strategy moving forward.
Ashraf_Activepieces
Jun 27, 2024A: I really appreciate the way you put together your feedback, pretty neat and helpful.
Different platforms take different approaches to scale their connectors. Zapier and Make are famous for bringing on partners to build the pieces.
In our case, we're still relying on our team and our community of developers to add these pieces.
We're working on exploring other approaches including the partnership model amd generating pieces with AI to strengthen this part of Activepieces.
Once we succeed with one of the approaches, we think the number of pieces will start hiking quickly (if anyone reading this thinks can help with ideas or implementing these ideas to scale up our pieces, we should talk).
To answer your question, when you request a piece on our roadmap, we'll appreciate it if you write in the description which triggers/actions you're looking for. That will give our developers better guidance.
I hope my anwer helps!
Damn, I love ChatGPT. I'm pretty sure that you're doing exactly as I do because the first line is a dead ChatGPT giveaway, "I hope this message finds you well." I've even instructed ChatGPT to never use a line like this but it always does.
Anyhow, I'm guessing that you probably told ChatGPT what you like about this software, the problems you run into, and it spit out what we see here which is clear and easy to understand. I'd love it if everyone did this so that things are easier to understand. Thanks!