A workflow API task calling an action discovered from the browser's network log fails with a "does not have the expected parameters" error, even though the same parameters worked in the direct UI call.

All FAQ questions / Workflows and automation

Answer

Check whether that action is a bound action on a nested sub-entity rather than a standalone, parameterless action — a bound action like this typically needs the workflow to read the specific nested entity record first, then call the action as an immediate follow-on task against that read result, rather than calling it directly with the parameters copied from the network trace.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Workflows and automation questions