Greetings, Poly API Community! I’m excited to share a sneak peek of a demo that really underlines the strength and flexibility of our platform from an operational perspective.
The focus here is on our native out-of-the box event handler functions, which empowers you to react to changes in variables and handle errors seamlessly when Poly functions experience them (either due to the function or underlying APIs). Here are a few key points I’d like to share about this feature:
- Customizable Listeners: Our platform allows you to write your own listeners, which can be as specific or as broad as you need. You could zero in on a particular client/function/error condition, or span across all errors within a tenant.
- Separate Processes: These listeners function as independent processes, unobtrusively tapping into the event stream from Poly and do not add load to runtime servers.
- Versatile Actions: Here’s where it gets even more interesting – you can take actions based on these events using Poly functions, HTTP calls, or any custom logic you prefer. You have the FULL power of coding in your native language.
- Numerous Use Cases: You can use these listeners to raise alerts, create tickets, log data, generate analytics, automate processes, and much more. The possibilities are virtually endless!
In the demo, we showcase how these features can be used to generate alerts, perform automated testing, revert a key, and even employ AI to craft a detailed description about an error before dispatching it.
Our aim with Poly is to set the bar high and become the gold standard for integration and automation. This means also being extremely easy to integrate and automate. For this we leveraged a modern event based architecture.
Take a look at the demo below – I’m certain you’ll find it both intriguing and useful. As always, your feedback and ideas are most welcome!
Let’s continue leveraging Poly’s capabilities to make the most of our tech-driven world.