Overview
This node executes gRPC calls to any service defined in protobuf files. It allows users to specify connection settings, metadata headers, protobuf definitions, and select a gRPC service and method to invoke. The node sends a JSON request payload and supports options like timeout and response format. It is useful for integrating with gRPC APIs, enabling automation workflows to interact with microservices or backend systems using gRPC protocols.
Use Case Examples
- Calling a user management gRPC service to fetch user details by ID.
- Invoking a payment processing gRPC method with transaction data.
- Streaming data from a server using a gRPC server streaming method.
Properties
| Name | Meaning |
|---|---|
| Use Credentials | Whether to use saved credentials or define connection details manually. |
| Connection Settings | Host and TLS settings for the gRPC server connection, used when not using saved credentials. |
| Metadata | Custom metadata headers to send with the gRPC request, used when not using saved credentials. |
| Protobuf Definitions | Protobuf definition files to define the gRPC services and methods, used when not using saved credentials. |
| Service Name or ID | The gRPC service to call, selected from a list or specified by expression. |
| Method Name or ID | The method to invoke on the selected gRPC service, selected from a list or specified by expression. |
| Request Body | The JSON payload to send as the request to the gRPC method. |
| Options | Additional options for the request such as timeout and response format. |
Output
JSON
json- The response data from the gRPC call, either parsed JSON or raw data depending on the selected response format.
Dependencies
- Requires access to gRPC services defined by protobuf files.
- Optionally requires saved credentials for connection details and metadata.
Troubleshooting
- Error 'No protobuf definitions provided' occurs if no protobuf files are supplied; ensure protobuf files are configured either via credentials or manual input.
- Error 'No service selected' occurs if the service parameter is empty; select a valid gRPC service.
- Error 'No method selected' occurs if the method parameter is empty for any input item; select a valid method for each item.
- Invalid JSON in request body error occurs if the requestBody parameter is not valid JSON; ensure the request payload is correctly formatted JSON.
Links
- gRPC Official Documentation - Comprehensive guide and reference for gRPC protocol and usage.
- Protocol Buffers Documentation - Information about protobuf syntax and usage for defining gRPC services.