An emite IPaaS Integration typically consists of a single primary Action which is responsible for saving data to a data store (Elastic Search / Open Search) and is executed on a schedule / published.
However, a single Action can only interface with a single API endpoint, so how can an emite IPaaS integration retrieve and consolidate data from multiple API endpoints / multiple data sources?
...