Skip to Content

gRPC Action

The grpc action calls a gRPC method. The service definition is resolved through server reflection, so no .proto file is needed at run time.

Basic Syntax

- name: Get a user uses: grpc with: addr: "grpc.example.com:443" service: "user.v1.UserService" method: "GetUser" tls: true body: | {"id": "123"} test: res.status_code == "OK"

Parameters

ParameterTypeRequiredDefaultDescription
addrStringYes-Host and port of the gRPC server
serviceStringYes-Fully qualified service name
methodStringYes-Method name
bodyStringNo""Request message as JSON
metadataObjectNo{}Request metadata (the gRPC equivalent of headers)
timeoutStringNo-Request timeout, such as "10s"
tlsBooleanNofalseUse TLS
insecureBooleanNofalseSkip certificate verification
cert_fileStringNo-Client certificate for mutual TLS
key_fileStringNo-Client key for mutual TLS
ca_fileStringNo-CA certificate used to verify the server

Response Object

FieldTypeDescription
res.bodyStringResponse message as JSON
res.status_codeStringgRPC status code, such as OK or NOT_FOUND
res.status_messageStringStatus message
res.metadataObjectResponse metadata
rtStringRound-trip time
reqObjectThe request as it was sent
Updated at