> For the complete documentation index, see [llms.txt](https://docs.sharelogic.com/unifi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sharelogic.com/unifi/integration-guides/servicenow-table-api/incident-update-poller-guide/polling/poller.md).

# Poller

A Poller is a configuration record which defines the frequency of polling and which logic to use.

A Poller is a configuration record which defines the frequency of polling and which logic to use (the logic itself is defined in the Poll Processor). Each time it is run, it creates a corresponding Poll Request record.

## New Poller

Click the **'Pollers' icon** & then **New**.

The fields to be configured for the New Poller modal are as follows:

| Field         | Description                                                   | Value               |
| ------------- | ------------------------------------------------------------- | ------------------- |
| Name\*        | The name of your Poller.                                      | \<Your Name>        |
| Description   | A description of what this Poller is for and/or how it works. | \<Your description> |
| Integration\* | The Integration the poller belongs to.                        | \<Your Integration> |

*\*These fields are mandatory, or automatically defaulted to true.*

*Your New Poller modal should look like this:*

![](https://3662067745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDk6VgKBXe6rYT8F9wuaY%2Fuploads%2F3ghBIAyuMTzSi6gd4qpE%2FPollerCreation.png?alt=media\&token=1339336d-3e82-4c00-a784-871e8288732f)

**Submit and view** to further configure the Poller.&#x20;

## Details

The fields to be configured for the Details form are as follows:

| Field                   | Description                                                                                                           | Value                  |
| ----------------------- | --------------------------------------------------------------------------------------------------------------------- | ---------------------- |
| Poll processor\*        | The Poll Processor to use when running this Poller.                                                                   | \<Your Poll Processor> |
| Attach response payload | Attaches the response from a successful poll to the Poll Request record. Only really required when debugging pollers. | True                   |

*Your Details form should look like this:*

<figure><img src="https://3662067745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDk6VgKBXe6rYT8F9wuaY%2Fuploads%2F2qY9tjvkfe6QWXo2YYA2%2FPollerDetails.png?alt=media&amp;token=9a910b32-e595-4501-8642-c05fb67d04b4" alt=""><figcaption></figcaption></figure>

Navigate to **Scheduling**.

## Scheduling

The fields to be configured for the Scheduling form are as follows:

| Field             | Description                                         | Value                                               |
| ----------------- | --------------------------------------------------- | --------------------------------------------------- |
| Run               | The frequency at which the Poller should run.       | 'Periodically'                                      |
| Run as            | Poller will run with credentials of specified user. | Defaults to: \<Your Inbound user> (from Connection) |
| Repeat interval\* | The interval at which the Poller should repeat.     | '05' (Minutes)                                      |
| Starting          | The date/time the Poller should start.              | \<Your Start date/time>                             |

*\*This field is mandatory.*

*Your Scheduling form should look like this, if these fields are not visable ensure the poller is enabled:*

![](https://3662067745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDk6VgKBXe6rYT8F9wuaY%2Fuploads%2Fn2LVRBvazzHvbhGrZeg4%2FPollerSchedule.png?alt=media\&token=ba40d1fe-17be-47ac-b3fb-5ea0f0f0c5ff)

**Save** the Poller.

In order to process the inbound Requests, we next need to configure our **Inbound Message**.