Every iPaaS.com integration declares the set of supported features it implements. Supported features are the contract for what an integration can actually do, and they quietly drive behavior across the platform. Understanding them explains a lot of "why does it work this way for this integration but not that one?"
What a Supported Feature Is
A supported feature is a declaration that a given integration handles a particular data type in a particular direction. Two integrations that both "do products" may support different feature sets - one might send products to iPaaS.com and receive inventory back, while another only sends products. The supported features are what make that difference explicit.
What Supported Features Drive
Manual sync: which data types you can manually sync for a subscription, and the external ID format used to look records up, follow from the integration's supported features. See Manual Sync.
Webhook and hook visibility: which hooks and scopes are relevant for a subscription depends on what that integration supports.
Mapping creation: the data types and directions available when you create a mapping collection reflect the supported features - the UI won't offer a mapping the integration can't fulfill. See Manage Mappings.
Why It Matters
When you're planning to implement an integration, the supported features tell you up front which data flows are possible before you configure anything. When you're troubleshooting, they explain why a particular data type or direction may not be available for a given subscription: if it isn't a supported feature of that integration, it won't appear.
How you can see them
Supported features are documented on support.ipaas.com for each integration in the Subscriptions section.
They can also be found from the marketplace and clicking on the integration listing page and scrolling to the bottom of the page. Each line is clickable.
