Understanding Make
At the heart of Orchestration Engine are digital processes. These are Make scenarios that can be combined together to create automated processes. The processes run sequentially, following a set of steps from start to finish. Therefore, Orchestration Engine is closely integrated with Make. To use it, you'll need an understanding of how Make works, the way the scenarios behave, and how they can be combined within an execution.
Some key things you'll need to understand are:
Make apps: Make is a no-code integration platform based on Make apps. It connects multiple apps in a scenario to process and transfer data between them. In addition, Make runs your scenarios automatically on schedule.The advantage of Make is that you don't need to be a coder to share data across apps.
Make scenarios: Make uses scenarios to automate your tasks. A scenario consists of a series of modules that indicate how data should be transferred and transformed between apps/services.
Types of modules: Make has several different types of module. For example, you'll find actions, searches, and triggers. Actions are the most common module type. A typical action module returns just one item which is then passed on to the next module for processing.