Is the product polished? We need your inputs

This is another big one for me: the flow of data quickly becomes unmanageable, especially for non-technical users. I’d like to see things like local variables and (global) constants, for example to share a Google Drive folder ID across flows.

Flow-scoped storage tasks can be (ab)used as local variables, but it’s often tedious and/or counter-intuitive to use. (For example, using the result of a “Put” task as an input for something else.) I’d love to see a dedicated system for this that’s easier to manage, maintain and takes up less valuable screen real estate.

(Again, I’m still working on formulating some more coherent thoughts and suggestions!)


As a bit of extra perspective: the concept of a file being (stored at) a URL is often alien to non-technical users. They’re used to files being “a thing” that they can just throw around, expecting the recipient to just be able to deal with it.

This leads into another concept I’ve dunked in the Discord a while back (abstracting JSON/YAML as a piece’s “values”), but I (again) still need to write a more coherent proposal for it…


True, I guess a note like “File accessible at the following link:” might help

Even so, file name and file type should be available in the output at the very least.

1 Like

Hello @S_M, this issue should be fixed in about 15 mins from now, cheers to all of you guys pointing stuff out, we really appreciate it.


This is what I really appreciate about Activepieces - devs who act quickly and listen to the community. Please don’t see this thread solely as negative critique; the only reason people are taking the time to comment is because they believe in the product and want to help make it even better.

Keep up the great work!


Spotted another good example of “meh” error handling and abstraction leak in another topic:

This is a weird combination of mixed signals for non-technical users. I absolutely see why it’s like this, an HTTP 400 is a valid response for a “succesful” request, but for an end-user the thing they wanted to happen has failed. Activepieces doesn’t always recognize this properly, which can lead to even weirder behavior down the line.

I’d like to see Activepieces become much more vigilant in this type of error handling, i.e. fail-fast in programmer’s terms. Deployed flows ideally don’t receive attention from humans, so errors could currently easily go unnoticed for extended periods of time. Error handling and resiliency is already incredibly hard to get right for even experienced programmers, I’d love to move as much of this burden to Activepieces rather than the (non-technical) users.

The “output values” idea I mentioned earlier could help with this, since it creates a clear “expected value”, which makes it much easier to detect when something weird happens.

Like @Dennis said, please don’t let my flood of (hopefuly constructive) criticism get to you, Activepieces is already a solid product with tons of potential to become the greatest in its class!
I’d also like to mention again that it’s 100% my intention to actually help contribute to these things rather than functioning as the classic “idea man”, but unfortunately health issues are a limiting factor at this point in time.

1 Like

Thanks, Abdul, this has been fixed! :slight_smile:
@Abdul If you could please fix the trackpad scroll bug I mentioned here too:

Another example of problematic error handling from another topic:

hi @S_M what do you mean with Auto-save for flows?

It feels like my concepts are saved right automatically? Or is this maybe just the cloud solution?

Sorry @Bram, I was tired when I wrote that.

I meant revert to an auto-saved flow instance, not just a published instance.

For example, if you don’t ever publish a WIP flow but have been working on it for several days or even weeks, there’s no way to go back if you make a mistake.

This would also extend to undo/redo functionality which @Dennis mentioned.


No problem! I understand what you mean. Makes sense

Also not sure if it is mentioned but saving HTTP pieces would be amazing, I’ve set up quiet a lot of HTTP Pieces but have to set these up again for every flow. Saving these and reusing them would be amazing and saves a lot of time.

Besides that Pabbly has set-up something a while back where it is easier for users to create these HTTP pieces please see this video,

Kr Bram


Yes, 100%! Same for the Code pieces, please!


Another example of unpolished/undocumented/unintuitive behavior: Google Drive "Read file" bug? - #3 by abuaboud

1 Like

Thanks for asking!!!

I’d suggest a few things:

  • Undo and redo button at the top of the screen.
  • More info on errors and input fields. For instance, in the Drive piece, in Folder ID there is no information on what folder id is or where to get it (I already got it, but sometimes it is frustrating not having any help on how to get it)
  • A view of favorite pieces.
  • A view of favorite flows.
  • A changelog on pieces to see what changed or new improvements.



A lot of pain is caused by the lack or poor documentation of feature blocks and the lack of implementation examples. I know that you have this functionality that I need, but I can’t start using it, because all that you have written about it is that it exists…

Example - 🔒 Authentication for Webhook - #3 by Konrod

And yes, I write about this because I like what you do and how. If I didn’t believe in the product and your team, I would simply leave.

1 Like

I can see the effort and the community, but in my opinion the product is far from polished.

The reason being is the lack of Pieces as well as the lack of triggers/actions for the ones existing. In many cases, it’s members of the community, and not from ActivePieces, that create them altruistically.

I knew Activepieces was a young project when I purchased it, but I was not expecting it to develop at this slow pace. However, I still have faith :muscle:

1 Like

Despite being a paid user, am unable to use AP. It breaks, especially chat gpt. Most of the templates (1500 word blog, for example) does not work

1 Like

What do you mean by “it breaks” and “does not work”? Can you help us understand your perspective?

Yes, in fact both. Have showed @kishanprmr this. CHat GPT token doesnt work. Simple Rss to Twee does not work.

And the one use case that I bought AP for (Automatic blog writing from SHeets), never worked. Sharing the issue link with you to you.

The documentation is lacking. Eg. I still haven’t managed to connect Excel, as there is no complete documentation and nobody replies to the topic in this forum.