Accelerate the Value of Data

Reltio Connector

Connectors simplify the interaction with the SaaS providers' APIs, providing methods for most or all of the available operations.

Reltio Integration Hub provides you the Reltio Connector through your Reltio Integration Hub account. When you create or modify recipes using Reltio Integration Hub, you require the Reltio Connector to simplify all the operations related to integrations with Reltio. Reltio Connector has the capabilities to support all your data flow tasks.

You can search for it and use it in all your recipes to handle data that flows to and from Reltio. The authentication mechanism relies upon the Reltio Authentication server.

The Reltio Connector enables you to operate on Reltio entities, relations, interactions, and data change requests. Using the Reltio Integration Hub, you can build a flow that integrates APIs from a number of applications.

Note: Reltio Connector must be either a source or a destination or part of an intermediate step in each recipe that you create using the Reltio Integration Hub.
Some of the important points regarding Reltio Connector include:
  1. In a recipe, you cannot connect to more than two different Reltio tenants. This limit is applicable to all other connectors as well.
  2. As of now, Reltio Integration Hub does not support Reference Data Management (RDM) operations.
  3. The maximum file size that Reltio Integration Hub can uncompress is 50 MB. For more information, see Uncompress files.
  4. For each task, the connector retries upto a maximum of three times. The connector waits for five seconds for the first retry and increases the interval by five seconds for each subsequent retry.

The Reltio Connector enables you to do the following tasks:

  • Custom action - Perform any Reltio API request by using Custom action
  • Create entities
  • Create relationships
  • Create interactions
  • Get entity
  • Get Relationship
  • Get interactions
  • Export entity
    • Check job status
  • Merge entities
  • Set entities as potential matches
  • Get entity by crosswalk
  • Get entities by crosswalks
  • Match entities
  • Update entities
    • Manage Roles
      • add
      • get
      • update
      • delete
    • Manage Tags
      • add
      • get
      • update
      • delete
  • Mark entities not a match
  • Unmerge entities
  • Unmerge entities tree
  • Get Potential Matches
  • Apply data change request
  • Create data change request
  • Delete data change request
  • Reject data change request
  • Search data change request
  • Additional actions included:
    • Task status
    • Delete entity by id
    • Delete entities by id
    • Delete relation by id
    • Delete interaction by id