Collection of message payloads for gRPC streams

Feature Request
1

A gRPC stream can deliver messages with several payload variants:

message ServerMessage {
  string request_id = 1
  oneof payload {
    ErrorRes error = 2;
    MessageData data = 3;
    ChangeEvent change_event = 4;
  }
}

At the moment, you can’t (1) maintain a reusable set of predefined payloads or (2) filter incoming messages by payload type.

Suggested enhancements:

  1. Allow a collection of predefined payloads for gRPC streams (like requests in HTTP endpoints).
  2. Enable comments inside message payloads (currently unsupported).
  3. Support dynamic variables such as {{request_id}} within payloads (exists but not working).
2

Thank you for your valuable feedback! I’ll share this with our team.