Overview
This node allows you to run any other n8n node dynamically within your workflow, but with a specified set of credentials. It is useful when you want to execute a particular node's logic using different credentials than those configured in the main workflow or when you want to isolate credential usage for security or organizational reasons.
Common scenarios include:
- Running an API call node with a different user's API key without changing the main workflow credentials.
- Testing or executing a node with temporary or alternate credentials.
- Dynamically injecting and running nodes that require specific authentication at runtime.
For example, you can pass the JSON definition of an HTTP Request node configured with certain credentials, and this node will execute it using the provided credentials ID, returning the results as if the node ran normally.
Properties
| Name | Meaning |
|---|---|
| Credentials ID | The ID of the credentials to use when running the injected node. |
| Run Per Item | Whether to run the injected node separately for each input item (true) or once for all (false). |
| Node To Execute | The JSON representation of the node to execute, including its parameters and configuration. |
Output
The output is the combined result of executing the injected node(s):
- The
jsonfield contains the data returned by the executed node(s). - If
Run Per Itemis enabled, the output corresponds to each input item processed individually. - Metadata about sub-execution is included, such as execution IDs and workflow IDs, allowing traceability of the nested execution.
- In case of errors during execution, error information is attached to the corresponding output item if "Continue On Fail" is enabled.
No binary data output is explicitly handled by this node; it simply passes through whatever the executed node returns.
Dependencies
- Requires an existing workflow environment where this node runs.
- Needs a valid credentials ID that matches credentials stored in n8n for the node being executed.
- Uses internal n8n workflow execution APIs to run the injected node as a sub-workflow.
- No external services are directly required by this node itself, but the executed node may depend on external APIs or services.
Troubleshooting
Error: "There are no credentials in the node that is entered."
This occurs if the injected node JSON does not contain any credentials property. Ensure the node JSON includes credentials configuration.Parsing Errors on Node JSON
TheNode To Executeproperty must be valid JSON representing a single node or nodes array. Invalid JSON will cause parsing failures.Credential ID Mismatch
If the provided credentials ID does not correspond to valid credentials for the node, execution will fail. Verify the credentials exist and are correct.Execution Failures
If the executed node fails, the error will propagate unless "Continue On Fail" is enabled, in which case the error is attached to the output item.Performance Considerations
Running per item (Run Per Item = true) can be slower due to multiple executions. Use only when necessary.
Links and References
- n8n Documentation - Creating Custom Nodes
- n8n Workflow Execution Concepts
- JSON Schema for n8n Nodes (for understanding node JSON structure)