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 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 Integration retrieve and consolidate data from multiple API endpoints / multiple data sources?
...
A GetUsers API endpoint, to retrieve a list of User Names and User ID’s:
…/rest/api/getUsersA GetUserGroup API endpoint, to retrieve the Group assigned to a particular User ID:
…/rest/api/getUserGroup/{{userID}}- Note how , this particular API Endpoint accepts a parameter{{userID}}
So you will need to create two (2) Actions to meet this requirement, as follows:
...
The GetUsers (Primary) Action will retrieve a list of User ID’s and User NamesName's. It will also have a Group Name Mapping which references the second Action GetUserGroup, passing the User ID as a parameter, to retrieve each user’s assigned Group.
The GetUsers (Primary) Action Mappings would be configured like this:
...
The GetUsers (Primary) Action Group Name Mapping’s Params would be configured like this (passing the User ID over to the referenced Action):
...
The GetUserGroup Command Commands section will be configured to accept a the User ID parameter, like this:
...
The GetUserGroupAction Mappings would be configured like this:
...
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Things to consider:
 |