Understanding the Integration Basics

It is crucial to understand how connectors, recipes, triggers, and connections come together to enable integrations between systems.

Reltio Integration Hub enables you to create intelligent process automation integration flows between different applications based on your business requirements. The basic building block of intelligent process automation is a recipe that starts with a trigger event, and a list of one or more actions.

A Recipe allows you to automate processes between tools, systems, and applications that you use. By using datapills, you can create conditions as part of the integration flow logic to determine the action that must be taken.

Recipes are automated integration flows that can span multiple applications and are simple yet powerful. These use a bunch of connectors to push data from one system to another. They are event-based, and you can configure the specific event that will kick-start your automation based on the integration flow requirements. For example, you can use a recipe to monitor the Salesforce system for new accounts, check the account type, and send Reltio APIs to get the information.

The three main components of a recipe are:
  1. Trigger - It determines when you would like to execute the recipe.
  2. Actions - These are the steps that your recipe will do.
  3. Application connections - These connections are required for all applications that your recipe touches.

Note: Reltio Connector must be either a source or a destination or part of an intermediate step in each recipe that you create using Reltio Integration Hub.

Process Flow

The process flow diagram describes the stages and steps to create a recipe between different applications.

As an integration specialist, your approach to creating an end-to-end integration would involve four stages:

  1. Launch Stage - Before you launch a recipe between your applications, you can look for an existing recipe that might be already available in the community for a similar use case. Community has a collection of pre-built and shared recipes that you can use. If your use case is specific to your organization and there isn’t a matching recipe, you can create a new one.
  2. Build Stage - If you choose to create a new recipe, select the recipe starting point, or, Trigger. Then, select the trigger application, or, Source. Configure or select an existing connection and build the integration flow under Actions. Whether you choose to select an existing recipe or are building a new one, at this point, you must configure the connector of the destination app and configure the mapping.
  3. Test Stage - After configuring the mapping in the Build stage, you must configure the connector for exception handling and activate the recipe. Test the recipe by activating the trigger event in the source, and if the test is successful, export the recipe for deployment. If for some reason, your test is not successful, you must recheck the erroneous job and check the recipe step that appears in red and resolve it by editing the recipe.
  4. Deploy and Monitor Stage - In the Production tenant, import your recipe for deployment, configure connections and activate and start the recipe. You can use the Dashboard page to monitor the usage and job details.

For more information on core concepts and terminology, see Core Concepts.