Since the question is, “What is the best approach to create an integration using more than one Snaplex?”, it is important to know what you’re trying to achieve as there can be multiple approaches here.
If you’re looking for a parent-child relationship to accomplish this, then the Pipeline Execute Snap is the way to go. In the parent pipeline with the Pipeline Execute snap, use the “Execute On” and “Snaplex Path” fields to point the child pipeline(s) to a different Snaplex. Here is a screenshot that shows my parent pipeline will run on TriggerCloudplex and the Pipeline Execute snap would run the child pipeline on the rsramkoski_demo Snaplex.
Here is a screenshot of what that looks like from the Dashboard:
Another option if you’re looking to go with an API-focused approach where the child pipeline might be used separately from the parent, you could also have the child pipeline called by a Triggered Task using our REST snap pack. The point is there are options, so knowing more about what you’re after can help us provide better direction for you.
