Many services provide so-called webhooks to deliver instant notifications whenever a certain change occurs in the service. To process these notifications, you can use instant triggers. These can be easily recognized by the INSTANT tag:
If the service does not provide webhooks, polling triggers can be used instead to periodically poll the service.
All incoming webhook data (or shortly, webhooks) are stored in the webhook's queue. To view the content of the queue:
The limit of stored webhooks in the queue depends on your pricing plan (see Webhook queue size in the pricing plans table). When the queue is full, all incoming webhooks over the limit will be refused. Webhooks are stored in the queue for 30 days, and older webhooks are removed. The data stored in the queue is counted into your storage space limit:
If your scenario contains an instant trigger, you can schedule the scenario to run Immediately:
In this case, your scenario will run immediately when Integromat receives new data from the service. Once the scenario executes, the total number of pending webhooks in the queue is counted and the scenario performs as many cycles as there are pending webhooks, processing one webhook per cycle.
If you use any schedule setting other than Immediately, the scenario will execute at specified intervals. Because several webhooks can be gathered in the queue during the interval, it is recommended to set the Maximum number of cycles to a higher value than the default 1 to process more webhooks in one scenario run:
Now, when the scenario is executed, 10 webhooks from the queue will be processed in one scenario run.
The current rate limit is five webhooks per second. If the limit is exceeded, a 429 status code is returned.
Any webhook that has not been assigned to a scenario for more than 120 hours will be removed.
When there is an error in your scenario with an instant trigger, the scenario:
If an error occurs during the scenario execution, the webhook is placed back into the queue during the instant trigger's rollback phase. In this situation, you have the possibility to fix the scenario and run it again.
If there is a Webhook response module in your scenario, the error is sent to the Webhook response. The Webhook response module is always executed last (in the case where the Auto commit option in the Scenario settings is not enabled).