Iām a newcomer to the platform, and this is also a big problem for me. I donāt have a clear picture of what actions are available because the naming seems random. And because there is no grouping, such as under a top-level Pipedream namespace for core functions, I donāt feel confident that I even know what core functions are available. It always feels like Iām missing something, and there doesnāt appear to be any good way to search. I also find the browsing experience difficult to use.
Itās funny, this is actually worse since I posted this.
Itās overall better everywhere on the platform, nothing but upgrades but the grocery shop and ingredients is worse because the scope of these features has grown and itās almost too easy to get lost in the sauce now.
I have a notion table with names and functions as a ācheat sheetā I make it each time I connect a new account and have a list and keep my eyes peeled for changes and update it.
Itās like a code library, you need to maintain it
@davies Too bad! This seems like low hanging fruit, but maybe itās harder than it seems. But Iāve spent way too much time scrolling their list of actions. If you have the Notion table made in a way that you can share it, Iād love a copy.
Iāll happily share that. Need a bit of time because itās in my internal tools and has some specific references to flows I have. Gonna do some hygiene and post it
I ended up going to the github repo and downloaded all of the codebase and parsed out the folders of the componants. it says i have 1500~ componants, which Pipedream says it has over 2500. not sure if this just doesnt include the ones that were without actions that just had auth for custom code?
Good idea! I may want to try to categorize these for easy searching. The group that I want to be able to see the most is just core functions. Donāt suppose you could either export this or make it editable so that I can duplicate into my own workspace?
The core functions were migrated into a āPipedream Utilsā app. This includes the Helper Functions and Formatting components. Since there are many āoldā actions, feel free to submit feature requests / bug reports in our public repo!