CUSTOM SCRIPT¶
Executes a user-supplied script (Python, MATLAB, PHP, or native executable) inline within a workflow node, passing arbitrary arguments and returning a vector output. Use this worker when a standard transformation does not exist and custom scripting logic is needed to process or generate data.
When to use¶
Classification: process.
Tagged: custom_script, exe, inline_code, matlab, php, process, python, scripting.
Inputs¶
| Label | ID | Type | Default | Required | Description |
|---|---|---|---|---|---|
| Type | type | string | count | Script language / runtime to use; choose one of ‘Python’, ‘Matlab’, ‘PHP’, or ‘EXE’ (native executable) — defaults to ‘count’ (no runtime) when left unset. | |
| Code Value | code_value | text | — | Full source code (or path to executable) to run; enter the complete script body as a text string, or supply the file path when type is ‘EXE’. | |
| Arguments | arguments | vector | — | Ordered list of arguments passed to the script at runtime; repeatable vector fields — add one entry per positional argument (e.g. input file paths, numeric parameters). |
Outputs¶
| Label | ID | Type | Description |
|---|---|---|---|
| custom_script_output_1 | custom_script_output_1 | vector | Vector result returned by the executed script; content and units depend entirely on the user-supplied code. |
Disciplines¶
- data.dataset.transform
- platform.workflow
Auto-generated from transformation schema. Worker id: custom_script. Schema hash: 71dae8f76cab. Hand-curated docs in workerexamples/ override this page when present.