Generally, you have three options:
- Handle your ‘workflow’ programatically externally (e.g. PowerShell SDK, Python SDK…etc).
- Shift the workflow out to another more capable / centralised / enterprise-grade workflow engine (n8n or whatever else you have), instead of handling complex workflow in a ‘relatively’ limited and niche workflow engine of ISC.
- If you must handle it within the tenant of ISC, potentially this to handle value extraction: How to date transform in a workflow - #6 by David_Norris
With recent progress in vibe coding, one may say that the technical hurdle for options 1 and 2 are now lower than before. ISC workflow has its own set of limitations (e.g. nondeterministic out-of-order loop iteration, loop iteration limit unless you do recursive workflow…etc.)