The Poller trigger periodically checks the data source for updates. After you configure it, Poller checks for new data periodically using the polling URL of a data source. The Poller is ideal for use cases where real-time updates are unavailable or when the frequency of updates is low.

Overview

The Poller operates on the concept of polling, where the trigger periodically sends requests to the polling URL for new data. You can configure the Poller to receive the incoming event notifications and start the subsequent automation based on the notification. The poller URL of the application serves as the endpoint that the trigger polls for new events.

You can configure the Poller for a GET call or PUSH call. You must add the header parameter, query parameter, context management details, and JSON filter when configuring Poller. The PUSH option includes a provision to add a request body. You can use this option to send data to the poller URL that requires additional data for the events.

Settings

The following settings are available in Listener trigger:

Settings panel of Poller

Name
Specify a name for the Poller
Polling URL
Specify the polling URL of the application.
Request type
Select the API request type. Poller supports GET and POST methods.
  • GET - You can use the GET method to fetch the event details.
  • POST - You can use the POST method to limit the response data. The POST method has a provision to add a request body. This option acts as a filter to limit the response data.
Request body
Enter the request body for the POST method. You can add the request body in formats such as TXT, JSON, XML, and HTML.
Polling interval
Set the frequency for polling the URL for new information. You can set the interval in Minutes, Hour, or Day. The minimum limit for the interval is 5 minutes.
Authentication Mode
Specify the authentication mode for the trigger. You can choose No Authentication or OAuth2 - Control Room managed.
Connection
Use the Pick button to choose an existing OAuth connection as the authentication mode. Ensure that the connection is set up and active.
Add Header
Specify the appropriate header for the request. Enable the check box and click Add header to open the Item modal. Enter the header name and values in the Item modal.
Add Query parameter
Specify the appropriate query parameter for the request. Enable the check box and click Add header to open the Item modal. Enter the header name and values in the Item modal.
Context management
Specify the context management for the query parameters that are dynamic. For example, if you want to set a poller configuration for status change, the context management setting enables you to define that the query parameter for status is dynamic and updates after each poller interval.
Json filter
Specify a filter for response data. This setting allows you to filter the data as per your requirements. For example, if the JSON data contains records with multiple lengths such as 1, 5, 10, 25, and 30, you can define the JSON filter to as record.length>10, this filter discards the records with a length less than 10.
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 the Audit log page and select the Bot run by trigger event to view the response data.