Integromat polling vs webhooks
Polling is a bad option when it comes to Integromat scenarios.
Polling means repeatedly sending HTTP requests to some API to check if something has changed in the state of the resource that the API server manages (i.e. REST).
Besides overloading the network with too much traffic (in and out of the querying app), there is one bad side effect when it comes to Integromat.
In Integromat’s scenario, every operation is taking into account when it comes to your quota. For example, Integromat’s free plan includes 1000 operations in a month.
Lets say that you have a scenario with 5 operations and you define a polling trigger for this scenario that runs every 5 minutes, that means 288 times a day.
As a result , after 3.47 days, your quota will be empty and all your 1000 operation will be wasted on ONE scenario, (in reality it’ll be even worse than that because if you have other scenarios running, your quota will be empty much sooner than that).
If you put a filter after the first operation, and the filter will check every incoming notification to Integromat’s scenario then stop the next operations due to some condition not fulfilled, it will NOT help, why ?
Because Integromat counts ALL of the operations, after an invocation of a scenario, even if ONLY one operation is actually executing.
(as opposed to Zapier that counts ONLY actions that are actually executing).
So, as a lesson from that, the solution is to find a way to use a webhook i.e. incoming HTTP notification from the API server
that’ll notify your app (in our context the app=Integromat) that something has changed in the state of the resource that the API server manages (i.e. REST).
If a webhook is not implemented on the API server, it is possible to find some other scheduling server that will not cost too much as Integromat’s operations, and let it poll the API server to check if something has happened.
Note that a webhook (i.e. HTTP request from another process, that is sent when some event happens) is usually a Trigger in some automation process. Polling is also a Trigger for a process but it is an HTTP request that is sent out from the automation process.
For example, when an Integromat process is polling the API of Twilio (third party platform, in this context, for interacting with the official API of WhatsApp), it act as a trigger. After each polling the response is checked and if a certain condition happens, the process will start.
But, when using a webhook is much better. When certain event happens, Twilio will send an HTTP request to Integromat and this will immediately trigger the automation process.
Twilio as a third party, is calling the API of WhatsApp and in this example, sends a message to some WhatsApp number.