Stay organized with collections
Save and categorize content based on your preferences.
Solace trigger
The Solace trigger is a Connector Event trigger that lets you invoke an integration based on the Solace events that you've subscribed to in your Solace connection.
Before you begin
If you plan to create or configure a new connection for the Solace trigger, make sure that you have the following IAM role on the project:
Connector Admin (roles/connectors.admin)
For information about granting roles, see Manage access.
Grant the following IAM roles to the service account that you want to use for the Solace trigger:
The Integrations List page appears listing all the integrations available in the Google Cloud project.
Select an existing integration or click Create integration to create a new one.
If you are creating a new integration:
Enter a name and description in the Create Integration pane.
Select a region for the integration.
Select a service account for the integration. You can change or update the service account details of an integration any time from the infoIntegration summary pane in the integration toolbar.
Click Create.
The newly created integration opens in the integration editor.
In the integration editor navigation bar, click Triggers to view the list of available triggers.
Click and place the Solace trigger element in the integration editor.
To configure the Solace trigger, you can either use an existing Solace connection available in Integration Connectors, or create a new Solace connection using the inline connection creation option.
Configure Solace trigger using an existing connection
You can configure the Solace trigger using an existing Solace connection in Integration Connectors. Note that the Solace trigger is an Connector Event trigger, therefore you can only use a Solace connection with event subscription enabled to configure the trigger.
To configure a Solace trigger using an existing Solace connection, perform the following steps:
Click the Solace trigger element in the integration editor to open the trigger configuration pane.
Click Configure trigger.
Provide the following configuration details in the Connector Event Trigger Editor page:
Region: Select the region of your Solace connection.
Connection: Select the Solace connection that you want to use.
Application Integration only displays those Solace connections that are active and have an event subscription enabled.
Select Queue or Topic as the JMS Source Type.
If you select Queue, provide the Solace queue name in the JMS Source Name column.
If you select Topic, provide the Solace topic name in the JMS Source Name column.
Service Account: Select a service account with the required IAM roles for the Solace trigger.
Click Done to complete the trigger configuration and close the page.
Configure Solace trigger using a new connection
To configure the Solace trigger using a new Solace connection, perform the following steps:
Click the Solace trigger element in the integration editor to open the trigger configuration pane.
Click Configure trigger.
Skip the Region field.
Click Connection and select the Create Connection option from the drop-down menu.
Complete the following steps in the Create Connection pane:
In the Location step, choose the location for the new Solace connection:
Region: Select a location from the drop-down list.
For the list of all the supported regions, see Locations.
Click Next.
In the Connection Details section, complete the following:
Connector: Select Solace from the drop down list of available Connectors.
Connector version: Select the Connector version from the drop down list of available versions.
In the Connection Name field, enter a name for the Connection instance.
Connection names must meet the following criteria:
Connection names can use letters, numbers, or hyphens.
Letters must be lower-case.
Connection names must begin with a letter and end with a letter or number.
Connection names cannot exceed 49 characters.
For connectors that support event subscription, the connection names cannot begin with the "goog" prefix.
Optionally, enter a Description for the connection instance.
Service Account: Select a service account that has the required roles.
To use the connection for event subscriptions, select Enable event subscription. Selecting
this option, enables the event subscription with actions.
Message VPN: The Solace Pub/Sub+ message router Message VPN that you want to connect to. A connection is specific to a Message VPN. If you have many message VPN, you must create a separate
connection for each message VPN.
Default Queue Name: The name of the default queue, may be overridden when executing action.
Default Topic Name: The name of the topic to connect to.
(Optional) To use SSL, select Enable SSL and specify the SSL configuration details.
Select a trust store type. You can specify Public, Private, or Insecure Connection.
Select the certificates based on your trust store selection. For example, if you select Private, specify a custom trust store.
If you are using mTLS, select the key store certificates in the Key Store section.
Optionally, select the TLS version.
Enter the supported cipher suite. Enter multiple cipher suites, as
comma separated values. For more information, see Supported cipher suites.
(Optional) Configure the Connection node settings.
Minimum number of nodes: Enter the minimum number of connection nodes.
Maximum number of nodes: Enter the maximum number of connection nodes.
A node is a unit (or replica) of a connection that processes transactions.
More nodes are required to process more transactions for a connection and conversely,
fewer nodes are required to process fewer transactions.
To understand how the nodes affect your connector pricing, see
Pricing for connection nodes. If you don't enter any values, by default
the minimum nodes are set to 2 (for better availability) and the maximum nodes are set to 50.
Optionally, click + Add label to add a label to the Connection in the form of a key/value pair.
Click Next.
In the Destinations section, enter details of the remote host (backend system) you want to connect to.
Destination Type: Select a Destination Type.
To specify the destination hostname or IP address, select Host address and
enter the address in the Host 1 field.
To establish a private connection, select Host Address and add the endpoint attachment created for the SAP Gateway using the HTTPS protocol.
If you want to establish a public connection to your backend systems with additional security, you can
consider configuring static outbound
IP addresses for your connections, and then configure
your firewall rules to allowlist only the specific static IP addresses.
Click Next.
In the Authentication section, enter the authentication details.
Select an Authentication type and enter the relevant details.
The following authentication types are supported by the Solace connection:
In the Event Subscription Details section, configure the event related details.
Enter the dead-letter configuration. If you configure dead-letter, the connection writes
the unprocessed events to the specified Pub/Sub topic. Enter the following details:
Dead-letter project ID: The Google Cloud project ID where you have configured the dead-letter Pub/Sub topic.
Dead-letter topic: The Pub/Sub topic where you want to write the details of the unprocessed event.
Review: Review your connection and authentication details.
Click Create.
Trigger output
The Solace trigger takes a couple of minutes to complete the event subscription configuration. You can view the status
of your event subscription in the trigger configuration pane under Event Subscription details.
The Solace trigger indicates the status of an event subscription using the following states:
restart_alt
Creating: Indicates that the trigger is subscribing to the event subscription.
check_circle
Active: Indicates that the trigger is successfully subscribed to an event subscription.
error
Error: Indicates that the there is an issue with the configured event subscription.
In addition to the event subscription status, the Event Subscription details section also
displays other details such as connection region, connection name, and event subscription name.
Trigger output variable
For each event, the Solace trigger generates a ConnectorEventPayload
output variable (in JSON format) which you can use in your downstream tasks. The output
variable will have the payload from your Solace event. For example:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2026-06-09 UTC."],[],[]]