The Listener trigger listens for events in the external application and triggers automation in real-time. This trigger requires a listener URL that serves as the endpoint to which the external application sends the webhook event details.

Overview

The Listener trigger enables you to create triggers for applications that support webhooks. You can configure the Listener trigger to receive the incoming event notifications and start the subsequent automation based on the notification. You must create a listener URL for the Listener trigger, which acts as the endpoint for receiving the notification. The platform hardcodes this URL and you cannot edit it after creation. Create the Listener URL in the Event Triggers page.

The Listener trigger provides options to add authentication headers and signature schemes based on the application for which you are configuring the trigger. You must set the authentication header in the webhook settings of the application and add the same headers in Authentication headers. You can also set a security scheme for validating the incoming payload. Set the X-Signature header with the key on the application side and add the same parameter and key in the Signature scheme field. Currently, Listener trigger supports HMA-SHA256 signature only.

Settings

The following settings are available in Listener trigger:

Screenshot of Listener web trigger settings panel

Listener
Choose an appropriate listener URL for the trigger from the drop-down list.Listener trigger. You can use the Refresh button to refresh the drop-down list.
Authentication headers
Enter the authentication headers that you set on the application side. The authentication headers ensure that the webhooks are secure. The headers use the name-value format. Ensure that you enter the exact name and values that you configure in the application settings. This field is optional.
Signature scheme
Select an appropriate signature scheme to validate the incoming data. The signature scheme verifies the data origin and integrity, providing an additional security layer. The signature scheme consists of a key identifier and a header name.
Secret key
Enter the secret key used to identify the signature. Use the Credential option to choose a key that is available in the Credential Vault. Alternatively, enter the key directly in the Insecure string option.
Signature header name
Enter the header name for the secret key.
Response
Select a record variable to save the trigger response data. The automation saves the trigger response data in a key-value pair format. After you execute the bot, go to Audit log page and select the Bot run by trigger event to view the response data.