Http POST to wordpress doesn't update custom field

Describe the problem/error/question

I want to update post’s custom field on a WP instance. I use HTTP node, since I have no option to update meta field using the WP node.

As response, I got the supposedly updated post. But when I check the custom field, it still has the old value.

The body sent is

{
    "meta": {
        "link-tool": "https://www.example.com/"
    }
}

Authentication is not an issue, since I got no error.

I made the same request with make.com, with a generic http module, and worked immediately.

Now, I am not sure where I can check the actual request sent through N8N, so I am not sure what N8N sent, but since it gave me no error, I am really puzzled on why is happening.

To be noted
I just discovered that this is happening with postman too. The only difference between N8N / Postman and Make.com is the authentication method. Make.com use a plugin to generate an api key, N8N and Postman use the native application credentials from WP.

I suppose that could be reason? Not sure, though…

What is the error message (if any)?

No error message, simply the edit on the post’s custom field isn’t done.

Please share your workflow

Information on your n8n setup

  • n8n version: 1.39.1
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Ubuntu

I am noticing more discrepancies between modules in Make.com and node in N8N regarding WordPress.

Another thing I noticed:

searching for post using slug give different results. Specifically, correct in make.com and incorrect in N8N.

I don’t think is authentication-related, but it concerns me a lot.
I would like to use N8N more and more, but since it’s not reliable as make.com in simple requests, I am a bit frustrated.

Also, if I make a request and gives me response, I suppose that is correct, which is not the case now…

I am a bit frustrated.

Hi @giacomolanzi, thank you for reaching out and being a part of the community!

I’m sorry you’re experiencing some difficulties. There is a mistake in the request made to your endpoint (https://automatiking.com/wp-json/wp/v2/posts/34899) in your workflow.

The field link-tool is not nested under meta in your JSON structure.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.