Webhooks are how iPaaS.com and third-party systems tell each other, in real time, that something changed. This article explains scopes (what a webhook is allowed to act on), prioritization (the order webhooks are processed), and the Webhook Receiver (how iPaaS.com ingests inbound webhooks).
For the developer-side detail on building and processing webhooks in an integration, see Webhooks (Integration Development).
Webhook Scopes
A scope defines what a given webhook covers - which data type and direction it applies to. Scopes are what the Events Queue displays for each queued hook, and they determine which mapping collections a webhook engages when it's processed. Getting scopes right is what keeps a change in one system flowing to exactly the right records in the other.
Prioritization
When many webhooks are in flight, the order they're processed in matters - for example, making sure a product category exists before a product that needs it is created. Much of this type of dependency is handled by integrations themselves. However, some users like to prioritize certain data types outside of this (for instance, process all transactions before products). iPaaS.com can prioritize webhook processing so higher-priority work is handled first.
Prioritization is enabled by iPaaS.com on request. It isn't a self-serve setting at this point. If you'd like webhook prioritization configured for your subscription, reach out to us at support@ipaas.com and we'll set it up for you.
The Webhook Receiver
The Webhook Receiver is the iPaaS.com service that accepts inbound webhooks from external systems. It authenticates the sender (via OAuth), parses the incoming payload, and hands it to the platform to queue and process. This is what lets an external system notify iPaaS.com the moment a record changes, rather than iPaaS.com having to poll for changes.
The Webhook Receiver has its own API surface; see the REST API: Swagger/OpenAPI Reference Guide for reference.