Overview
This node acts as a JSON-RPC executor, designed to facilitate communication with services or APIs that use the JSON-RPC protocol. It is useful in scenarios where you need to send JSON-RPC requests and receive responses within an n8n workflow, enabling integration with systems that expose JSON-RPC endpoints. For example, it can be used to invoke remote procedures on blockchain nodes, custom backend services, or any API supporting JSON-RPC.
Properties
| Name | Meaning |
|---|---|
| Debug Mode | Whether to enable detailed logging of input and output data for troubleshooting purposes (true/false). |
Output
The node outputs a single field named response in its JSON output. This field contains the result of executing the JSON-RPC request via a proxied executor instance. The exact structure depends on the JSON-RPC service response but generally includes the data returned by the remote procedure call.
No binary data output is indicated.
Dependencies
- Requires an API authentication credential to connect to the JSON-RPC service.
- Uses internal proxy and executor modules to handle the JSON-RPC communication.
- No additional external dependencies are explicitly required beyond the configured API credential.
Troubleshooting
- If the node fails to execute, ensure the API credential is correctly configured and has access to the target JSON-RPC endpoint.
- Enabling "Debug Mode" can help reveal more detailed information about the request and response, aiding in diagnosing issues.
- Common errors may include connection failures, authentication errors, or invalid JSON-RPC method calls. Verify endpoint URL, credentials, and method parameters accordingly.
Links and References
- JSON-RPC Specification
- n8n documentation on Credentials and Custom Nodes