Run JavaScript in a local sandbox or a Docker or Podman container.
Usage and specifics
Sandbox mode runs JavaScript locally with a timeout, allowed hosts and selected secret credentials. Docker mode uses source and executionTarget. A sandbox does not provide all container capabilities.
Technical type : code. Runtime : nodulz.
Credentials and prerequisites
This node defines no dedicated external credential. Remote sources or execution targets may still need their own access credentials.
See the credentials guide if a remote source or execution target requires access.
Parameters
Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.
Each mode keeps its own script and settings. The sandbox runs a function body or a run(context) module, with network access limited to allowed hosts. Container or cloud runs a module exporting run(context) through the selected provider: local Docker/Podman, an SSH server, a managed container or a cloud function (such as Lambda). Dependencies, files and network access depend on the provider runtime; sandbox host restrictions do not apply.
dependencies Dependencies
Public npm packages via esm.sh, one per line with an exact version (e.g. [email protected]). Import the package name or use await import(). Only compatible JavaScript modules are available: no native addons, files or Node APIs. The initial download counts toward the timeout; sources are then cached.
timeoutMs Timeout
Past this delay the node fails, including during a fetch or a sleep.
allowedHosts Hosts allowed for fetch
One per line: api.example.com, *.example.com for subdomains, or * for any public host. Empty: fetch is disabled. Private and internal addresses are always refused.
secretCredentialIds Secrets
Secrets connections whose variables are readable in secrets and process.env. Their values are masked in logs.
Initial configuration
Initial catalog configuration example, to adapt before running. Keep secrets in credentials.
Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.
Run JavaScript in a local sandbox or a Docker or Podman container.
Usage and specifics
Sandbox mode runs JavaScript locally with a timeout, allowed hosts and selected secret credentials. Docker mode uses source and executionTarget. A sandbox does not provide all container capabilities.
Technical type :
code. Runtime :nodulz.Credentials and prerequisites
This node defines no dedicated external credential. Remote sources or execution targets may still need their own access credentials.
See the credentials guide if a remote source or execution target requires access.
Parameters
Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.
filesrecorddirectoriesarraydependenciesarray[]libraryIdsarrayexecutionModeliteral"sandbox"sandbox,dockercodestring"const name = input.name ?? \"world\";\nreturn { message:Hello ${name}, nodeKeys: Object.keys(nodes) };"timeoutMsnumber10000allowedHostsarray[]secretCredentialIdsarray[]sourceunionsource.filesrecordsource.directoriesarraysource.kindliteralinline,git,workspacesource.scriptstringsource.dependenciesarraysource.repostringsource.branchstring"main"source.scriptPathstringsource.credentialIdstringsource.installRootstringsource.installCommandstringsource.workingDirstringimagestringworkspaceSourceunionworkspaceSource.kindliteralupstream,nodeworkspaceSource.keystringexecutionTargetunion{"kind":"host"}executionTarget.kindliteral"host"aws_ecs,aws_lambda,gcp_job,gcp_function,azure_container,azure_function,scaleway_job,scaleway_function,scaleway_container,digitalocean_function,host,remote_server,kube,swarmexecutionTarget.credentialIdstringexecutionTarget.storageCredentialIdstringexecutionTarget.bucketstringexecutionTarget.regionstringfr-par,nl-ams,pl-waw; max 64executionTarget.clusterstringexecutionTarget.taskDefinitionstringexecutionTarget.containerNamestringexecutionTarget.subnetsarrayexecutionTarget.securityGroupsarray[]executionTarget.assignPublicIpbooleanfalseexecutionTarget.functionNamestringexecutionTarget.projectstringexecutionTarget.jobNamestringexecutionTarget.endpointstringexecutionTarget.subscriptionIdstringexecutionTarget.resourceGroupstringexecutionTarget.functionAppstringexecutionTarget.jobIdstringexecutionTarget.functionIdstringexecutionTarget.containerIdstringexecutionTarget.namespaceIdstringexecutionTarget.serverIdstringexecutionTarget.providerenumaws,gcp,scaleway,ovh,azure,digitalocean,hetznerexecutionTarget.clusterIdstringexecutionTarget.namespacestringConfiguration help
executionModeExecution mode
dependenciesDependencies
timeoutMsTimeout
allowedHostsHosts allowed for fetch
secretCredentialIdsSecrets
Initial configuration
Initial catalog configuration example, to adapt before running. Keep secrets in credentials.
{ "executionMode": "sandbox", "code": "const name = input.name ?? \"world\";\nreturn { message: `Hello ${name}`, nodeKeys: Object.keys(nodes) };", "timeoutMs": 10000, "allowedHosts": [], "secretCredentialIds": [] }Verification
Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.
See also : Expressions and data, Executions, Node catalog.