Adding WFs/Scripts to Site Actions - Custom Configuration via NBI

[MarieKraus]

Hello,

Why isn't it possible to add more than one WF to the custom configuration via NBI?
It can be done manually, but since I'm planning to create a larger number of sites with predefined values, actions and WFs/Script using a NBI WF, it doesn't help. Also:

- It is not possible to add a script to Custom Configuration via NBI
- An existing WF/Script is deleted(replaced) when adding a WF via NBI

Why is this?
I cannot even help myself with a workaround WF because it would only work for one selected vendor. I have created a workflow to make a difference between VOSS and EXOS, so this WF will start another WF depending on the device family, but Im tied to the vendor.

Thank you for your time

[zayllee11 · Accepted solution]

You're right currently, the NBI API overwrites the existing custom configuration block when adding a WF or script, as it doesn’t support appending multiple WFs/scripts. Also, script objects aren’t exposed via NBI in the same way as workflows, which limits automation.

A possible workaround (though limited) is chaining logic within a single WF or using a parent WF that delegates by device type, as you've done. Hopefully, future updates will support better multi-WF handling and vendor-agnostic logic via NBI.