N8N and Fibery Integration Error (RichText)

What does your POST request look like?

We will probably get round to it at some point, but there are currently other priorities.
Out of curiosity, what advantages do you see that N8N has over say Zapier or make.com ?

I don’t mean to sound churlish, but if you’re using N8N to sent http POST requests, then there is not much specific to Fibery+N8N to be explained. POST is just a standard mechanism, so it shouldn’t matter if you’re using N8N to send a POST request or using any other REST API client.

Of course, there are plenty of people who think that the Fibery API is hard to understand, but I don’t think that’s an issue exclusive to N8N.