Toggl is a time tracking service: https://toggl.com/
@stvad what is the use case you are looking to do exactly?
Ultimately replicating setup described here: https://medium.com/@stvad/tk-time-pressure-c94cd4cf5dfb
In more unified/coherent fashion
For that the Toggl integration should provide a way to react to the new time entries.
@stvad Thanks for clarifying. I have a couple of integration to finish and then will check it out.
Awesome, thank you @RicardoE105!
@RicardoE105 yeah. As a food for thought - I believe there are more services out there that provide an API for querying things then services that provide webhooks. So you probably eventually would want to implement nodes that do the polling anyway.
Yes, I agree. At some point, we will probably not get around polling. Like you said do some services sadly not offer webhooks. Not sure though if n8n should provide some abstraction layer for it or if the nodes should simply implement it themself with an interval/cron.
Here a previous discussion about polling:
As you mention in one of the replies there - getting a stream of events from polling without duplicates and without skipping the events reliably is non-trivial, so some abstraction layer/support from n8n would come in handy IMO