Would love to have the ability to change the column width too.
I know this can be done indirectly by changing card size, but it’s still a pre-set width.
Is there a plan to make these into separate nodes? Takes more effort to only trigger on one event. Not the end of the world I think though… Haven’t tried.
It’s definitely possible. For first release decided to implement the easiest and the most flexible node which utilizes our webhooks api. If there will be a need for more granular events, we can implement some polling-based nodes, same as we do in Zapier
2 Likes
Very nice!
We’re using it already to push our fireflies conversations to fibery.
Would be glad if you can add the json field type to the entity update/creation as you can add it in fibery as field 
how do you want to use json field in Fibery?
Hey, thanks for reply!
currently you can’t select the json fields so far. It would be really nice if i we can, the value must then either a JSON.stringify() representation or an array/object. Since it’s javascript it should work i think.
1 Like
Well, JSON field in Fibery is kinda hidden and not officially supported What for you use it in Fibery?
6 posts were split to a new topic: New Field Type: JSON
super excited about the N8N integration and the sharing improvements!
2 Likes
Hi everybody, first of all im very excited about this N8N integration, I’ve been waiting for this a lot, so cheers and thanks to all who are working on this.
I have a question regarding the usage of the update entity action.
I select the the database, I pass the UUID of the entity, but no configurable or mapeable inputs for updating the entity are shown in the UI, it just let me choose the “Output fields” that are shown when the node is executed.
Does anybody knows what I’m doing wrong?
I’m running package version v0.1.13
Thanks!
Have you tried clicking the Add field button?
1 Like
Yep, Chris is correct.
Please use “Add field” to construct the entity input
Thanks guys for your replies, yes I confirm that the Add field button is working properly now:
I had already tested yesterday and the “Value” input wasn’t being displayed and the workflow failed. Not sure why, maybe with v0.1.13 that was fixed.
Thanks again
yeah, there was a bug with number inputs…
It was marked [beta] for a reason 
Please let me know if you face more issues
Sure, thanks again and congrats about this huge work. I will keep you posted if I face another issue, is this the right place to post them?
Better to create a separate topic or drop a message to support from inside the Fibery.