# Conclusion

This Guide has shown us how we might configure a poller integration - polling data from the table API of a Personal Developer Instance (PDI) and then configure the relevant message to process and respond to that data. As such, we created the following records:

* Connection Variables
* Poll Processor
* Poller
* Messages
* Fields

We also created & used a specific Assignment group in the remote instance (PDI), in order to facilitate the following:

* Ticket Identification

In testing our integration, we created some incidents in the remote instance which were non-bonded and assigned to a range of groups. We then polled for newly created tickets. We successfully proved that we were only querying non-bonded records which were assigned to a specific group, pulling back records created in the remote instance since the last update time, only retrieving a select number of fields and that the returned requests were looped through, generating transactions for each non-bonded ticket.

By Using the **Unifi** integration platform, we have discovered that building and testing our integration is simpler and more efficient, saving both time and money. Our hope is that this Guide has been a valuable aid to you in that process.

For further information please see our [technical documentation](https://docs.sharelogic.com/unifi/4.1/readme).

If you have any feedback or questions, please contact us via our website [contact form](https://sharelogic.com/contact).