Description
The Execute Node JS activity allows you to run a custom Node.js script or application as part of a workflow. You can specify the script file, working directory, command, output location, and control execution timeout.
Use this activity to:
- Run backend automation written in Node.js
- Process data, files, or external API responses using custom JavaScript logic
- Integrate with CLI tools or third-party Node packages
Use Case
Useful when workflows require backend processing logic like JSON manipulation, calling APIs, or custom data transformation that is best handled using Node.js.
| Type | Description |
|---|
| Files | Project or script files required for execution |
Output
| Type | Format | Description |
|---|
| Execution Data | Table | Output from the executed command |
Configuration Fields
| Field Name | Description |
|---|
| File | Path to the Node.js script or main file to execute. |
| Base Folder | The folder where the script/project is located. |
| Working Path | Optional working directory path during execution. |
| Command | Node.js command to execute the script (e.g., node index.js). |
| Output Directory | Folder path to save execution output files. |
| Max Execute Time | Maximum time (in seconds) to allow script execution before timeout. |
| Refresh Interval | Interval (in seconds) to poll for execution status. |
Not applicable — input files are provided through the Files field.
Sample Configuration
| Field | Value |
|---|
| File | index.js |
| Base Folder | /user-scripts/ |
| Command | node index.js |
| Output Directory | /output/ |
| Max Execute Time | 60 |
| Refresh Interval | 5 |
Sample Output
| CommandOutput |
|---|
| Hello World! |
