Things to consider: Do your research to ensure that you are using the most optimal API endpoints provided by the 3rd party system. Try and minimise the amount of API endpoints you need to query, in order to meet your specific requirement(s). Only Actions within the same Integration can be referenced, however multiple Actions can talk to multiple data sources within the one Integration. Make use of the eMite IPaaS Action caching feature (see emite IPaaS Integration Cache) if data is expected to change infrequently. In the GetUserGroup example above, you could save the data to the Integration’s cache, so subsequent Action executions don't waste valuable API calls (retrieving the same data) and instead the Integration’s cache is leveraged for the required Group Name. Most 3rd Party systems require you to authenticate with a separate API endpoint, before you can retrieve data from any other API’s, so referencing a seperate authentication Action is common in most emite IPaaS Integrations. Authentication Actions can be referenced directly within Commands > Headers, using the format bearer {{[Action Name].[Alias]}}, i.e.
 |