How to Configure Clay CRM Integrations for GTM Enrichment

According to research published by HubSpot, B2B database contact data decays at an average rate of 22 percent per year, which translates to a 2 percent monthly erosion of lead accuracy [HubSpot Data Decay]. This compounding data decay means that traditional static databases quickly become obsolete, forcing sales teams to waste productive hours on out-of-date information. Building a dynamic, automated data enrichment workflow is no longer optional for go-to-market teams trying to maintain competitive outreach efficiency.

While many organizations attempt to solve this by chaining together multiple APIs with middleware tools like Zapier, this approach introduces latency, high task costs, and complex debugging challenges. Native clay crm integrations offer a high-performance mapping solution that allows direct synchronization of lead and company objects from platforms like HubSpot and Salesforce into Clay for automated enrichment. This guide details how to set up, map, and automate these integrations to keep your customer relationship management systems updated without brittle workarounds.

When managing prospect files and enriched contact lists, GTM teams have traditionally relied on manual file transfers, downloading CSV exports, or storing spreadsheets in generic folders. However, local storage offers no version control, while legacy cloud folders lack automated indexing. This is where modern collaborative environments come in, helping teams transition from static spreadsheets to dynamic workspaces that keep humans and automated agents aligned.

Connecting HubSpot to Clay allows you to query companies, contacts, deals, and leads directly. The native connector establishes a secure OAuth channel that supports bidirectional data flows. Rather than setting up third-party webhooks, you configure the connection at the workspace level, making it available to any table you create.

To establish the connection, follow these steps:

1. Open your Clay workspace settings and navigate to the Connections panel.
2. Select Add connection and choose HubSpot from the list of available integrations.
3. Click Connect. You will be redirected to the HubSpot login portal.
4. Authenticate using an account with admin-level permissions to ensure Clay has permission to read and write records.
5. Select the specific HubSpot portal you want to link, then click Authorize to return to Clay.

Once authorized, you can import records using filters to isolate high-value leads. For example, instead of pulling your entire contact directory, you can select only same-day leads that are missing corporate domain or company size data. This targeted approach prevents credit waste and keeps your tables clean.

After importing the records, Clay carries the unique HubSpot Record ID as a key field. This ID is essential because it acts as the primary key when you push enriched details back to HubSpot, ensuring the platform updates the correct object rather than generating duplicate profiles. You can then add enrichment columns, such as LinkedIn profiles or revenue estimates, using Clay's data providers.

The Salesforce integration in Clay supports complex workflows, including reading from Salesforce reports, pulling records via custom SOQL queries, and updating lead or account objects in real time. Because Salesforce configurations vary, planning your connection is critical.

To set up the native Salesforce sync, perform the following actions:

1. Go to your Clay workspace settings and click Connections.
2. Select Salesforce from the menu and choose the appropriate authentication method.
3. Authenticate your account. If you are testing a new enrichment workflow, connect a Salesforce sandbox instance first to protect production records.
4. Once connected, select the Salesforce objects (Leads, Contacts, Accounts, or Opportunities) to import.

For complex lead pools, the standard Salesforce import might bring in too many irrelevant records. In these cases, write a custom Salesforce SOQL query to target specific records. For example, you can write a SELECT query that retrieves leads with a status of Open where the annual revenue field is blank. Testing these queries with a LIMIT clause first helps verify the data structure before executing a large sync.

When pushing enriched data back to Salesforce, use the Upsert action. Upsert combines updating existing records and inserting new ones. Clay matches the records using the Salesforce ID or a unique custom field, such as a verified email address. This ensures Salesforce remains the single source of truth for your sales representatives.

SELECT Id, Name, Email, Company, State FROM Lead WHERE Status = 'Open' AND AnnualRevenue = null LIMIT 100

A successful enrichment workflow requires precise field mapping to prevent data pollution. Because Clay pools data from multiple enrichment providers, you must define exactly which Clay column matches each HubSpot or Salesforce property.

To maintain data hygiene, use lookup actions first before writing any updates. A lookup action is read-only and pulls information from your CRM into Clay to check if a record already exists. This allows you to verify that a contact's email or domain is already present before running expensive enrichment waterfalls.

Once you confirm the record needs enrichment, configure the mapping rules. For instance, map Clay's enriched company size column to the corresponding custom field in HubSpot. If you are using Salesforce, verify that the data types match exactly (for example, mapping a decimal number to a currency field) to prevent Salesforce API sync errors.

Always carry the CRM's unique identifier throughout your workspace. If you lose this key, you risk creating duplicate contacts when pushing updates. To automate the entire process, enable the auto-update toggle on your imports. This setting instructs Clay to scan your CRM for new records on a schedule, typically on a daily basis, and automatically run the enrichment waterfall, ensuring your sales reps always have fresh data.

Coordinate Clay data and agent outputs in one place

Set up a shared, intelligent workspace to store, version, and query your enriched CRM lead lists. Access your files via the Fast.io MCP server or UI. Start a 14-day free trial of a paid organization subscription today.

Start 14-Day Trial

While Clay serves as the engine for GTM lead enrichment, teams require a collaborative workspace to manage, version, and share the resulting files. Relying on local desktops or static cloud folders leads to context gaps and lost history.

Fast.io provides a shared workspace platform designed for GTM and agentic teams. Instead of using generic storage, teams use Fast.io to coordinate files, notes, and automations. For unstructured files like PDFs or contracts, Fast.io's Metadata Views turn documents into a queryable database. Users describe the fields they want extracted in natural language (such as contract renewal dates, counterparties, or billing details), and the built-in AI populates a structured view. To explore this feature, read about document data extraction.

Fast.io supports paid organizations with plans starting at Starter (29 dollars per month), Business (99 dollars per month), and Growth (299 dollars per month). Every organization begins with a 14-day free trial, which requires a credit card. To view plan limits and start a trial, see our pricing page. Teams can configure webhooks to trigger downstream scripts whenever a new CSV is uploaded, and use URL Import to pull files directly from OneDrive or Box.

For developer teams, Fast.io works with AI workflows via its Model Context Protocol server. The MCP server exposes tools for reading, writing, and querying files. Developers can access this server via Streamable HTTP at the /mcp endpoint and legacy SSE at the /sse endpoint. For developer onboarding instructions, refer to llms.txt and the MCP guide. This allows AI agents to automatically fetch lead lists, pass them to Clay, and write the enriched files back to the shared workspace. Fast.io maintains a per-file version history, keeping every modification auditable and reversible. If an agent error corrupts a file, a human administrator can restore the previous version with a single click. To explore persistent workspace features for AI workflows, see our agent storage capabilities.