Execute NodeJs
Infoveave Data Automation — Script Execution
Built-in activities not enough? Execute NodeJs runs your custom code in the workflow.
Standard no-code transformation activities cover the majority of data pipeline needs, but some logic is genuinely complex — custom authentication flows, proprietary calculation libraries, third-party npm integrations, or business-specific algorithms. Execute NodeJs slots your custom Node.js application into the Infoveave workflow canvas as a native step. The script receives workflow data and files, executes in a configured directory with full npm package support, and returns its output files to the next activity — making Infoveave the orchestrator for both no-code and code-based pipeline steps.
What Execute NodeJs does
Execute any Node.js script or application as a workflow step in Infoveave. Pass data between workflow activities and your Node.js code, leverage npm packages, and automate complex business logic that goes beyond built-in transformation activities.
When to use Execute NodeJs
- Your transformation or integration logic requires custom JavaScript/Node.js code that cannot be expressed with built-in activities
- You have an existing Node.js application or module that processes data and you want to incorporate it into an automated pipeline
- You need access to a specific npm package or third-party SDK not covered by native Infoveave activities
- You are implementing complex calculation logic, proprietary algorithms, or multi-step API interactions that require custom code
When to avoid it
- Your data transformation can be handled by built-in transformation activities — use the Transformations library for cleaner, more maintainable pipelines
- You need to execute SQL queries — use Execute Query instead
- You need to run Python scripts — use the Python script execution activity or a custom transformation
- You need to run Java-based ETL jobs — use Execute Talend
Where it fits in your Infoveave automation
Execute NodeJs is one step inside a multi-step Infoveave workflow. Chain it with other activities — no code, no manual hand-offs.
Build this workflow visually in Infoveave Data Automation — drag, connect, and schedule with no infrastructure setup.
How teams use Execute NodeJs
Real scenarios where this transformation saves hours of manual work.
API Authentication and Data Fetch
A data pipeline needs to authenticate to a third-party API using a non-standard OAuth flow that the Execute API activity does not support. A Node.js script handles the authentication handshake, calls the API, and writes the response to a JSON file. Execute NodeJs runs the script inside the workflow, and the output file is passed to Read CSV Files for downstream processing.
Custom Calculation Engine
A risk management team runs proprietary pricing calculations implemented in a Node.js library. Execute NodeJs runs the library against each day's market data (passed as a file from a previous Read CSV step), executes the pricing model, and writes the results file. Downstream activities load the priced records into the risk database.
Device Protocol Conversion
Shop floor devices produce data in a proprietary binary format. A Node.js parser converts the binary files to CSV. Execute NodeJs runs the parser against files downloaded from an SFTP connection, making the converted CSV output available to downstream Read CSV Files and transformation activities.
See Execute NodeJs in action
Input data (left) is transformed using the configuration below. The output table (right) is ready for dashboards or downstream steps.
index.js/home/infoveave/scripts/my-node-app/home/infoveave/scripts/my-node-appnode index.js/home/infoveave/scripts/my-node-app/output120 (seconds)5 (seconds)Input Data
| (files from previous workflow activity) |
Output Data
| (files produced by the Node.js script in the Output Directory) |
Configuration
Key fields to configure in the Infoveave workflow builder. Full reference available in the documentation.
File
The entry point script file for the Node.js application — typically 'index.js' or the main module file. Must be present in the Working Path directory.
Base Folder
The root folder on the Infoveave server where the Node.js application is installed. All file paths used by the script are resolved relative to this directory.
Working Path
The directory from which the command is executed. Usually the same as Base Folder, but can be a subdirectory if the application is structured with multiple modules.
Command
The shell command to execute the Node.js application — typically 'node index.js'. Can include command-line arguments to pass configuration or input file paths to the script.
Output Directory
The directory where the Node.js script writes its output files. Infoveave monitors this directory after execution and makes the files available to downstream workflow activities.
Max Execute Time
Maximum time in seconds that the activity waits for the script to complete before timing out. Set this to exceed the expected runtime of your script — for example, 120 seconds for a complex calculation that typically takes 60–90 seconds.
Frequently asked questions
Everything you need to know about Execute NodeJs in Infoveave.
Also in Script Execution — and what runs before & after
Transformations in the same family as Execute NodeJs, often chained together in the same Infoveave workflow.
Part of Infoveave Data Automation
80+ transformations. Zero manual steps.
Execute NodeJs is one of over 80 transformation activities available inside Infoveave workflows. Chain transformations together — no code, no exports, no waiting for IT.
Ready to see Infoveave in action?
