Input - HTTP Poll

HTTP Poll will periodically initiante a HTTP request to the given URL, and process the result.
Example configuration:


https://slite.com/api/files/Ba86kSsRf/image.png?apiToken=eyJhbGciOiJIUzI1NiIsImtpZCI6IjIwMjMtMDUtMDQifQ.eyJzY29wZSI6Im5vdGUtZXhwb3J0IiwibmlkIjoiVm1BUnVoZU1qIiwiaWF0IjoxNzQ2ODMxNzEwLCJpc3MiOiJodHRwczovL3NsaXRlLmNvbSIsImp0aSI6Im5zQ0JLY0xqMl9VT3k4IiwiZXhwIjoxNzQ5NDIzNzEwfQ.N-VfKFw_w10yE-iruEfrOvyR5ZRXm40V2ZBppxrDF24


https://slite.com/api/files/XLK5_kUMI/image.png?apiToken=eyJhbGciOiJIUzI1NiIsImtpZCI6IjIwMjMtMDUtMDQifQ.eyJzY29wZSI6Im5vdGUtZXhwb3J0IiwibmlkIjoiVm1BUnVoZU1qIiwiaWF0IjoxNzQ2ODMxNzEwLCJpc3MiOiJodHRwczovL3NsaXRlLmNvbSIsImp0aSI6Im5zQ0JLY0xqMl9VT3k4IiwiZXhwIjoxNzQ5NDIzNzEwfQ.N-VfKFw_w10yE-iruEfrOvyR5ZRXm40V2ZBppxrDF24
Where frequency is in seconds (5 minutes in our example).
We are not ignoring errors, so we don't progress with failed authentication.
The API is waiting for a POST request, we could choose GET, PUT, PATCH or other methods.
URL, or part of the URL could come from environment configuration,
like =<.api_url>=/auth so we could reuse the code with staging, UAT and live systems.
User, Password and Bearer Token are optional, can be provided with =<.api_user>= environment template tags. It could be hardcoded as well, but when sharing the interface as a recipe this will be a security issue.
The Request Body is available for POST, PATCH and PUT request methods.
We have added a Content-Type header, values also can be templated from environment.
JSON parser has been set, this will parse the response and error on any format issues.