Instant triggers (webhooks)

Many services provide so called webhooks to deliver instant notifications whenever a certain change occurs in the service. To process these notifications, use instant triggers. These can be easily recognized by the INSTANT tag:

mceclip0.png

If the service does not provide webhooks, polling triggers have to be used instead to periodically poll the service.

Webhook's queue

All incoming webhook's data (or shortly, webhooks) are stored in the webhook's queue. To view the content of the queue:

  1. Go to the Webhooks section in the menu on the left.
    2019-11-14_13_48_45-My_Lab___Integromat.png
  2. Find the webhook you want to view the queue of.
  3. Click the button with a truck icon and the number of received webhooks:
    2019-11-14_13_51_33-Webhooks___Integromat.png
  4. The webhook's queue is displayed.
    xgY96Sc5tv.gif

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, older webhooks are removed. The data stored in the queue is counted into your storage space limit:
2019-11-14_13_45_19-My_Lab___Integromat.png

Incoming webhook data is always stored in the queue regardless of the Data is confidential option setting. As soon as the data is processed in a scenario, it is permanently deleted from our systems.

Scheduling Instant triggers

If your scenario contains an instant trigger, you can schedule the scenario to run Immediately:

2019-11-14_11_41_00-Integration_Webhooks__Tools__HTTP___Integromat.png

In this case, your scenario will run immediately once Integromat receives new data from the service. Once the scenario executes, the total amount of pending webhooks waiting in the queue is counted and the scenario performs as many cycles as there are pending webhooks, processing one webhook per cycle.

A cycle is not the same as a scenario run! There can be more cycles within a scenario run. For more information about cycles, please refer to the Cycles documentation.
When executing scenarios with an instant trigger scheduled as Immediately, then the following exceptions apply:
  1. The interval between two executions is not subject to the Minimum interval according to the pricing plan. - i.e. once the scenario finishes its execution, the webhook's queue is checked again. If there are any pending webhooks, the scenario executes immediately again, and once again processes all the pending webhooks.
  2. The Maximum number of cycles scenario setting is ignored. See Maximum number of cycles for further details on how the actual Maximum number of cycles is determined in this case.

If you use any other schedule setting than Immediately, the scenario will execute at given intervals. As 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:

  1. Click on the cog-wheel in the bottom of your scenario to open Scenario settings.
  2. Enter the desired value (number of cycles) to the Max number of cycles field. e.g. 10.

Now, when the scenario is executed, 10 webhooks from the queue will be processed in one scenario run.

Rate limits

The current rate limit is five webhooks per second. If the limit is exceeded, 429 status code is returned.

Expiration of Inactive Webhooks

The webhook that has not been assigned to any scenario for more than 120 hours will be removed.

mceclip0.png

Error Handling

When there is an error in your scenario with an instant trigger, the scenario:

  • stops immediately - when the scenario is set to run Immediately.
  • stops after 3 unsuccessful attempts (3 errors) - when the scenario is set to run as scheduled.

If an error occurs during the scenario execution, the webhook is placed back into the queue during the instant trigger's rollback phase. In such a situation, you have the possibility to fix the scenario and rerun 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).

Custom Webhooks

You can create your own webhooks. For detailed information on creating custom webhooks, please see the Webhooks Documentation.

Popular use cases from our blog

How-to-manage-Twitter-from-a-Notion-database-part-1-Illustzration

Can You Tweet From Notion? Yes, and Here’s How to Do It [Tutorial]

slack-automation-illustration

Slack Automation: 20 Free Templates to Get You Inspired

google-sheets-automation-alt

Google Sheets Automation for Ecommerce: 23 Free Templates

tweet-automation-illustration

How to Get Someone's Tweets Before Anyone Else Does

onboarding-automation-with-integromat-alt

How to Automate Employee Onboarding in Minutes with Integromat

shopify-order-to-manufacturer-illustration-alt

How to Auto Send Shopify Orders to Dropshipping Suppliers [Guide]

Didn’t find what you were looking for?

Ticket

Create a ticket

Contact our world-class support team and tell us what’s happening.

Create a ticket
Expert

Find an expert

We feature a network of 450+ certified partners across the globe who are ready to help

Find an expert

Automate any workflow in your business

Sign up for a free account today. No credit card required, no time limits on free plan.