Update tags on wf, some tags not found

Describe the problem/error/question

Hello,
I wanted to create workflow tagger what will update workflow tags. It seems to n8n api complain on something what I don’t agree with, so I am confused.

What is the error message (if any)?

I am getting on request node error:

The resource you are requesting could not be found [item 0]
Some tags not found

Error code: 404
Full message: 404 - "{\"message\":\"Some tags not found\"}"
Request: 
{ "body": [ { "id": "E85csJjVdrH7f9kb" }, { "id": "2QPXVOFCQ9izGgIF" } ], "headers": { "accept": "application/json,text/html,application/xhtml+xml,application/xml,text/*;q=0.9, image/*;q=0.8, */*;q=0.7", "X-N8N-API-KEY": "**hidden**" }, "method": "PUT", "uri": "https://mws02-51638.wykr.es/api/v1/workflows/0yJr6l6jR1njqDBX/tags", "gzip": true, "rejectUnauthorized": true, "followRedirect": true, "resolveWithFullResponse": true, "followAllRedirects": true, "timeout": 300000, "encoding": null, "json": false, "useStream": true }

So I try assign tags: E85csJjVdrH7f9kb and 2QPXVOFCQ9izGgIF on wf with id 0yJr6l6jR1njqDBX
I see on other request that api return those tags:

[
  {
    "data": [
      {
        "createdAt": "2025-01-12T02:34:33.484Z",
        "updatedAt": "2025-01-12T02:34:33.484Z",
        "id": "E85csJjVdrH7f9kb",
        "name": "aidevs"
      },
// [...]
      {
        "createdAt": "2025-02-02T16:34:09.518Z",
        "updatedAt": "2025-02-02T16:34:09.518Z",
        "id": "2QPXVOFCQ9izGgIF",
        "name": "chainLlm"
      }
    ],
    "nextCursor": null
  }
]

Please share your workflow

Information on your n8n setup

  • n8n version: latest
  • Database (default: SQLite): sqlite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): selfhosted
  • Operating system: linux

Any idea what I could do wrong will be appreaciated :3
Thanks

hi @Shirobachi

Is that error coming from the endpoint of that last node? The error might be coming from that third party API and not n8n necessarily,

can you make sure the API call makes sense outside of n8n as well?

Thanks!

1 Like

I really believe that’s the case here:

I might not have been clear enough—those two request nodes are actually custom API calls within n8n

I have two instances, and interestingly, it works just fine on another one (n8n Cloud) :smiley:

Not sure why, but it seems like there’s an issue with my instance specifically. I’ll investigate further later this week and update this thread if I find anything.

Thanks for the hint! :heart:

— Simon

2 Likes

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