home

Applications

ReltioProductsDeveloper resourcesRolesApplicationsObjectives
ReltioProductsDeveloper resourcesRolesApplicationsObjectives

Unify and manage your data

Show Contents

thumbnailApplications

Reltio Zero Copy Interaction Integration from Databricks at a glance

Configure Reltio Zero Copy Interaction Integration from Databricks using APIs

Learn how to configure Reltio Zero Copy Interaction Integration by completing the required API tasks in sequence.

Configure the Databricks connection and mapping required for Reltio Zero Copy Interaction Integration from Databricks by completing the required API tasks in sequence. Create a Databricks connection, store service principal credentials, test the connection, and map a Databricks source object to a Reltio interaction type. After you complete these tasks, Reltio can query the mapped Databricks source and return matching interaction data for the related profile without copying that data into Reltio.

Prerequisites

Before you begin, ensure the following requirements are met.
  • A Reltio role that allows you to manage data integrations, such as ROLE_ADMIN or PUBLIC.
  • A running Databricks SQL Warehouse.
  • A Databricks service principal with an OAuth client ID and client secret.
  • Databricks permissions that allow the service principal to access integration objects, including:
    • CAN USE on the SQL Warehouse.
    • USE CATALOG on the target catalog.
    • USE SCHEMA on the target schema.
    • SELECT on each target table or view.
  • An existing Reltio interaction type to use in the mapping.
  • The Databricks workspace URL, warehouse ID, and shared catalog name for the source data.

Configure Zero Copy integration with Databricks

To configure Zero Copy Interaction Integration from Databricks, complete the following tasks in order:
  1. Create a Databricks connection in Reltio: Define the Databricks workspace, SQL Warehouse, shared catalog, connection properties, and authentication type for the integration.
  2. Store Databricks OAuth credentials in Reltio: Store the service principal client ID and client secret that Reltio uses to request and refresh Databricks access tokens automatically.
  3. Test the Databricks connection in Reltio: Verify that Reltio can connect to the Databricks SQL Warehouse before you create the interaction mapping.
  4. Map a Databricks source object to a Reltio interaction type: Define the Databricks source object, returned attributes, interaction type, and member mappings that link Databricks rows to Reltio entities.
Note: This integration uses OAuth 2.0 machine-to-machine authentication. In this model, Reltio authenticates to Databricks by using a service principal instead of a user sign-in. Personal Access Tokens are not supported.

Result

After you complete these tasks, Reltio queries the mapped Databricks source and returns matching external interaction data for the related profile without copying that data into Reltio. The connection, credentials, connection test, and mapping together complete the API setup required to make the mapped Databricks source available in Intelligent 360.

Updated on April 17, 2026

Footer

You've found your way to a temporary environment. Content is not complete or final. Looking for Reltio documentation? Go to docs.reltio.com.

© 2026 The RELTIO® mark is a registered trademark of Reltio, Inc. in the United States and other countries; DataDriven and Reltio Data Cloud are trademarks of Reltio, Inc. Other names or marks are trademarks of their respective owners.

Terms and Conditions, Privacy Policy, and