I'm creating a workflow that pulls (user submitted form) data from an api, and then performs some validation and transformation, then kicks off various other processes depending on the data. The script is also going to have to reach out to other services to determine some of its actions.
So for all the conditional logic of the transformations, I could obviously hardcode it all, but it will require (non-frequent) updating so I was thinking about some way to make all the transformation definitions/conditionals be separated. I can't think of a great way to do that though.
I'm back and forth with it just being "essentially code in a different spot" - but it would be nice if someone without pwsh experience could make additions/changes. (just nice, not required)
Is it just a fruitless effort, or is there some other data format that would fit this use case?
#Workflow Transformation Conditional Logic
3 messages · Page 1 of 1 (latest)
I mean, there are graphical workflow tools, like n8n and automatisch and of course, power automate (which is built-in as a desktop app on Windows 11) ...
You can call PowerShell as a node in n8n