Help with API for views/documents

Get Help
1

i need to vent:

i was wondering FOR LITERAL HOURS why n8n didn’t show me document views when i didn’t filter them. turns out documents dont show up when you FILTER OUT THE LIST VIEW TYPE. like… i may not be the most logical person to everyone all the time, but stuff like this is… like… wow!

i’m sorry but who the hell thought this would be even remotely logical?! i’m absolutely speechless!

the amount of hours i wasted on this so far is absolutely nuts. not showing documents when lists are filtered. LISTS! WHEN YOU HAVE A GODDAMN LIST ‘document type’ in the gui.

like… am i stupid? or is this as backwards unintuitive (bordering on out right bugged and broken) as i feel it is?

having a good api is absolutely crucial in order to make fibery work as the awesome tool it is when it comes to the front end!

oh and also: this isnt just a documentation problem. even implementing something as simple as showing all views and databases for all available views of a workspace took me dumb amounts of work, since in views the spaces are indentified by space id, while for databases in the schema it’s dead simple to implement because the databases are using their plaintext names. i really don’t understand why this can’t be done (or the space/view names be added) to the views api query output. imho if stuff like this (which i think one can expect from a paid tool in 2025) would be done, then the documentation doesn’t even have to be that in depth since being intuitive to use is even better than needing a thorough documentation.

2

Can you explain what you mean. Or perhaps explain what you are trying to do.

‘List view’ is not a ‘type’ (in the way that Fibery uses these words)

I’m not sure what you mean by this.

Are you talking about a ‘list view’?

3

It sounds like you’re using the API to find the views within a space or folder. Is that the case?
I know how intense things can get when you’ve been chipping away at error after error for a long time, but it’s hard to provide support without any context to what you’re trying to do and what exactly you’ve tried.

I recommend you create a separate thread so we can help you troubleshoot this specific thing you’re building separate from this conversation about improving the documentation.

2 Likes