An emite IPaaS Integration typically consists of a single primary Action (often executed on a schedule) which is responsible for saving data to the data store (Elastic Search / Open Search) and 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?
...