From looking at the qs.customFieldMask.join is not a function error message it appears the node is expecting an array rather than a string. Perhaps you want to try using an expression (not a fixed value) of {{ ["Employee_Information"] }} here? Like so:
But also I’m really not happy about it.
If what I’m pushing is correctly formatted (array), I shouldn’t have to use expressions that are otherwise not needed here as nothing get’s referenced and no JS is used.
I wouldn’t be surprised as much by this if it would be a manual https call but this is a pre-made node that.
On the flip side I really like that it correctly handles paging and I can pull a whole domain in one go, it’s probably a main benefit of pre-made nodes like this.
HI @Mateusz_Bijakowski, I understand the frustration and actually share it to some extent. It’s often hard to figure out how to use some of our nodes when going beyond the default options. I’m sorry for the trouble this has caused.
That said, our product and design teams do read these forum posts regularly, so sharing your experiences here will help us to improve them.