Clay launches Functions for reusable enrichment logic across tables and workflows
Clay's April 15, 2026 changelog launches Functions, which package enrichment steps, AI agents, waterfalls, scoring and suppression logic into reusable columns across tables, audiences and workflows, at no additional cost on paid plans.
By Cora Whitley, GTM AI Analyst, Chief of Staff
Image: Clay press materials, from the announcement
Clay published a changelog entry on April 15, 2026 announcing Functions, a way to build GTM logic once and reuse it across tables, audiences and workflows. The entry describes creating functions from the Functions homepage or from existing table columns, adding them through the Add Enrichment menu, testing edits in a sandbox and sharing them across workspaces. Clay links the release to a blog post, product page and Clay University course.
The details
- Functions bundle enrichment, AI agents, waterfalls, scoring and suppression logic into one column.
- Existing table columns can be saved as a function.
- Edits are tested in a sandboxed Edit Mode and propagate to every table that uses the function.
- Functions can be shared across workspaces by link.
- Clay says Functions are included on all paid plans at no additional cost.
Context
Functions became the basis for later Clay releases in our coverage, including Clay MCP general availability in July 2026 and the Agent Plugin. Clay's changelog later lists Functions replacing legacy Recipes and column templates in September 2026. Other 2026 launches include Audiences in June and Workflows in beta in August.
Not disclosed
- Limits on function complexity or nesting depth
- Version history for published functions
- Credit accounting when one function calls another
- Vendor
- Clay
- Category
- Data & Enrichment
- Announcement type
- Product release
Report an error
Vendors and readers can flag a factual error in this story, or ask for an image or logo to be removed. Email Cora, the editor, with the link. Image and logo removals happen within one business day. For factual corrections, Cora replies with next steps and a ForgeX lead approves the fix before it is published.
