We’ve been rolling out more and more information about Reltio’s newest product, Reltio Integration Hub. We’ve hosted two webinars, the first on the Hub’s basic features and components. The second webinar went even more in depth, talking about best practices and more detailed recipes. We’ve also broken this topic into multiple articles, so that members of the community can find answers about the Reltio Integration Hub on many levels.
The first article broke down the business benefits of the Reltio Integration Hub. The second article described the Hub’s features, which are:
- Integration orchestration,
- No-code/low-code integration,
- Pre-built connectors,
- An intuitive user interface, and
- High data security
We also went over triggers and actions, two main components within a recipe.
In this blog, we aim to give an actual demonstration of Reltio Integration Hub’s components and recipes. Additionally we will answer some of the topic questions that our customers and partners had. To watch along, be sure to view the first webinar on the Reltio Integration Hub.
Demonstration of Reltio Integration Hub Components
To begin, Reltio Integration Hub will be available to users right within the platform. You will be able to access it in the application selector within the drop down menu on the upper right hand side of your Reltio dashboard. The Hub is also available as a part of the console application.
Once you click on the Reltio Integration Hub, a new application will open. Here, you will see the landing page where assets are created. These assets are the recipes we’ve already covered, as well as connections.
One of these recipes has been built by one of our webinar presenters, Gaurav Gera, and is a HubSpot integration with Reltio used to replicate leads. The use case here is of lead qualification and prospecting. You can use Reltio for prospecting, and require that leads created in your marketing application are cleansed, enriched and qualified before your sales team can convert them to opportunity. Once the lead is qualified you can then share it back to your marketing automation, or the Salesforce automation applications, if you use these. This recipe replicates a lead whenever a new lead is created within HubSpot including the contact, organization as well as relationship. It also publishes the Reltio generated URI or Reltio ID back into the respective lead in HubSpot.
You will be able to view this orchestration on your screen. The first piece is the trigger, which activates the recipe whenever a new lead is created or updated in HubSpot.
The recipe performs a number of actions that includes the data replication to Reltio by using the Reltio connector, performing certain checks before creating an entity for example, before organization if created in Reltio, the recipe checks if there is an associated company to the lead.
There is also error handling, or exception handling. This monitors all the operations, and raises an error if any of the actions fail. You can control how you want to react when an error occurs. In some cases, you may choose to retry the recipe, log the error, or send out a notification using an email.
Within the actual logic of replicating data, the first action is using the Reltio connector to create the contact. Within the connector setup you map the fields from your HubSpot lead, along with transformation required. Once the lead is created in Reltio, it replicates back to the URI or the Reltio ID.
Then, it checks whether there is a company attached to that lead in the actual data that came in. If there is a company, it creates an organization using the same connector. It also maps all the data, and updates the company or Reltio ID back into HubSpot and creates the relationship.
This is a more real-time orchestration, but it could be completed as a scheduled mechanism as well. There is also a poll mechanism you could use to trigger this at a certain frequency, and check for certain events. How you trigger a recipe depends on the application as well as the connector you are using to trigger the recipe. For example, certain application connectors may not provide real time triggers or batch triggers. So if advised to check the connector capabilities before deciding on how you want to trigger data sync.
Reltio Integration Hub Dashboard
The Hub dashboard allows the administrator to monitor the number of jobs being executed, as well as the number of tasks being consumed. They will also be able to see the recipes that have been built out, getting into the details for those recipes to understand how they are being performed.
You can also check out the Workato community library within the Hub. Within this community, there are many customers, partners, and enthusiasts who contribute information. This has led to a collection of rich content, with dozens of available applications and custom connectors. In fact, this is the best place to find which sources are available within Reltio Integration Hub. Ideally, best practice would be to search for recipes in the community, based on the scenario you want to build. And, if there is already a recipe for that out there, you can quickly install it and begin to use it.
Questions Answered About Reltio Integration Hub
What is the cost of Reltio Integration Hub?
We’ve mentioned this before, but it’s worth repeating. While there is no cost involved up front, there is an addendum to review and access Workato as the subprocessor.. The addendum includes terms and conditions, and details on certain areas like data retention and storage policies. Make sure that you read through the addendum prior to signing it.
Can Reltio Integration Hub replace other systems?
No, because Reltio Integration Hub does not take on the capabilities of other systems. Rather, it connects these systems to Reltio. Look at the Hub as your first option, and leverage all the capabilities available.
I have a specific system my organization uses. How does it work with Reltio Integration Hub?
In many cases, it’s best to ask these questions of our experts within the Reltio community. Search or post your specific questions here, and be sure to watch the next webinar on the Reltio Integration Hub.
Can Reltio Integration hub fetch data from Snowflake source and load into Reltio? Please share the detailed steps on how to do that? As for Reltio Integration Hub, it provides a Snowflake connector using which you can build a recipe to replicate data to Reltio. You can build a recipe that is scheduled for example on a daily basis that reads a batch of rows from Snowflake and replicates that data into Reltio.
While creating the connection to Snowflake, you need to provide the account, warehouse, database and schema details along with the credentials (user/password or oAuth 2.0 credentials).
Can we consider Integration Hub as a central integration system for an MDM project, which could involve executing third party applications e.g. executing a Qubole notebook API? I think the first part of the question is clear. It's a straight answer, which is yes, you should consider the integration hub as the central integration system for any integrations between Reltio and any other system. This is not to be seen as a general-purpose integration platform for your organization. It is specific to Reltio. Reltio must be one of the end points. But for that purpose, for your MDM project with Reltio, you should treat the integration hub as a central integration system for connecting into Reltio or sending data out of Reltio. The example that is mentioned about executing a Qubole notebook, I think that might require some further details for us to understand and provide the right recommendation.Does Reltio Integration Hub support AWS SQS and SNS including FIFO? Those are some of the connectors already available on the platform. Amazon SQS, Google Pub/Sub, even Azure Service Bus is being created by Reltio. Those connectors are available for you to use and integrate with Reltio, read the Reltio Docs to use and then perform various operations based on the payload. All those are available. And all these questions, in the demo below, we can see how this works. And of course, we cover this in more detail in the next session, found here, wherein we'll see a complete end-to-end process of building the recipes.Can Reltio Integration Hub integrate with any source or is there a fixed set of sources? We have sources such as Qualtrics, Exigo, Hyper wallet etc.? The best way to identify whether those sources are available or not is going through the Workato Community Recipes. Or most likely, somebody would have built out the connector. Workato themselves would have built out a connector through which you can integrate with that application. The reason you do not find that connector, there are generic connectors available called HTTP connectors, as we call it, that you can use to build an integration with those external applications, making API calls, and then extracting that data and then doing the mapping. Using that HTTP connector is also simple point-and-click tools. You don't need to be a developer to use those generic connectors as well.
A deep dive in how to use Reltio Integration Hub and How to Build a Recipe within RIH
Other Helpful Resources: