Hi Reltio Community,
We are currently implementing the Reltio Enrichment with ZoomInfo integration and have come across a significant discrepancy between the official documentation and the actual RIH recipe package. Hoping someone from the community or the Reltio team can help clarify this.
1. DOCUMENTATION vs RIH RECIPE DISCREPANCY
The Reltio documentation (https://docs.reltio.com/en/applications/data-integrations/data-enrichment-integrations-at-a-glance/reltio-enrichment-with-zoominfo-at-a-glance/reltio-enrichment-with-zoominfo-set-up) states that batch enrichment can be "scheduled within RIH or triggered manually/externally via API." This implies that the batch process involves a direct API-based interaction with ZoomInfo.
However, after a thorough analysis of the RIH recipes, here's what we found:
a) No Direct ZoomInfo API Connection in Batch Recipes:
- The Real-Time recipes (Organization & Individual) use the "ZoomInfo | CON | ZoomInfo Connection v2.0.0" (provider: zoom_info) with an __adhoc_http_action, which is a direct ZoomInfo API call.
- In contrast, none of the batch recipes (Company or Contact) contain this ZoomInfo API connection. The only ZoomInfo-related connector in batch recipes is "zoom_info_utilities_connector," which is a local utility for attribute filtering and property validation - not an actual API call to ZoomInfo.
b) Batch Flow Relies on S3 File Exchange:
- The batch recipes follow a file-based exchange model: Reltio Export → CSV Transformation → S3 Upload (amazon_s3 → upload_file) → [Gap] → S3 File Trigger (amazon_s3 → new_file) → Response Processing → Reltio Load.
- There is no recipe or action that notifies ZoomInfo, calls a ZoomInfo API, or triggers ZoomInfo to process the uploaded file.
c) TODO Comment Still Present in Package:
- The recipe "ZoomInfo | PROC | Company - Submit Batch" (and the Contact equivalent) contains an unresolved TODO comment in the csv_parser → create_csv_lines action:
"TODO: Determine the structure of the batch request file to ZoomInfo S3 bucket."
- This suggests the batch CSV output format may not yet be finalized.
2. ZOOMINFO HANDSHAKE MECHANISM
Based on the recipe analysis, the batch enrichment appears to work on a file drop/pickup model where:
- Reltio/RIH uploads a CSV file to an S3 (or Azure Blob) inbound folder.
- ZoomInfo is expected to poll/monitor the same storage bucket, pick up the file, process it, and drop enriched results back into an outbound folder.
- RIH then detects the new outbound file via an S3 trigger recipe and processes the response.
Would love to hear from anyone who has implemented this or from the Reltio team on the following:
a) Is the above file exchange model the intended design for batch enrichment? If yes, is there documentation available covering:
- The expected folder structure (inbound/outbound paths)
- How ZoomInfo monitors/polls the storage bucket (frequency, mechanism)
b) Does ZoomInfo need separate configuration/setup on their end to enable bucket polling? If so, what is the process to initiate this with ZoomInfo?
c) Storage Compatibility: For clients on Azure infrastructure (not AWS), can ZoomInfo poll an Azure Blob Storage container instead of S3? If yes, what configuration changes are required on both the RIH recipe side and ZoomInfo's side?
d) Is there an alternative batch approach that uses direct ZoomInfo API calls (similar to how real-time enrichment works) instead of the file exchange model? If so, is there a separate recipe package or configuration for this?
Any insights or experiences from those who have worked with this integration would be greatly appreciated!
Thanks,
Nipun
------------------------------
Nipun Fnu
Apptad Inc
------------------------------