Clay adds cross-entity MCP search and a Pardot integration

What changed

Clay connects richer MCP prospect searches with Account Engagement list operations. Matching, enrichment and campaign eligibility remain separate checks.

Sources: Clay official release · Clay Search documentation

Two changes connect discovery with activation

Clay's 7 September roundup announces Advanced Search by default for its MCP users in Claude and ChatGPT, including cross-entity and OR filters. The same release makes its Pardot integration generally available, adding prospect and list operations for Salesforce Account Engagement. These capabilities have different consequences: one changes which records a team finds; the other can change records and campaign-list membership.

The distinction matters for RevOps because a useful search result is not automatically an eligible recipient. An operator can approve a targeting definition without authorizing immediate activation. Treat discovery, enrichment, destination matching and enrollment as separate checkpoints even when the tools sit close together in one working environment.

Inspect the query behind the request

The linked Search documentation describes a beta experience and says cross-entity filters require a paid plan. It also distinguishes Companies searches from People searches: some combinations involving company job postings or other employees are not available in People searches. Verify the relevant mode and entitlement instead of interpreting the announcement as every query being supported everywhere.

Write down the intended result grain before asking an assistant to build a query. If the business wants target accounts, a company should be the unit of selection. If it wants specific contacts, a person is the unit. Job evidence may qualify a company without identifying the correct person to approach. Inspect a sample of matches and non-matches to see whether the query implements the actual targeting decision.

OR logic deserves an explicit review

An OR clause can intentionally widen coverage, but misplaced grouping can also admit records that bypass a required condition. Translate the proposed logic into ordinary language and check each alternative against requirements that must always hold. Keep geographical, customer-status and exclusion rules visible instead of burying them in a long conversational request.

Use a small set of test cases with expected outcomes. Include a company meeting only one alternative, a company meeting both, an existing customer and a record with missing information. This is an operator-designed test, not a claim that Clay supplies a particular test harness. The purpose is to find a logic error before it becomes a larger enrichment bill or an unwanted campaign audience.

Destination matching is a separate contract

The release describes prospect lookup by email or identifier, plus create, update and upsert operations. It also supports checking and changing list membership. Before enabling writes, decide which identifier represents the existing destination record and what should happen when a match is missing or ambiguous.

Do not let a broad search silently become a broad create operation. A destination may already contain the prospect under an older email, an alternate address or a relationship the source search does not know about. Use approved test records to inspect actual mapping and failure behavior. Keep source record, destination record and intended operation together in the audit trail so a reviewer can explain each result.

Removal matters as much as addition

Audience maintenance includes records that stop qualifying. Decide whether a changed source condition should remove a person from one list, route them for review or leave the destination unchanged. These are business rules; the availability of an action does not choose the correct rule for the company.

Keep commercial exclusions and communication preferences outside the targeting model's power to overwrite. A fresh enrichment value may change a job title or company attribute without changing permission to contact someone. Recheck eligibility close to activation, particularly if enrichment and campaign execution happen at different times. Preserve the reason for a hold so the next run does not repeatedly rediscover the same unresolved record.

Validate one complete round trip

Clay says the Pardot actions use existing Salesforce authentication. Inspect the connected account and effective access before assuming an existing connection is suitable for a new workload. A connection appropriate for one table may require a new owner review when it begins maintaining campaign lists.

Follow one approved record from search through enrichment, destination lookup, intended update and resulting membership. Then change the qualifying condition and test the removal or review path. Record what happened in the destination, not only whether the source action reported success. A duplicate run should not create a second commercial or communication effect.

Track reviewed matches, ambiguous matches, rejected writes and records held by eligibility rules. Keep those operational counts separate from meetings or revenue, which require additional attribution and observation. The combined release can reduce manual movement between discovery and activation, but its value depends on whether the audience remains explainable, correctly matched and maintained after the first successful run.