Integration architecture and components
Understand how the Reltio–Veeva Vault CRM integration works by exploring its core components, connection model, and system interactions.
The Reltio Integration for Veeva Vault CRM is built using modular components that support real-time and batch synchronization. The architecture includes a prebuilt Veeva Vault CRM integration, configurable recipes, cloud event queues, and environment-specific properties managed in the Reltio Integration Hub (RIH).
This topic introduces each component and explains how they interact to enable data flow between systems.
Key components
| Component | Description |
|---|---|
| RIH (Reltio Integration Hub) | A Workato-powered, low-code platform used to host, configure, and execute integration recipes |
| Vault CRM Connector (SDK) | A Reltio-managed connector that handles authentication, API calls, and object-level transformations for Veeva Vault CRM |
| Prebuilt recipes | Configurable automation flows that execute create, update, merge, delete, and DCR actions based on system triggers |
| Event queues | External message brokers (SQS, Pub/Sub, or Azure Topic) used to deliver entity change events in real time |
| Lookup tables | Store mapping details such as attribute alignment, ID relationships, or value transformations |
| Project properties | Environment-specific key:value settings that define tenant ID, filters, callback preferences, and more |
Data flow overview
The integration enables directional data flow between Reltio and Veeva Vault CRM through the Reltio Integration Hub. Each system can act as the source or target, depending on configuration and use case.
Bi-directional sync and search-before-create flows are managed using prebuilt recipes in Reltio Integration Hub.
- A change event is emitted to the configured queue
- A trigger recipe detects the message and initiates the appropriate flow
- The relevant recipe transforms the payload and uses the connector to push the record to Vault CRM
- A callback is sent to Reltio to update the crosswalk with the Vault ID
- A scheduled job or user action in Vault CRM creates or updates an account
- A batch or event recipe retrieves the change using the Veeva connector
- The record is transformed and sent to Reltio using standard APIs
- Optionally, a DCR is raised in Reltio if approval is required before merging the change
Cloud queue interaction
| Cloud | Supported Queue Type |
|---|---|
| AWS | SQS |
| Azure | Topic |
| GCP | Pub/Sub |
Each queue transports structured messages from Reltio to the RIH recipes. The queue receives entity-level updates such as creation, merge, or deletion events.
Project structure in RIH
- A project folder (example,
Veeva Vault Integration) - Subfolders for:
TRG(trigger recipes)PROC(process recipes)CON(connection configurations)Lookup(attribute and object mappings)
- A centralized Project Properties tab for managing environment variables
Each recipe is modular and can be individually deployed, customized, or versioned without affecting the rest of the integration.