Unify and manage your data

Prepare your environment for Reltio–Veeva Vault CRM integration

Review the required access, configuration, and system setup before deploying the integration between Reltio and Veeva Vault CRM.

Before you begin deploying recipes or configuring synchronization, make sure your environment meets the required platform access, infrastructure, and credential criteria. These requirements ensure that real-time and batch flows function reliably across systems.

Reltio tenant requirements

Before configuring the integration, your Reltio environment must satisfy several platform-level requirements related to access, modeling, and event readiness. These settings ensure that real-time and batch data flows are enabled and that synchronization operates as expected.
  • Reltio Integration Hub (RIH) must be enabled for your tenant
  • The ROLE_INTEGRATION_SPECIALIST or ROLE_INTEGRATION_CUSTOMER_ADMIN role must be assigned to users managing the recipes
  • Your Reltio model must include entity types for HCP, HCO, and Location, with configured relationships
  • Your tenant must be configured to publish change events if using real-time queues
  • You must have valid credentials for a Reltio API user with client_credentials or password grant access

Veeva Vault CRM access

To enable integration with Veeva Vault CRM, ensure that you have the following credentials and access to a licensed tenant environment.
  • A licensed Vault CRM tenant must be available for integration
  • An API-enabled user with permission to create, update, and query Vault records
  • Veeva Vault DNS (example, yourvault.veevavault.com)
  • Vault CRM version number for compatibility with the connector
  • Password and user ID for all Vault authentication steps

Queue and environment access

If you're using real-time synchronization from Reltio to Veeva vault CRM, ensure:
  • You have one of the following queue services provisioned:
    • AWS SQS
    • Azure Topic
    • GCP Pub/Sub
  • Required credentials are available:
    • For AWS: Access key, Secret key, Region, and Queue ARN
    • For Azure: Namespace, Topic name, and connection string
    • For GCP: Service account credentials and topic configuration
  • Network access is configured to allow the Reltio Integration Hub to read from your message queue
For batch integrations, queue setup is optional.

Deployment package and tools

Before deploying, make sure you have the integration assets and administrative access to all necessary tooling.
  • Latest Reltio–Veeva Vault CRM ZIP package (provided by Reltio)
  • Access to the Reltio Integration Hub Console
  • Admin access to Workato or RIH instance used for recipe configuration
  • (Optional) Access to development or sandbox environments for testing
  • (Optional) Test data sets in both Reltio and Vault CRM environments