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.

3

Any updates regarding requested features? I have to use Postman for cases related to gRPC.

4

Hi Damir,

  1. Are you looking to predefine different payloads and then select them as messages to send out?

For points 2 and 3, you can update to the latest version – I’ve verified that comments and variable substitution (like {{request_id}}) work correctly there.

515a33eb-ebd1-445f-bd60-a021d785c689.jpeg
515a33eb-ebd1-445f-bd60-a021d785c689.jpeg1401×1241 96 KB

5

Yes, I’m looking for predefine collection of payloads which I can send out in the same opened stream.

6

Thank you for your feedback. We’ve logged this feature request and will notify you of any updates. For gRPC-related tasks, we recommend checking our documentation for current capabilities.