N8N API Update Workflow needs to handle Settings

[Lesterpaintstheworld]

Hello!

Using the N8N API node, “Create” or “Update” does not support the settings “callerPolicy”, “executionOrder” and many more.

This means anytime we use this node, the “executionOrder” is set to v0, which in practice make this not unusable.

Documentation: API reference | n8n Docs

Could you please update this asap?

Many thanks

[Lesterpaintstheworld]

I figured it out!

Updated the workflow settings in PgSQL direcly.

Here’s my code:

[dkindlund]

Here’s another variation of the same thing:

How to set default “Error Workflow” for new workflows

I can’t believe this hasn’t been fixed yet. Regardless, here’s a workaround: Do you consistently forget to set a Default Error Workflow when creating new workflows? Then this helper workflow is for you! When activated, this helper workflow will: Scan ALL other workflows every 4 hours Make sure ALL workflows have a default error workflow set (based on what Workflow ID you provide) This helper will SKIP OVER any workflows that have the default_error:false tag set (make sure your default erro…

[Lester_Reynolds]

Hep @devs is there any news on this front ?

Calling POSTgresSQL is not a great solution at all…

n8n API UPDATE workflow with :

  "settings": {
    "callerPolicy": "any"
  }