gRPC Trigger

The gRPC trigger acts as a server to gRPC clients.

Note: You must run the preinstall script before running the gRPC trigger or activity binary.

Trigger Settings

Field Description
Trigger Settings
Port The port on which the trigger listens to requests. You can use any open port. This field can also be set using an app property.
Proto File

When creating a gRPC trigger, you can configure it by uploading an .proto file. To do this, either click on Browse and then select the .proto file from your local disk or click the Use app level spec toggle to select a spec uploaded on the SPECS tab. Once you select the file the other fields are populated as per the spec.

Note: The gRPC trigger and gRPC Activity do not support options in the .proto file. For more information, see the limitations when creating a .proto file in gRPC Activity.
Secure Connection By default, it is set to False. If you set this field to True, you can create a secure endpoint by providing CA Certificate, Server Certificate, and Server Key.
Note: If the secure connection is True, you have the option for mutual TLS. This field is optional.
Use Mutual TLS Set it to True to enable mutual authentication for a secure connection to the server. The default value is False.
CA Certificate

A PEM-encoded CA certificate.

Browse and select a Certificate Authority (CA) certificate that validates either the client's certificate or the server's certificate to establish a secure connection during the TLS handshake.

Alternatively, you can configure the app property using the Bind an Application Property toggle. Set the Base64-encoded value of the CA certificate to the corresponding app property.

Server Certificate

A PEM-encoded server certificate.

This certificate is used to authenticate the server to the client over TLS. Browse to select the server certificate.

Alternatively, you can configure the app property using the Bind an Application Property toggle. Set the Base64-encoded value of the server certificate to the corresponding app property.

Server Key

A PEM-encoded private key file. Browse and select the server key.

Alternatively, you can configure the app property using the Bind an Application Property toggle. Set the Base64-encoded value of the server key to the corresponding app property.

Handler Settings
Service Name Name of the service defined in the .proto file. You must create one gRPC trigger for any specific .proto file. Any subsequent gRPC triggers using the same .proto file can select the service and method they need from the dropdown list.
Method Name of the RPC method in the .proto file. Each method in the .proto file is represented by a separate flow and attached to the same gRPC trigger.

Map to Flow Inputs

You can map the trigger output to flow input on this tab. This tab displays fields from your selected method.

Map from Flow Outputs

You can map the flow output to the trigger reply on this tab.