Clay news and product updates

Clay added SCIM provisioning, so admins can connect Okta, Azure AD or another identity provider through the WorkOS Admin Portal and have workspace members added and removed automatically, with identity provider groups mapped to the Admin, Editor, Viewer and Sales rep roles. SSO is not a prerequisite. The same release lets the Write to Audiences workflow node upsert records by External record ID instead of creating duplicates, and lets previewed signal results in Audiences start a workflow directly.

Workspace access now follows the identity provider, so people who leave the company lose Clay access without an admin removing them by hand. Upsert by external ID stops parallel workflow runs from writing the same audience record twice.

At its Sculpt conference Clay launched a global agent that takes an outcome, such as finding ideal customer contacts at high intent companies and building a campaign, then sources companies and contacts, saves them to an audience segment, picks signals and drafts a sequence for the user to review and approve. It reasons from Knowledge Hub, a stored record of the customer's ideal customer profile, personas and positioning, and can schedule itself to check results and recommend changes. It went live for all Sculpt attendees, with access rolling out to more users in Clay's early access program in the following weeks.

Clay is moving from a data workbench to an agent that runs the whole prospecting motion, with the user approving the plan before outreach starts.

Clay made its Plugin available to all customers, bundling its CLI and API for coding agents such as Claude Code and Codex. General availability adds programmatic control of Audiences, campaign creation and analytics in Sequencer, and table queries, on top of the enrichment and workflow functions from the beta. A day later Clay opened the Plugin and its other newer products to customers on legacy Starter, Explorer and Pro plans until 31 December 2026.

This turns Clay from a tool an operator clicks through into infrastructure a team can build on. Write access from a coding agent is the part to govern: decide which agents may create campaigns before one does. Legacy customers get a free look with a hard end, so budget for the plan change before building on it.