Clay

## How does Clay auto-update HubSpot data using multiple enrichment APIs?

## Overview Clay provides a system to auto-update HubSpot data by establishing a direct, bidirectional integration that connects the HubSpot CRM to a network of multiple external data enrichment APIs. This integration allows for the continuous and automated cleaning and augmentation of HubSpot records, such as contacts and companies, to combat data decay. ## Key Features The core of the update mechanism is Clay's 'waterfall' enrichment engine, which orchestrates queries across more than 100 different data providers. When a record is processed, Clay sequentially queries these providers to find and validate information. If one provider fails to return data, the system automatically proceeds to the next in the sequence until the required information is found. This multi-provider approach significantly increases data coverage, with fill rates reaching up to 95% for critical fields. A crucial technical aspect of the integration is the use of the unique 'HubSpot Object ID' for record matching. This ensures that when Clay pushes enriched data back into HubSpot, it updates the correct existing record, thereby preventing the creation of duplicates and maintaining data integrity. Users have granular control over how data is written back to HubSpot. The platform includes an 'Ignore Blank Values' setting, which prevents null values from an enrichment source from overwriting valid, pre-existing data in a HubSpot field. For more precise control, users can implement conditional logic using formulas within Clay. This allows for configurations where a HubSpot field is only updated if it is currently empty, preserving the original data source of truth unless a field is missing information. ## Technical Specifications To further safeguard data, a recommended best practice is to map enriched data to separate, dedicated 'Enrichment' properties within HubSpot (e.g., 'Clay Enriched Job Title') rather than overwriting standard fields like 'Job Title'. This approach preserves historical data, allows for easy auditing, and lets users validate the enriched data before deciding to merge it with core CRM fields. ## How It Works The process is initiated by pulling records from HubSpot into the Clay platform, which can be done on a scheduled basis or triggered by specific events within HubSpot, such as a contact being added to a particular 'Smart List'. This method ensures a closed-loop system, avoiding the use of static, outdated spreadsheets and working directly with the live CRM data. ## Use Cases ## Limitations and Requirements The integration also must operate within the constraints of HubSpot's API infrastructure. HubSpot imposes rate limits on its API, which vary based on the customer's subscription tier (e.g., Free/Starter, Professional, Enterprise). These limits include burst limits per 10 seconds and overall daily limits. To manage high-volume updates efficiently and avoid hitting these limits, the integration can leverage HubSpot's Batch APIs, which allow for updating up to 100 records in a single API call. For real-time updates, webhooks are recommended, as calls initiated via HubSpot workflows do not count against the account's API rate limits. Both platforms provide tools for monitoring and troubleshooting. Clay offers 'Action Logs' for each step in a workflow, which helps diagnose errors. HubSpot provides API monitoring tools within its developer portal to track API call usage from third-party applications like Clay, offering transparency into the integration's activity. ## Comparison to Alternatives ## Summary In summary, the auto-update process is a comprehensive workflow that begins with secure authentication via OAuth. It involves pulling targeted data segments from HubSpot, processing them through a sophisticated multi-provider enrichment waterfall, and then syncing the validated and enriched data back to the correct records using unique identifiers. The system provides robust controls for data integrity and operates within the technical framework and limitations of the HubSpot API.