For a quick example, imagine I have N resources. I could set up each of them to have their own triggers, which would result in N API calls per poll.
But I have an endpoint which I can poll, which gives me updates on all of these resources in a single call. For example, if I GET /user/history it gives me a list of changed/added resources, and their resource type.
I think it would be a complete waste to have each resource do its own polling to the exact same url, when 1 call would be enough. I know webhooks would be the best solution, but unfortunately I don't manage the API, and they do not have support for webhooks. What I would like to do, is to define one procedure/trigger, which in turn could run other triggers. Say I have a hidden trigger called: fetchUpdates which Zapier could use to poll every x minutes, but if the user had multiple triggers for different resources, it would not start making a lot of API calls. With this I could cut API traffic down by a large factor.
The only alternative I really see at this moment, is to do the polling myself on my own resources, and use that to send a webhook to Zapier. However this would waste a lot of my resources, and don't want to have to do that. Is there any way to implement this on Zapier?
Best answer by matthewView original