Unfortunately I mostly share the experiences of @Adik and @Tobias_Geisler.
In theory Activepieces is a great product, but there’s next to no documentation and pieces are more often than not fragile and/or unintuitive. Activepieces markets itself als “no-code business automation”, but in my experience it’s too much of an abstraction leak and definitely not reliable enough to serve these purposes well.
On paper there’s a large number of pieces/integrations, but in practice a lot of them are incomplete, fragile or outright broken. It feels like a classic “quantity over quality” situation.
I suppose this might be a case of “open source syndrome”: a bunch of awesome people have graciously donated their time to contribute pieces for their usecase, without taking into account the platform as a whole. This seems to have created a flood of low quality/poorly thought out/fragile pieces.
To be clear, I don’t think this is the responsibility of these awesome contributors. They just want to get their work done, they’ve already gone out of their way to donate their time to someone else’s commercial product. However, given that Activepieces is a commercial venture, I’d expect the developers to be more involved with quality control, for example by adjusting and extending these altruistic contributions to match quality standards.
Please don’t see this as some kind of roast though! I assure you all of my (admittetly intense) feedback comes from a place of love and genuine enthusiasm for this project, and I hope I’ll be able to contribute more to improving these things soon.