Actions10
- Spot Actions
- Future Actions
- Custom Actions
Overview
This custom node allows users to execute predefined or custom functions by specifying a function name or ID along with parameters in JSON format. It is designed to provide flexibility for running user-defined logic or API calls dynamically within an n8n workflow.
Common scenarios include:
- Invoking specific custom functions that perform specialized data processing.
- Running dynamic code snippets or API interactions where the function and its parameters are determined at runtime.
- Integrating external services or complex logic without creating multiple static nodes.
For example, a user might select a custom function that fetches data from an external API and pass query parameters as JSON to tailor the request.
Properties
| Name | Meaning |
|---|---|
| Function Name or ID | Select a predefined custom function from a list or specify a function identifier using an expression. |
| Parameters | Provide input parameters for the selected custom function in JSON format. These parameters customize the function's behavior or API call. |
Output
The node outputs the result of executing the specified custom function. The output is available in the json field of the node's output data and contains the response or data returned by the function.
If the function returns binary data, it will be included accordingly, allowing workflows to handle files or media.
Dependencies
- Requires access to a set of custom functions registered in the environment (retrieved via a method named
getCustomFunctions). - No explicit external API keys or credentials are shown in the provided code snippet, but depending on the custom functions used, appropriate authentication may be required.
- The node depends on the bundled methods and properties defined in separate modules (
./methods,./actions/binance.properties,./actions/binance.execute), which manage loading options and execution logic.
Troubleshooting
- Invalid JSON in Parameters: If the JSON provided in the Parameters field is malformed, the node will likely throw a parsing error. Ensure valid JSON syntax.
- Function Not Found: Selecting a function name or ID that does not exist or is unavailable will cause execution failure. Verify the function list is up-to-date.
- Missing Required Credentials: Some custom functions may require API keys or tokens. Failure to provide these will result in authentication errors.
- Execution Errors in Custom Functions: Errors thrown inside the custom function will propagate. Review function implementation and input parameters for correctness.
Links and References
- n8n Expressions Documentation
- binance-api-node npm package (referenced in the Parameters description)