You can find the functionality in the UI under Subscriptions Management in the left-hand navigation:

While you can set APIs to check systems for new data on a schedule, Webhooks in iPaaS.com exist to trigger APIs when a certain event takes place. For instance, when a purchase happens on an E-commerce site.

iPaaS.com has implemented both internal and external webhooks that are configurable at the subscription level.

Webhooks also have a scope that limits the type of data it utilizes.

Mapping is the process of either:

For example, in one system, you may have a field called “street_address”, and in another piece of software, that field is called “mailing_address”. Through a process of mapping fields, you can associate these so that the iPaaS.com platform can pass information from the appropriate field in one system to another.

A Mapping Collection holds all of the attributes for individual field mappings as well as mapping and error filters. It also specifies the direction, sync type and collision handling method.

Mapping collections can be nested within different levels of child records.

Each subscription in the marketplace comes with a set of pre-built mappings that can be edited as needed.

A Mapping Collection consists of one or more mappings. Each mapping has a mapping type.

Mappings can be done in a variety of ways:

iPaaS.com supports throttling which ensures key systems aren’t overloaded.

APIs are powerful tools, but the databases, servers, and clouds behind them don’t have infinite resources. As a result it is helpful to schedule and/or throttle the movement of data in and out of systems (more specifically throttling the calls that are made).

For example, when working with a large product catalog, a user would not want to update prices and inventory for all product records at once, especially not in the middle of a busy shopping day. Ideally, updates would be streamed in more manageably as to not overwhelm the eCommerce site.

You can see throttling settings on the settings page for each subscription:

Allows users to use basic C# to filter out items that are not needed or are not ready for iPaaS.com or the destination system. For instance, a merchant might not want to bring over orders from their eCommerce store till they have passed a fraud check.

Allows users to use C# to trigger errors based on the data in this mapping collection. For instance, a store owner might want to ensure that their team is adding a brand to a product, so they might want to error out on products that do not have brand specified. Errors will then be displayed in the error logs dashboard.

Translations allow users to build out a table of values from one system and match them to another. In the example above, there is a mapping of invoice status from one system and what it should be mapped to in iPaaS.com.

Allows an extension of the functionality of the subscription integration without needing to create a new data model by allowing you to map custom fields from the external system within iPaaS.com.

Data managed by iPaaS.com flows in two directions:

The Marketplace is where users can learn about and sign up for subscriptions.

When working with a system like iPaaS.com that handles data going back and forth between systems, you might encounter a scenario where one system is trying to create a duplicate ID in another system. iPaaS.com has a variety of ways to handle these types of issues: