The cornerstone step vital through the entire process is knowledge of the systems. 

Knowing is half the battle

Prior to working on the integration, it is important to be versed in both parties' data models and with their API capabilities as it will serve you well to familiarize yourself with them for later use.


IPaaS.com API/Data Models can be found here.


All 3rd party information will always be ad hoc as this can only be determined once the 3rd party is identified, and some research is done.

Data Models

Things To Note

When it comes to the data models for both the 3rd party system and/or for IPaaS.com it is important to know which direction this data will be moving in relation to IPaaS.com (To/From).

Simple Activity

To better understand what work will be done for the integration. which collections will be used and which direction the data will move should be determined prior.

Collection types:

  • Customers
  • Transactions
  • Lines
  • Payments
  • Items
  • Inventory
  • etc.

once the collections that will be worked with for this integration may it just be customers or only transactions, we must now determine which direction this collection's data will be moving. This could be...

  • From IPaaS.com 
    •  IPaaS.com-->3rd party system
  • To IPaaS.com 
    •  IPaaS.com <--3rd party system
  • Bi-directional
    • IPaaS.com <-->3rd party system

Also take note of the schema for each collection in the system as one may return a collection differently than it is received.

this worksheet can define what the integration will be capable of. In terms this worksheet is a synopsis of the data models and the way that data will work in the integration based on the supported models in IPaaS.com. Consider this the order that needs to be delivered in the end.